17.7 Steps

Steps are the basic components of a template. Every template must have a start step and an end step. The start step exists by default. You can also add the following types of steps to a template:

17.7.1 Start Step

Every workflow template must have one start step. The transition from a start step is always unconditional.

17.7.2 Manual Steps

This type of step indicates that manual work must be performed. Every manual step in a template must be assigned to a role. The users in that role are notified through a worklist item when an instantiated workflow process reaches the manual step. When a user accepts the worklist item, it is removed from the queues of the other users in that role. For more information about worklists and stepping through a workflow process, see Understanding the Work Item Summary Interface.

The description of the step should indicate what work needs to be performed. The user is expected to perform that work and then acknowledge completion.

A manual step includes the following attributes:

  • Name of step

  • Role

  • Variables

    • Delete

    • Add

  • Description

Variables

The user can also be asked to set one or more variables to appropriate values. Four variable types can be assigned to manual steps: Integer, Boolean, String, and Float. The variable can be set to an explicit default value during the step definition, or the user can set the value at run-time as part of the workflow process. The value can be optional or required.

The value of the variable can be used as part of a conditional transition to determine the path the workflow follows. It can also be used later as part of a conditional transition from a decision step to determine the workflow path.

NOTE:If the value is to be used later as part of a decision step, it should be marked Required.

For example, an integer variable can be set by the user to hold the event rate. Output transitions from the manual step can be defined so that if the event rate is greater than 500, one path is followed, and another path is followed if the event rate is less than 500.

To create a variable:

  1. Access the Sentinel Control Center. For more information, see Step 1 in Accessing the iTRAC Administration Tools.

  2. Click the iTRAC tab.

  3. In the toolbar, click iTRAC > Template Manager.

  4. Click the Add button in upper left corner to open a new template.

    or

    Select an existing template, then click View/Edit.

  5. Right-click Variables in the Process Tree, then select the type of variable to add.

  6. Use the following information to define the selected variable:

    Name: Specify a name for the variable.

    Variable Type: Select the variable type. The options are:

    • INTEGER

    • BOOLEAN

    • FLOAT

    • STRING

    Default Value: Specify a default value for the selected variable. The Boolean variable has only the options of True or False.

    Description: (Optional) Specify a description for the variable.

  7. Click OK to save the variable.

From a manual step, you can set conditional, unconditional, timeout, or alert transitions.

17.7.3 Decision Steps

This type of step selects different exit transitions, depending on the values of variables defined in prior steps. See Manual Steps for the available variable types. The decision step itself is very simple; you can edit only the step name and description. The workflow path is determined by the transitions.

From a decision step, you can set conditional and else transitions. Every decision step must have an else transition and at least one conditional transition. The else transition leads to a workflow path that is followed if none of the criteria for the conditional transitions are met.

17.7.4 Mail Steps

This step sends a pre-written e-mail. A mail step includes the following attributes:

  • Name of step

  • To addressee

  • From addressee

  • Subject of e-mail

  • Body of e-mail

From a mail step, you can set a conditional, unconditional, timeout, alert, or error transition. An error transition should always be included so error conditions can be handled properly.

NOTE:If the first step of a workflow fails without an error transition, the iTRAC process cannot proceed.

17.7.5 Command Steps

A command step executes an operating system command or script (shell, batch, Perl and so on). The name of the command can be explicitly provided or set as a string variable, and parameters can be passed in the same manner. Output from the command can also be placed back into a string variable.

A command step includes the following attributes:

  • Name of step

  • Description

  • Command (Can be explicit or variable-driven)

  • Arguments (Can be explicit or variable-driven)

  • Output Variable

NOTE:The command (a script file that refers to the command) must be stored in the /opt/novell/sentinel/bin/actions directory on the iTRAC workflow server. Symbolic links are not supported

Variables

The command output can also be used to set a variable to the appropriate values. Command steps must use String variable types.

The value of the variable can be used as part of a conditional transition to determine the path the workflow follows. It can also be used later as part of a decision step to determine the workflow path.

For example, a command step can return a value of 0 for failure and 1 for success. This output can be assigned to a variable, and then a conditional transition or a decision step can use this value to determine which workflow path to take.

The command and its arguments can each be specified explicitly by the person designing the workflow or can be set as a string variable. If either the command or the argument is set as a String variable, there must be a previous step in the template where the variable is set to a String value.

From a command step, you can set conditional, unconditional, timeout, alert, or error transitions. An error transition should always be included so error conditions can be handled properly.

NOTE:If the first step of a workflow fails without an error transition, the iTRAC process cannot proceed.

17.7.6 Activity Steps

An activity step is a type of automated step that can be used in a workflow template. Activity steps are created in the Activity Manager and can consist of internal Sentinel operations or external scripted operations. After activity steps are created, the user can select from a library of these activities and include them into a workflow. For more information on creating each type of predefined activity, see Creating iTRAC Activities.

An activity step includes the following attributes:

  • Name

  • Description

  • Activity Assignment

From an activity step, you can set conditional, unconditional, timeout, alert, or error transitions. An error transition should always be included so error conditions can be handled properly.

NOTE:If the first step of a workflow fails without an error transition, the iTRAC process cannot proceed.

17.7.7 End Step

Every workflow template must have an end step to complete every branch of the workflow path.