Skip to content

1 February 2023 Release Notes

Alpha release; User interface version 0.70.0

Feature highlights

Introducing journeys!

Journeys represent a collection of components in your data estate responsible for creating a data analytic deliverable.

Journeys give you an end-to-end view of the components and relationships that exist across your organization. Start from a high-level perspective, then drill down into the details—so you can understand how work is being done, at any level.

For complete details and information, see Journeys.

Tip

Interested in learning more? Start with Data Journeys and Data Estate.

Rules are changing

Along with the introduction of journeys, we've improved the way that rules are configured. To apply to more relevant and real-world situations, rules are now configured at the journey level. Plus, the conditions and actions you define can be applied to some, or all, of the batch pipelines that exist within a journey.

Set up rules to stay alert to general changes during a journey or watch out for more detailed events that are specific to your data estate. See Define Rules for information on how.

Other fixes and enhancements

  • As previously noted, the run_key property is now required by all event types. New events that do not include the run_key will not be received by the system. Existing events (those already received by Observability) will be unaffected. [PD-882]
  • The run_key property is now exclusive to a single run within a particular batch pipeline. This ensures that events published from a data estate can be more accurately associated with their respective run. For more information, see Run Status. [PD-902]
  • We applied general fixes to reduce errors.
  • We made various improvements to our user experience. Our help documentation has been updated to reflect these changes.