Run Conditions Dialog Box

This dialog box enables you to define which attributes must match for a component or flow to run.

To access	In the Test Plan module, select a flow or a business process test. Select the Test Script tab. Select the component or flow for which you want to add the run condition and click Add/Edit Run Condition .
Important information	You can only define one run condition per business component or flow. If defining a run condition for a component with an output parameter that has more than one iteration, ALM uses the value from the corresponding iteration. Tip: In some cases, it may be preferable to define different flows, rather than use a large number of run conditions within a particular flow.
Relevant tasks	How to Learn Flows and Business Process Tests
See also	Criteria for Determining if a Component Can Be Reused

User interface elements are described below (unlabeled elements are shown in angle brackets):

UI Elements	Description
Run If	Lists the parameter types defined in that entity. The following types are available: Input parameter. Available for components and flows, only if one or more input parameters are defined for this entity. Output parameter. Available for components and flows, only if one or more output parameters are defined for one or more of the previous entities. Flow parameter. Available for components, only if one or more flow input parameters is defined. Test parameter. Available for components and flows, only if one or more test parameters is defined. Note: When creating a run condition on a parameter that contains a dynamic date value, define the run condition as a static date (for example, 12/10/2011), which is compared to the actual date used in the run.
<parameter name>	Lists the available parameter. Encrypted parameters are not listed. Parameters with encrypted values cannot be chosen from the list when defining run conditions. It is recommended that you do not use parameters whose default values are encrypted when defining run conditions.
Is	Lists the operators that need to be met for the component to run. The following conditions are available: equal to not equal to less than less than or equal greater than greater than or equal
<value>	Enables you to enter the valid value for the condition.
Else	Specifies what to do if the condition is not met. The following options are available: Skip to the next component and continue. If the condition is not met, the entity for which the run condition is set does not run, and the test/flow run continues with the next entity. When running with the Manual Runner, the test results list the run status for the component / flow with the run condition as Ignored. When running with the Automatic Runner, the test results list the run status for the component / flow with the run condition as Not Run. End component / flow run and fail. If the condition is not met, the entity for which the run condition is set does not run, and the test/flow run continues with the next entity. The status of the run as Failed. Because the status of the run is set as Failed, the execution of the flow or test might be stopped, depending on the Failure condition set for the entity. For details, see Set failure conditions for components and flows. Go to... If the condition is not met, the entity for which the run condition is set does not run, and the test / flow run continues with the entity you choose. You can "go to" subsequent components, flows, and groups. The entity you choose must appear after the current entity in the test; For example, you cannot go to a component that already ran. To change the entity to go to, click Change. Change appears only after you have already selected a "go to" entity before. The status of the test run is not affected. When running with the Manual Runner, the test results list the run status for the component / flow with the run condition as Not Run. When running with the Automatic Runner, the test results list the run status for the component / flow with the run condition as Not Run. Note: If a run condition is not valid, the run condition link is displayed in red. This can happen, for example, if a reference parameter was deleted, a parameter value was encrypted, and so on. Delete the run condition and define a new one. Tip: Your selection in the Else box applies only if the run condition is not met. To specify whether to continue or end the entire run if a component run fails, set the failure condition for the component. You do this in the Test Script tab of the Test Plan module. For user interface details, see Test Plan Module Menu and Buttons for Business Process Testing.
Summary	Displays a text description of the run condition you have defined for the component or flow.