|Version||Date Released||Features & Enhancements||Resolved Issues||Downloads|
|23.04.0||16 June 2023
Through Journey Analytics use of Organisations we have confirmed that the application is ready to support multi-tenanted Journey Manager instances. In this release, along with extensive testing, we identified and resolved Issues around Segmentation so that all Journey Analytics data is isolated by Organisation.
Queue processing improvements
Improvements have been made to task processing in our GCP queues to provide better error logging and clean up of old tasks.
EventConsumer API Changes
We hardened our APIs this release. The following changes are noted but should not affect normal operation. No action is required due to the changes to EventConsumer APIs.
Required Analytics Info
Going forward, we will require the following information is populated (cannot be
tmInstance in request JWTs
customerId in request JWTs
formVersion data for form analytics payloads
If any required data is not supplied, a
400 Bad Request response will be returned.
This affects all types of EventConsumer API requests. For clarity, these include:
- Metadata: recieves data about the Form or Job sent when a user session begins
- Session: recieves data about each user sesssion for a form transaction
- Analytics: receives data about user actions during a form transaction
- Job: receives data about Job events during a Job transaction
Overall, impact is minimal. The changes only affect sending of custom analytics events. Now, if requests to the EventConsumer API lack required information, an appropriate error will be returned and the data will not be queued for storage.
The positive impact is that we will be reserving our resources for legitimate requests only. Prior to these changes, queues could accumulate many bad requests and as a result, a problematic customer environment would experience delayed data processing. We now provider faster feedback by identifying these issues at the interface itself.
Initial conceptual design for Benchmarking has begun and will continue into 23.10.
Legacy Dashboard deprecated
The Legacy Dashboard has been removed from the code base and is no longer available to clients. Public documentation has been update to remove Legacy Dashboard related content.
This release also fixes the following issues:
- Faster load time for Scope Selector data.
- Updated the design for empty charts in the Dashboard Completion History and Current Activity for a better UX.
- Increased the number of concurrent server requests possible.
- Previously unreported Safari users on iPad are now being identified more accurately.
- Completion History documentation improved.
- Updated old UI screenshots in public documentation.
Features and Enhancements
|ADP-7337||TID-2999||Verify Multi-Tenancy clients are isolated by organisation|
|ADP-7337||TID-3000||Expand documentation on Organisations and their use in JA|
|ADP-7337||TID-3035||Scope Selector - Show Collab Job Organization info for multi-org and global-org users|
|ADP-7337||TID-3041||Segment Data is not contained to the users org in global filters|
|ADP-3846||TID-2980||When network issues arise, have the "Retryable" retry over a longer period|
|ADP-3846||TID-2983||Discover why some payloads are unable to be processed by store-queue-payloads (metadata, session especially)|
|ADP-3846||TID-3014||Introduce a max retries for task queues to prevent holding invalid tasks indefinitely|
|ADP-3846||TID-3026||Address required user_agent property errors when value is NULL in FormSession payloads|
|ADP-3846||TID-3027||In some cases, Form Version metadata not stored in BigQuery|
|ADP-7338||TID-3007||Define reserved milestone values|
|ADP-7338||TID-3010||Design Jam: Design the output, what users will see in JA|
|ADP-5224||TID-2886||Remove Legacy Dashboard app (ti-dashboard module)|
|ADP-5224||TID-2997||Remove Dashboard from docs|
|TID-2643||Docs - Clarify dates for Completion History chart on Dashboard|
|TID-2729||Dashboard UI - Current Activity status to display "zero" when there are no active users|
|TID-2967||Replace UserAgentUtils with other supported lib|
|TID-3038||Visualiser - more than 20s for initial load, Waiting for Server to Respond|
|TID-3039||Given no segment data, when Segment reports are added the app crashes (localstorage must be cleared to recover)|
|TID-3044||React Select width always set to 300px when grouped values are displayed|
|TID-3069||Visualiser Concurrent Requests limit|
|TID-3071||Job Selector - Selecting job which shares name with other jobs causes multiple selections|