Orchestrator will go beta in Winter ’22. As a reminder, this is the home page for Orchestrator.
Here are the notable improvements in Winter ’22 for Orchestrator. To see the Winter ’22 preview for Flow, go here.
Background Steps enable Autolaunched Flows to be integrated into orchestrations
Background Steps are simple steps that don’t involve assignees. These steps essentially represent a single Autolaunched flow.
Orchestrations can loop back to repeat earlier stages
This functionality leverages the new ‘Go To’ connectors in Auto-Layout Mode
Orchestrations can be packaged
When you add an Orchestration Flow to a package, it will spider in the rest of the Orchestration’s metadata. It also properly adjusts for assignees, which were breaking cross-org packages.
Orchestrations support Manual Variables, Input Variables and Output Variables
You can now define manual variables in an Orchestration flow, just as in other flows, and configure them to be exposed to receive inputs or provide outputs.
Orchestrator Instance Records Available in Flow Builder
Orchestrator in Winter ’22 is lacking in tools to show the status of running orchestrations, but that temporary gap is already getting filled by the community, which can leverage the ability to query for all three of the core Orchestrator instance objects: Orchestration Instances, Orchestration Stage Instances, and Orchestration Step Instances