This image shows an example of the steps in the JDE_ORCH_Sample_AddConditionBasedAlert orchestration. At the top of the Orchestration design page is the Orchestration field that displays the name of the orchestration, and beneath the field is a description of the orchestration, which can be edited using the Edit Description button. The purpose of this image is to show the grid that contains the steps or components associated with the orchestration. The steps are shown in the Type column in the grid and include a parent rule that has the following children: two cross reference steps, a service request, and another rule. The second rule has the following children: two cross references and a service request. The names of the components for each step are in the Name column. The Action column is between the Type and Name columns, and shows the True or False actions for each step, which identify if the component is invoked based on the whether or not the condition in the rule was met. If a step has a True action, it means the step will be invoked when the condition in the rule is met. If a step has a False action, it means the step will be invoked if the condition in the rule was not met. In the image, all of the cross reference and service request steps have a True action. Only the second rule has a False action. At the end of each step row is an Edit button that you can click to create or modify the component for the step.