Start Schedule Activity

The Start Schedule activity allows a workflow schedule to start during the execution of another workflow.

When you place a Start Schedule activity in a subprocess, step, fault scope, or fault handler, the activity runs when the activity is reached in the process. The Start Schedule activity can have parameters passed to and from it. If output parameters are being used, the activity can be configured to pause the workflow until the schedule that is called has been completed and the value for the output is available.
Note: A workflow will terminate if the workflow that it is calling terminates, regardless of any related preconfigured settings, such as the Wait for the workflow to complete setting.

Settings Tab

You can use the Start Schedule activity to start a preconfigured workflow schedule from the workflow you are currently configuring.

AttributeValueDescription
ScheduleUser-defined

Click the ellipsis button to select the schedule that you want to start.

Click the arrow to:

  • bind the schedule to a directory resource variable, or
  • reset the default value.
When you bind, you must select a template schedule.
Note: If you do not select a template, your workflow will result in a validation error at runtime.
Template ScheduleUser-defined

When you perform a schedule bind, you must select a schedule template that defines the input and output parameters.

Note: The schedule and template schedule must have matching input parameters; otherwise, at runtime, the workflow will fail.

Click the ellipsis button to select a template schedule.

Click the arrow to reset the default value.

Wait for the workflow to completeUser-defined

Select this check box to allow a user to pause a workflow to wait for the 4140workflow that it is calling to complete.

When you select this check box, output parameters from the started schedule are available to bind to the calling workflow.

Note:
  • If a workflow is calling a disabled or terminated workflow, it will also terminate regardless of the status of this property.
  • A workflow cannot be recursive; that is, it cannot call itself.
End the workflow if cancelledUser-defined; Literal

Select this check box to allow a user to end a schedule if the run-time activity is cancelled. Ending the schedule means that it stops running and, if persistence is enabled, terminates it. Cancelling the activity also ends the workflow and any child tasks. This action removes workflow results from the server to save space.

Assignments Tab

When you use this activity to start another workflow, you can override the preconfigured location and personnel assignments by selecting new location and/or personnel resources. You can also bind the assignment to a workflow property. The assignments displayed are related to the selected workflow schedule, as well as the workflow attached to that schedule.

Override

Assignments are configured in a workflow where you bind personnel and location properties. However, when you use this activity to start a schedule, you can override these assignments for the schedule you are starting. Depending on the schedule, you may be able to override assignments at the workflow level or the subprocess level.

The following table describes the available attributes:

AttributeValueDescription
Override check boxUser-definedSelect this check box to allow a user to override the location and/or personnel resources assigned to the schedule you want to start.
LocationUser-defined

Click the ellipsis button to either:

  • edit the bind, or
  • select an alternate location to route the schedule.

Click the arrow to change how the value is set:

  • bind to a variable in the workflow, or
  • choose a literal location resource, or
  • reset the default value.
PersonnelUser-defined

Click the ellipsis button to either:

  • edit the bind, or
  • select other personnel to route the schedule.

Click the arrow to change how the value is set:

  • bind to a variable in the workflow, or
  • choose a literal personnel resource, or
  • reset the default value.