Jump Variables and Steps Setting Up Jumps

4-30 Application Administrators Guide for Content Server

4.5.7.3 Side Effects

Side effects are the actions that take place when a revision in a workflow step meets the jump condition. Side effects can include: ■ jumping to another step in the same workflow ■ jumping to a step in a sub-workflow or other Criteria workflow for Criteria workflows only ■ notifying users ■ exiting the workflow ■ setting state information in the companion file ■ releasing a workflow document prior to approval Side effects can be generated automatically by selections on the Script Properties Screen and AddEdit Jump Screen , and custom side effects can be specified in the Custom Effects field on the AddEdit Jump Screen .

4.5.8 Jump Variables and Steps

A jump can include a target step, which tells the workflow where to go to if the content meets the jump condition. The following is an example of a target step that sends the content to the next step in the workflow: wfSetwfJumpTargetStep, wfCurrentStep1 A jump can also include a return step, which tells the workflow where to go if the content is returning from another workflow. The following is an example of a return step that sends the content to the next step in the workflow: wfSetwfJumpReturnStep, wfCurrentStep1 A step name variable, step_nameworkflow_name, is assigned to each step in a workflow. There are two ways to reference a step in a jump: ■ Explicit reference is made to a specific step name, such as EditorMarketing Brochures. ■ Symbolic reference is made relative to the current step and workflow, such as wfCurrentStep-1 previous step or wfStart first step in the workflow. The entry count variable, entryCount, keeps track of how many times a step has been entered. This is part of the default entry script that is updated each time a step is entered. The following is an example of how an entry count variable is used in a conditional statement: if entryCount = 1 The last entry variable, lastEntryTs, keeps track of when the step was last entered. This is part of the default entry script that is updated each time a step is entered. The following is an example of how the last entry variable is used to specify that action should occur if the step has not been acted on within seven days: if parseDatewfCurrentGetlastEntryTs dateCurrent-7 Tip: Use symbolic references rather than explicit step names whenever possible especially when creating a script template. Managing Workflows 4-31

4.5.9 Setting Up Jumps

Before you create jumps in a workflow, you should draw a flowchart and work out all the possible jump scenarios. A recommended method of structuring jumps is to create a main workflow with steps that jump to sub-workflows. See the following example flowchart. After you have decided what jumps need to occur within a workflow, set up the jumps and then test them. You can create jumps directly in an existing workflow, or you can create script templates for jumps that will be reused in different workflows. Figure 4–5 Jump Flowchart

4.5.10 Creating a Jump