Trigger action task

A Trigger Action task performs a specified action on specified records.

If there are multiple records for a Trigger Action task to perform an action on, the action is performed on all of the records, one at a time. If the actions launch asynchronous workflows, depending on how IBM® Maximo® Real Estate and Facilities and its environment are configured, some or all of the launched workflows may run at the same time.

Note: You can set the Trigger Action task to allow the asynchronous event to be run by a user other than the currently logged in user.
The properties form for a Trigger Action task is organized into three sections. Here are descriptions of the fields in the first section:
Label
This is the label used to identify this task. This field's text appears on the shape in the drawing that represents this workflow task. Use the standards in Workflow naming conventions.
Description
A description of this task goes in this field.
Action
This field is a drop-down list of the actions that can be performed on the kind of records specified in the Records section of this task's properties form. The action specified by this field is the action that this task will perform on its records.
Note: The state-transition temporary support for validations should avoid using Trigger Action tasks that call state transitions, which call custom actions (such as platform Enterprise JavaBeans (EJBs)). The reason is that some of the custom action implementations can save temporary data as part of their work.
Parameters

The Trigger Action task can be used to pass parameters to asynchronous and synchronous workflows as follows:

  • You can pass parameters to an asynchronous workflow, both runtime and design-time.
  • You can pass parameters to a synchronous workflow that is triggered from a sub action on a state transition.
  • Parameter names must be exactly the same in the Trigger Action task and in the subsequently-called workflow. The order does not matter.
  • Parameters are supported in Object Migration and Workflow CLD files (text export).
  • You cannot pass a parameter on the User Action task nor custom action through classes or EJB.
  • There is no support or validation for finding callers on the asynchronous workflows. Temporary data or in memory smart object (IMSO) data are not supported. Return parameters are not supported.
Formulas

Defines the formula recalculation behavior on this task when the record is saved. The default is Disable Auto Recalculation. To change the value, click the recalculate formulas icon.

The three possible values are as follows:
Recalculate as Needed
Recalculates most formulas only if any input value of the formula changed during the task's activities. Extended formulas that contain query and/or association tokens are recalculated on every save.
Disable Auto Recalculation

Extended formulas that contain query and/or association tokens are not recalculated. All other formulas are recalculated only if any input value of the formula changed during the task's activities.

Extended formulas that contain query and/or association tokens can take longer to calculate, so this option is an available performance optimization for isolated use cases.

An example of an appropriate use of Disable Auto Recalculation is within a DataConnect task that is importing a large number of space records. You may wish to delay any floor/space rollup recalculations until after all the space records have been imported.

Recalculate All

Forces every formula to be recalculated during the record's save.

Selecting Recalculate All may slow performance.

An example of an appropriate use of Recalculate All is in a data cleansing workflow that refreshes formula values in the database that are stale for whatever reason. For example, if the definition of a formula changes for a business object, existing records may contain incorrect values as a result of the change. You may wish to use Recalculate All in a maintenance workflow that runs through the records and updates their formula values.