Using the Queue instruction to run an activity asynchronously

Parameter

Description

Type Queue followed by one space and the Activity Name (second key part) of the activity to execute.

Optionally, you can identify the Applies To key part of the called activity explicitly, using the format:

Call Data-Admin-Operator-ID.Analyze

Call MyCo-Finance-Work-Form990.Validate

The explicit class format causes rule resolution to bypass all class hierarchy searches — the activity must be present in the specific class identified before the dot. (Other aspects of rule resolution operate normally.) Because use of explicit class names can introduce inflexibility, complicate debugging, and reduce opportunities for rule reuse, avoid this format whenever possible. When you save an activity, Queue steps that use this format cause a rule warning.

Check to share the contents of the current activity with the called activity (a form of call-by-reference). If checked, ensure that all needed input parameters of the called activity are present with an appropriate value on this page before the Queue instruction occurs.

Use care if you select this option. As both the calling and calling activities can update any Out parameter values on a common, shared parameter page, changes to the parameter page may occur in any order.

If Pass current parameter page is not selected, enter values for the input parameters of the activity. Input parameters that are required to have a non-blank value are marked with an asterisk.