Release Notes

Last update: 2023-09-12
  • Created for:
  • Beginner
    User

This page lists all the new features and improvements for Journey Orchestration. For Experience Platform features, refer to the following release notes.

NOTE

For the features released in 2022 and 2023, the links direct to Adobe Journey Optimizer documentation.

August 2023 Release

Improvements

  • You can now leverage API call responses in custom actions and orchestrate your journey based on these responses. This feature is currently available as a private beta. Refer to the Journey Optimizer documentation.

April 2023 Release

Improvements

  • The layout of the configuration pane, which appears in actions, data sources, events and journeys, has been improved.
  • You can now define static or dynamic query parameters in your custom actions. Refer to the Journey Optimizer documentation.
  • New guardrails to manage growth of experiences delivered by Journeys:
    • We recommend that you keep the number of nodes limited to 50 or less to keep your journeys performant, easy to read, QA and troubleshoot. The number of activities will be displayed on the upper left section of the journey canvas. Refer to the Journey Optimizer documentation
    • As you develop and launch journeys, we will notify you as you approach the milestone of 100 live journeys at one time. Should your plans require more than 100 journeys at a time, please create a ticket for support after seeing the notification and we will help you. Refer to the Journey Optimizer documentation

March 2023 Release

Improvements

  • The new Throttling API allows you to set a limit on the number of events sent per second, preventing overwhelming traffic spikes on your external systems or API. When the set limit is reached, all subsequent API calls are queued and processed as soon as possible, in the order they were received. Please note that this feature supports only one throttling configuration across all your sandboxes. Learn more
  • The Journey canvas has been enhanced for a simpler and improved user experience. At the end of each path in the canvas, the empty place holders have been removed. You can now simply add your activities by dragging them at the end of a path.
  • In the journey canvas, the label of the End tag is no longer automatically set with the previous activity’s name. Users can manually add a custom label if needed.
  • The default timeout and error duration in journey properties has been changed from 5 to 30 seconds. Refer to the Journey Optimizer documentation.
  • A guardrail has been added to the test mode to only listen to events sent through the interface. Events sent through an external tool are not taken into account. Refer to the Journey Optimizer documentation.

February 2023 Release

Improvements

  • The Re-entrance wait period field has been added to the journey properties. This field allows you to define the time to wait before allowing a profile to enter the journey again in unitary journeys (starting with an event or a segment qualification). This prevents journeys from being erroneously triggered multiple times for the same event. By default the field is set to 5 minutes. Refer to the Journey Optimizer documentation.
  • Improvements have been made for journey start and end dates. If you have not specified a start date, it is now automatically added at publication time. This allows profiles to exit automatically when the date is reached. Refer to the Journey Optimizer documentation.

January 2023 Release

Improvements

  • When adding a Segment qualification in a journey, the namespace is now pre-filled, by default, with the last used namespace. Refer to the Journey Optimizer documentation.
  • In the journey canvas, a new button is available in the toolbar which allows you to download a screenshot of your journey.

September 2022 Release

New capabilities

Data Governance and Privacy

With its Data Usage Labelling and Enforcement (DULE) governance framework, Journey Orchestration can now leverage Adobe Experience Platform governance policies to prevent sensitive fields from being exported to third-party systems through custom actions. If the system identifies a restricted field in the custom action parameters, an error is displayed preventing you from publishing the journey.

The use of Data Usage Labelling and Enforcement (DULE) is currently restricted to selected customers, and will be deployed to all environments in a future release.

For more information, refer to the Journey Optimizer documentation.

Improvements

  • A new guardrail has been added to unitary journeys (starting with an event or a segment qualification) to prevent journeys from being erroneously triggered multiple times for the same event. Profile re-entrance will now be temporally blocked by default for 5 minutes. Refer to the Journey Optimizer documentation.

Other changes

  • To improve performance, Experience event field groups can no longer be used in journeys starting with a Segment qualification activity. This change only applies to new journeys. Existing ones will keep the current behaviour. Refer to the Journey Optimizer documentation.

Improvements

  • Ending a journey - In the journey canvas, the End activity has been removed from the palette. End tags are now added by default at the end of each path and cannot be removed. This improvement allows better reporting of where a customer dropped out of the journey, without any action required from the journey practitioner. Refer to the Journey Optimizer documentation.

  • The Profile time zone option is now unchecked by default in journey properties. Learn more.

May 2022 Release

Improvements

  • Expression editor - The limit function has been added to allow you to limit the number of items of a list. The sort function now allows you to sort out a list object. The support of listObject has also been added to the disctinct and distinctWithNull functions.

March 2022 Release

Improvements

  • To avoid having unnecessary fields in the unified profile schema, the Journey Step Event schema is no longer enabled for profiles by default. If needed, you can activate it. Learn more
  • New step events related to export jobs are now sent by Journey Optimizer to Adobe Experience Platform. Examples of queries have been added to documentation. Learn more

February 2022 Release

Improvements

  • To optimize performance and prevent obsolete resource usage, all journeys in test mode that have not been triggered for a week will now switch back to the Draft status. Read more

January 2022 Release

Improvements

  • Journey Orchestration step events can now be linked to other datasets in Adobe Customer Journey Analytics. The profileID field, in the built-in Journey Step Event schema, is now defined as an identity field. Learn more
  • The capping rule for Adobe Campaign Standard actions has been changed to 4000 calls / 5 minutes. Read more

October 2021 Release

Improvements

  • Expression editor - As a power user, you can now use functions to work with maps. Learn more
  • Accessibility - Accessibility enhancements have been implemented. Journey Orchestration is now fully compliant in terms of accessibility.
  • Collections - Arrays of objects containing sub-objects are now supported. Read more
  • Monitoring - Step events for live journeys and test mode have been enhanced. New fields have been added related to profile export jobs. For a better user experience, step event fields are now organized in different categories in the Journey Step Event schema for Journey Orchestration. All previous step events fields are still available in the stepEvents category.

September 2021 Release

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.

Improvements

  • System generated schemas and datasets that have been created during provisioning for step events are now in read-only mode, safeguarding against any inadvertent modifications to critical schemas. Learn more
  • Cleanly label the Wait activity with a label that will be displayed in the canvas. The label is also used in reporting and test mode logs to clearly identify what you are doing. Learn more
  • Find your events and actions faster by filtering elements in the Events and Action categories using search. Orchestration activities are no longer filtered. Learn more
  • When defining an event ID condition in a rule-based, the “contains” operator is now available for string types of fields. Learn more

August 2021 Release

Improvements

Journeys

  • Dynamic headers - You can now pass dynamic data in HTTP header parameters. These parameters can be used by the integration systems that receive the journey action HTTP calls, for example timestamp or tracking ID. Read more
  • Dynamic URL paths - You can now set up dynamic URL paths for custom actions. Read more

July 2021 Release

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.

Improvements

  • The Cache duration field has been removed from the data source configuration pane. Read more

June 2021 Release

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.

Improvements

  • For external data sources, a capping rule of 15 calls per second is now automatically defined. Read more
  • The simple and advanced expression editors now support the XDM date format.
  • In the journey list screen, a new filter has been added. You can now filter by journey type: Unitary event or Segment qualification. Read more
  • For live journeys, the journey properties screen now displays the publication date and the name of the user who published the journey. This information is also available when you copy the journey’s technical details. Read more

April 2021 Release

Improvements

  • In the Event configuration screen of the test mode, a dropdown is now displayed for fields that expect an enumeration. Simply select one of the available values. This will avoid errors when triggering the event if an incorrect value is defined. Read more

March 2021 Release

Improvements

  • A new status has been added to journeys. When a journey ends or is manually closed, its status switches from Closed to Finished 30 days after it was closed. This will allow you to identify inactive journeys more easily while making sure all individuals still present have time to finish the journey. Read more
  • In the activity right panes of draft journeys, read-only fields are now hidden by default. This interface simplification will help you configure your activities more easily. To display them, click the Show read-only fields icon, available in the top left corner of the activity configuration pane. Read more
  • In test mode, in the Event configuration screen, the Key field used to define the test profile’s ID has been renamed Profile identifier for a better user experience. Read more.
  • For reaction events, the timeout duration can now only be set between 40 seconds and 30 days. When testing a journey that uses a reaction event, the test mode Wait time default and minimum value is now 40 seconds. Read more.

February 2021 Release

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.

Other improvements

  • Now, when configuring an event, only fields that are mandatory for the XDM validation are pre-selected by default. These fields cannot be unselected.
  • In the journey palette, a new filter has been added. It allows you to only display the last five events and actions used, in addition to out-of-the-box ones. This is specific to each user. By default, all items are displayed. Read more
  • When starting a new journey, elements that cannot be dropped in the canvas as the first step are now hidden. This concerns all actions, the condition activity, the wait and the reaction.
  • In the left part of the advanced expression editor, functions are now regrouped under a Functions section at the end of the list.

January 2021 Release

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.

November 2020 Release

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:

  • simplify the design of very complex journeys by splitting them into several ones
  • build journeys based on common and reusable journey patterns

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.

Other improvements

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

October 2020 Release

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.

Other improvements

  • When you publish a new version of a journey, the previous version automatically ends and switches to the Closed status. Read more

September 2020 Release

GA updates

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.

Alpha updates

Read segment activity improvements

The following improvements have been made to the Read segment activity:

  • Segment-based journeys now display, above the canvas, a reminder of the journey's schedule type. You can click on this reminder to access the schedule configuration menu.

  • The granularity of test mode logs has been improved to display the segment export progress status.

August 2020 Release

GA updates

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

Alpha updates

Segment Trigger activity

The following improvements have been made to the Segment Trigger activity:

  • The activity's name has been changed to "Read Segment".

  • The configuration of the journey scheduler has been removed from the activity’s properties. It is now accessible directly from the Journey's properties, in a dedicated section that will display if a Read Segment activity has been dropped into the canvas.

  • You can now test the journey on a unitary profile and track its progress in the journey using the visual flow.
Rule-based events

The following improvements have been made to rule-based events:

  • You can now leverage all of the Adobe Analytics behavioral event data that you are already capturing and streaming into the Platform in order to trigger journeys and automate experiences for your customers. Read more

  • When triggering a rule-based event in test mode, you can now directly view the event ID condition. Also, a tooltip has been added next to each field that is part of the rule evaluation. Read more

  • The rule-based event definition screen has been reorganized for an improved experience. Read more

Alpha Release - July 2020

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:

  • Menus moved from the top to the left-hand side of the interface.

  • Grouping of admin functionalities into a single dashboard.
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

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

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, 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

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:

Previous page
Next page

On this page