Show Menu
SUJETS×

Release Notes

This page lists all the new features and improvements for Journey Orchestration. You can also consult the Documentation Updates .

Q2 Release - June 2020

Adobe Experience Platform integration enhancements
The following Adobe Experience Platform integration enhancements have been made:
  • A new activity allows the listening of Adobe Experience Platform segment entrances/exits to make people enter or move forward in a journey. Read more
  • Adobe Experience Platform segments can now be created and edited without leaving the Journey Orchestration interface, thanks to a new Segments tab. Read more
  • In the simple expression editor, Adobe Experience Platform segments are now directly listed in the navigation tree to allow easy setup of conditions such as "does this person belong to segment A?". Read more
  • Journey Orchestration is now automatically passing, to the Adobe Experience Platform, the steps executed in journeys. This includes potential errors encountered. This information can be used for achieving reporting and troubleshooting by executing queries on the Journey Step events for a particular journey or for all journeys. Read more
  • Journey Orchestration can now be connected to production and non-production Adobe Experience Platform sandboxes. Note that sandboxes is a beta feature. Read more
Journey designer and test mode enhancements
The following enhancements have been made to the journey designer and the test mode:
  • You can now copy paste activities from one journey to another, selecting 1 or N journey activities. Read more
  • After firing an event to make a test profile enter a journey, you can now see its progress along the journey thanks to a colored visual flow. In case of error in the journey, details of errors are also displayed. Read more
  • The Finished journey state has been renamed Closed (no entrance) to better reflect what this state means.
Other improvements
To avoid sending too many API calls to third-party systems, we're introducing a new public API to setup "capping" rules. Capping rules allow the definition of a maximum number of calls to an API endpoint per milliseconds. Read more
Access control now allows more granularity in user access management. Effective availability: June, 30 2020. Read more
Journey Orchestration is now available in APAC (Australian data center). Effective availability: June, 30 2020
The Journey Orchestration interface is available in Japanese.

Q1 Release - March 2020

What's new?
Test mode enhancements
The following enhancements have been made to the test mode:
  • When a journey uses several events, you can now trigger each of them individually from a drop-down list, in the Event configuration screen of the test mode. Read more
  • When one or more Wait activities are used in a journey, you can now define the time that each of these activities will last in test mode. The default time is 10 seconds. You can change this using the Wait time in test parameter, in the bottom left corner. Read more
  • In the test logs , in case of an error when calling a third-party system (data source or action), the error code and error response are now displayed. Read more
Centralized timezone management
Timezone management is now centralized in the journey properties panel. Two parameters have been added in the journey properties:
  • The Timezone drop-down list allows you to select a specific timezone. By default, the browser's timezone is used.
  • The Profile Timezone checkbox allows you to use the Adobe Experience Platform Profile timezone of the person entering the journey, if available. If not, the timezone defined in the drop-down list is used. This feature is not compatible with journeys using events that do not have a namespace.
For more information, refer to the Changing properties and Timezone management sections.
Journey designer enhancements
The journey palette , on the left side of the journey designer has been enhanced:
  • A new icon, next to the Search bar, allows you to hide or display unavailable elements in the palette, for example the events that use a different namespace than the ones used in your journey. By default, unavailable items are hidden.
  • When using the Search field, the number of results for each canvas activity category is now displayed.
  • The navigation between the different activity categories has been improved.
In the journey designer, you can now check you are accessing the latest version of the journey. This information is displayed next to the version number.
In the journey canvas , when two activities are disconnected, a warning message is now displayed.
For more information, refer to the detailed documentation .
Contextual Help
A contextual help is now available across the different Journey Orchestration list screens (journeys, events, actions and data sources). This allows you to view a quick description of the current functionality and access related articles and videos.
To display the contextual help, click the icon in the upper-right corner of the screen.
Other improvements
  • In addition to US, Journeys Orchestration is now available in EMEA . The application and documentation are available in French and German.
  • Experience League is now integrated into the product. This simplifies the access to related content and helps you get the most out of Experience Cloud. Direct access to Journey Orchestration documentation is available at the bottom of the Help tab. Additionally, click Help > Feedback to report issues or share your ideas with Adobe.
  • The C keyboard shortcut, which allows you to create a new item, is now available in all list screens: journeys, data sources, actions and events. Read more
  • You can now delete stopped journeys. Reports associated to these deleted journeys will not be available.
  • When browsing through Adobe Experience Platform fields (XDM format), you will now see the display name in addition to the field name. This information is retrieved from the schema definition in the Experience Data Model. When available, the alternate display name appears. This user-friendly description, especially useful in the case of eVar fields, allows you identify your fields more easily. Read more

GA Release - December 2019

Journey Orchestration is now GA.
Build real-time orchestration use cases leveraging contextual data stored in events or data sources.
Journey Orchestration allows real-time orchestration powered by contextual data from events, information from the Adobe Experience Platform, or data from third-party API services. The application determines in multistep flows called journeys the next best actions specific to the consumer, based on their profile and behaviors. This comprises both the optimal timing, as well as the type of action, such as sending the consumer a push notification via Adobe Campaign Standard transactional messaging capabilities (requires Adobe Campaign Standard) or the notification of a third-party system. These decisions are made based on rules and Sensei scores.
Learn more on Journey Orchestration.
Additional resources: