Defining Exceptions Flows FAQS

1. What is the Exceptions tab in the Load Plan Editor?

• The Exceptions tab in the Load Plan Editor is where you define the exception handling flow. It contains a list of Exception Steps, each with a hierarchy of steps for managing errors and failures during Load Plan execution.

2. How is the Exceptions tab different from the Steps tab in the Load Plan Editor?

• The Exceptions tab is similar to the Steps tab but with key differences:
• There is no root step for the exception step hierarchy. Each exception step is treated as its own root.
• The exception steps do not have the Exception Handling properties group. A failed exception step cannot trigger another exception step.

3. How do I create an Exception Step?

• You can create an exception step using:
• Add Step Wizard: Select Add Step > Add Step Wizard from the toolbar, then choose Exception as the step type and provide a name.
• Quick Step Tool: Choose Add Step > Exception Step from the Load Plan Editor toolbar, and a new exception step will be created, which you can rename.

4. Can I modify the name of an Exception Step after creating it?

• Yes, the default name “Exception” can be modified in the Steps Hierarchy table or using the Property Inspector.

5. How are Exception Steps organized in the Exceptions tab?

• Exception steps are organized in a hierarchy under their own root step. You can add and arrange steps under each exception step to create a flow for error handling.

6. What happens if an Exception Step fails?

• If an exception step fails, it will not raise another exception step, as the exception steps do not have the Exception Handling properties group.

7. Can I use the same steps for both regular steps and exception steps?

• Yes, you can use steps like Serial, Parallel, Run Scenario, and Case in the Exceptions tab. However, these steps do not have Exception Handling properties and cannot trigger another exception step.

8. Can I define complex flows of exception handling?

• Yes, you can define complex exception flows by adding and organizing new steps under each exception step. This allows you to create customized error handling for different scenarios.

9. What types of steps can I add under an Exception Step?

• You can add Serial, Parallel, Run Scenario, Case, and other steps as part of the exception flow. However, remember that these steps will not trigger additional exceptions if they fail.

10. What are the main differences between an Exception Step and a regular Load Plan Step?

• The main differences are:
• An exception step does not have Exception Handling properties.
• If an exception step encounters an error, it will not raise another exception step.
• The hierarchy of exception steps is separate from regular steps and does not have a root step.