This blog will help you to debug your Orchestration using Orchestrator Studio Debugger. From 188.8.131.52 Tools Release , we can debug the Orchestration Object from Orchestrator Studio.
The JD Edwards EnterpriseOne Orchestrator provides a way to debug your orchestrations. Debug Orchestrations is the tool that you can use to determine the state of your orchestration at any point during execution. Debug Orchestrations provides a view into an orchestration, enabling the designer to run an orchestration step-by-step and ensure that the data is correct at each step until the final orchestration output
As orchestrations become more complex, orchestration designers need a view of the data that is passed from one step to another to ensure that the orchestration is working as designed. Use the Debug Orchestrations to stop execution so that you can see the state of the orchestration at a specific point by reviewing the values of input parameters, output parameters, and variables. When the orchestration execution is stopped, you can review the output line by line to check for issues.
Orchestration debugger will be invoked when we click on the "Debug" button
Below features are available in Orchestrator Debugger
- Run - Runs an orchestration until completion unless you set up breakpoints. If you set breakpoints, this option executes an orchestration till the breakpoint is reached or resumes a suspended orchestration.
- Step Forward - Executes the orchestration one step at a time. When a step has been executed successfully, a green check mark appears on the step.
- Stop Orchestration - Stops the execution of an orchestration.
- Orchestration input - Shows or hides the dialog box to enter or edit the initial orchestration inputs.
- Clear Break points - Removes all the breakpoints that you have set for the orchestration in the debug mode.
- Close the debugger - Exits Debug Orchestrations.
Follow the below steps to debug the Orchestration
- Login into Orchestrator Studio
- Select the Orchestration
- Click Run Orchestration
- We can set the break point by selecting the circle highlighted in the below screenshot
Breakpoints enable you to define where or when to halt the execution of an orchestration. You use breakpoints to run the orchestration until it reaches a certain step.
In the debug mode, a blue circle appears to the right of the step in the orchestration flow. You can set a breakpoint by clicking either the blue circle or the step in the orchestration flow. A blue dot appears next to the orchestration step indicating that the breakpoint has been set.
If you set a breakpoint and click the Run/Resume icon on the Debug Orchestrations panel, the orchestration runs until it encounters that step. To continue execution after the breakpoint, you can use the Run/Resume or Step Forward icons on the Debug Orchestrations panel.
- Success condition debug flow
- Failure condition debug flow
- Data Section information - The Data tab displays all the available data that the orchestration consumes and generates, which includes the data that the orchestration consumes from a step. This tab displays the following information:
Step Variables. Displays all the variables created by the steps that have been executed. Variables from steps are added to the top of the list, so the most recent variables are shown at the top. Variables of single values like strings and numbers can be changed before resuming the orchestration. Variables containing arrays or JSON objects are read only.
Orchestration Inputs. Displays the values for inputs that were defined initially to start the orchestration.
System Values. Displays the values for the default inputs: User Address Book Number, User Name, System Date, and Orchestration Input. The values for these inputs represent the originator of the orchestration when executed at runtime. The system values are not editable as these are fixed for an orchestration.
History. Displays a record of the of the values for a variable that is overwritten. For each overwritten variable, click the History icon displayed in its row. The History dialog box lists the orchestration steps where the specific variable is used along with the values. Similarly, the Output tab displays the history of the overwritten output values.
- Last Step section information - Displays the outputs generated from the previous step that was executed in the orchestration.
- Output section information - Displays the accumulative output generated for all the steps in the orchestration until the breakpoint.
For more information refer the guide --> Debugging an Orchestration (Release 184.108.40.206)