Assign to Specified Group Trigger

This trigger is used to assign a workflow to a group. This trigger extends the existing group assignment functionality by allowing more control over when group assignments are made. For example, if a certain step is reachable by several other steps, and it is desired that different groups be assigned depending on which step they came from, this trigger should be used.

Implementation

Declaration

Usage 

Parameters

Group Assigned Parameter

This is a required parameter which specifies the group that the workflow should be assigned to.

To specify the group to which the workflow should be assigned

The name parameter has to be the string "group" while the value parameter can be any group name. If a specified group doesn't exist, the workflow will still be assigned to a group with that name. If such a group is created in the future, the workflow will be available for the users in that group.

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.