The following enhancements have been made for Oracle Infinity Data Collection:
- Back up persisted cookie data using localStorage. The Oracle Infinity tag now automatically uses localStorage in client browsers to back up persisted cookie data, allowing this data stored in the browser to persist even after the browser is closed. To benefit from this new functionality, contact your Oracle representative to update to the latest Oracle Infinity tag version.
- The BlueKai plugin for the Oracle Infinity tag has been redesigned to no longer store cookie data in raw JSON format. The reason for this change is that Akamai, who hosts the Oracle Infinity tag, detected a raw JSON data block that is used in the BlueKai plugin as an attempted attack when client browsers loaded the Oracle Infinity tag enabled with this plugin. With this redesign, data is no longer stored in raw JSON format, which mitigates the false positive result and eliminates the need for administrators to modify Akamai threat detection rules. If your Oracle Infinity tag has the BlueKai plugin enabled, please contact your Oracle representative and request an update to your tag.
- Unencoded percent ("%") characters in event data caused an event to fail data collection. When the i18n encoding setting for the Oracle Infinity tag was disabled and an event containing an unencoded percent ("%") character was passed to Oracle Infinity's data collection servers, the event failed to be collected and an HTTP status code of 500 was returned. The Oracle Infinity tag has been updated to automatically encode any standalone percent ("%") characters in an event. To benefit from this change, please contact your Oracle representative to update to the latest Oracle Infinity tag version.
Note, that as a best practice, Oracle Infinity recommends using the i18n encoding feature of the Oracle Infinity tag, which validates proper encoding before sending and collecting data to Oracle Infinity data collection servers.
The following enhancements have been made for Oracle Infinity Analytics:
- Navigate to a collection's dashboard by clicking a collection's thumbnail. On the Analytics Home screen, when you click a the thumbnail image for a collection you will land on the default dashboard that is configured for that collection. Note, each collection has only one default dashboard.
- Configure the default dashboard for a collection. As mentioned above, each collection has one default dashboard, though a collection can have multiple dashboards. When inside a collection, the default dashboard is pinned to the top of the left menu, and other dashboards are accessible within categories in the same left menu. To configure the default dashboard for the collection, go to the Analytics Home screen and edit the collection. In the collection editor, you will find a new setting allowing you to select from a list of dashboards that have been created in your account. Select from the list of dashboards and then save the change.
The following Oracle Infinity defects have been resolved:
- The Responsys connection in Oracle Infinity Action Center was always defaulting to RID when edited, regardless of the actual saved key value. This was a superficial error that was not recalling the actual saved key value from the configuration database even though it was correctly set. Now when editing a Responsys connection, the correct key value stored in the database will appear. (INF-32513)
- In analytics reports, the description defined for a measure should display in the measure's tool tip. (INF-12236)