This is the second post of a 2-part series. Here, we go over how to run an Orchestration. In Part 1, we built this Orchestration and showed the different features available to admins and end users during design time.
Orchestration Run Through
This is what the end user experience looks like when running the Orchestration that we built in the first post.
Orchestration Runs List View
The Orchestration Runs list view will give you a consolidated view of every orchestration that’s ever been run in your org. Admins can also cancel their running Orchestrations from this list view.
Debugging Your Orchestration
If an orchestration is not functioning as expected, you may want to visualize how it has progressed through each stage. The Debugger is a great tool for seeing the progress an orchestration has made. Additionally, the Debugger will list real values of any variables you’ve added in your Orchestration.
Upon clicking into an orchestration run, you can access the full run history. You’ll see a step-by-step rundown of what’s been completed in the orchestration so far, who completed it, and how long it took. The history is a great starting point for identifying bottlenecks in your process.
Orchestration Work Items List View
The Orchestration Work Items list view allows your end users to more efficiently track all of their assigned work, and is the view from where Admins can reassign work items.