Assign To Workflow Owner Trigger

This trigger assigns the next step (the step that will occur as a result of this action) to the user that initiated the workflow. This is particularly useful in the case of a "reject" action where the next step should always be assigned to the original user rather than relying on the current step owner to determine the appropriate assignation.

Implementation

Declaration

Usage

Please remember to use this on the step before the step that is desired to have step assigned to the workflow owner. 

Parameters

None

Adding a Workflow Trigger

The Cascade Server workflow builder utilizes centrally managed triggers.  For a trigger to be available in a workflow created by the Workflow Builder, the trigger must first be defined and assigned a name in the system-wide trigger base.  Defining triggers in this way allows the Java files that contain each trigger’s functionality to be referenced later in the workflow definition.

If a new custom trigger has been written or Cascade Server has been upgraded without including the default database, the new triggers will need to be added before they become available in the Workflow Builder.

To add a workflow trigger:

  1. In the Administration area, select ‘Workflow Definitions’.
  2. Click ‘Manage Workflow Triggers’.
  3. All currently available triggers in the default database are shown, along with the ‘Add a Trigger’ field.
  4. Type in the name of the new trigger and click ‘Submit’.
  5. The new trigger will now appear on the list of available triggers and will be available for use within the Workflow Builder.

manage workflow triggers

Adding a trigger using this interface ensures that the triggers will be defined in all workflows created using the Workflow Builder.  For workflows created without the Workflow Builder, triggers must be defined individually for each workflow.