This page lists all the new features and improvements for Journey Orchestration.
You can also consult the latest Documentation Updates.
Pass lists of data dynamically using custom actions |
---|
You can now pass collections or a list of data in your custom action parameters that will be dynamically populated at runtime. Two kinds of collections are supported: simple collections and object collections. Previously created custom actions will continue working. For more information on collections, refer to the detailed documentation. The filter and intersect functions have been added to the list of functions available in the advanced expression editor. This offers more possibilities for collection filtering and comparing. Consult the documentation on the filter and intersect functions. |
Journeys
Leverage schema relationships |
---|
Adobe Experience Platform allows you to define relationships between schemas in order to use one dataset as a lookup table for another. Journey Orchestration can now leverage data coming from a linked schema. These fields are available in unitary event configuration, journey conditions and custom action personalization. For more information, refer to the detailed documentation. |
Adobe Campaign Classic integration |
---|
The integration with Adobe Campaign Classic integration is now GA. It allows you to send emails, push notifications and SMS using Adobe Campaign v7 or v8 Transactional Messaging capabilities. The connection between the Journey Orchestration and Campaign instances is setup by Adobe at provisioning time. For more information, refer to the detailed documentation. |
Update profile activity |
---|
This new action activity allows you to update an existing Adobe Experience Platform profile with information coming from the event, a datasource or using a specific value. For more information, refer to the detailed documentation. |
When selecting a schema in the event configuration, only fields that are mandatory for the event to be received properly by Journey Orchestration are selected. Read more
Journey properties attributes are now available in the simple expression editor. Read more
Two new journey properties attributes have been added (sandboxName and organizationId). Read more
To align with Adobe Campaign Standard SLAs, a capping rule of 13 calls per second is now automatically defined for Adobe Campaign Standard actions as soon as Adobe Campaign Standard integration is set up. Read more
The event timeout duration is now specified more clearly on the timeout path. Read more
The getListItem and split functions have been added to the list of functions available in the advanced expression editor. This will offer more possibilities in your string computation use cases.
Jumping from one journey to another |
---|
A new action activity allows you to push individuals from one journey to another. The Jump activity allows you to:
For more information, refer to the detailed documentation and tutorial video. |
Using journey properties in the expression editor |
---|
In the advanced expression editor, we've added a new category in the list of fields and functions. This is the information retrieved by the system from live journeys, such as the journey ID or the specific errors encountered. This will give you more possibilities when building your journeys. For example, you will be able to alert third-party systems in case of errors encountered in a condition or an action. For more information, refer to the detailed documentation. |
Rule-based events (beta) |
---|
A new method is now available to set up your events more easily, without using an eventID: rule-based events evaluate if the event should be triggered according to a condition. You can still use the existing method, now called "system-generated". This feature, which has been tested among a limited set of customers through the Alpha program, is now available in Beta to all customers. |
Limitations have been added when creating new versions of a journey. These limitations avoid too drastic changes in the journey to keep some consistency between versions. Read more
The Segment Qualification activity can no longer be used in a journey that includes Campaign Standard message activities. This restriction protects the integrity of Adobe Campaign Standard instances. Indeed, Segment Qualification usage can lead to daily peaks of message sending that would overload Campaign Standard Transactional Messaging. Read more
Event timeout |
---|
You can now configure a timeout for an event in order to make a journey listen to an event only during a certain time. You no longer need to add a Wait activity in parallel to the event path to achieve this. For more information, refer to the detailed documentation. |
Condition activity improvements |
---|
When adding conditions to your journey, you can now define a label. If you use several conditions in a journey, this allows you to identify them more easily. For more information, refer to the detailed documentation. |
Read segment activity improvements |
---|
The following improvements have been made to the Read segment activity:
|
The payload of Segment Qualification events now contains the following context information, which you can use in conditions and actions: the behavior (entrance, exit), the timestamp of qualification and the segment id. Read more
Segment Trigger activity |
---|
The following improvements have been made to the Segment Trigger activity:
|
Rule-based events |
---|
The following improvements have been made to rule-based events:
|
The Alpha program offers features that are currently tested among a limited set of customers. This allows us to improve our product based on the feedback received. These features are not available to all Journey Orchestration customers.
Enhanced user interface |
---|
Navigation within Journey Orchestration menus has been enhanced, in order to provide a consistent interface with Adobe Experience Platform:
|
Segment Trigger activity |
---|
The Segment Trigger activity allows you to make all individuals belonging to an Adobe Experience Platform segment enter a journey. Entrance into a journey can be executed either once, or on a regular basis. |
Rule-based events |
---|
We have simplified the way you set up Experience events. We're introducing a new method that does not require the use of an eventID. When you set up your event in Journey Orchestration, you can now define a rule-based event. Read more |
Adobe Experience Platform integration enhancements |
---|
The following Adobe Experience Platform integration enhancements have been made:
|
Journey designer and test mode enhancements |
---|
The following enhancements have been made to the journey designer and the test mode:
|
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.
Test mode enhancements |
---|
The following enhancements have been made to the test mode:
|
Centralized timezone management |
---|
Timezone management is now centralized in the journey properties panel. Two parameters have been added in the journey properties: ![]()
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:
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 ![]() |
Other improvements
In addition to US, Journey 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
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: