TriggerWF

Build 1501 on 14/Nov/2017  This topic last edited on: 22/Mar/2016, at 17:01

Description

Creates or removes triggers executing a workflow when something changes in the system (GET)

Parameters

Remove

If specified the triggers are removed, otherwise they are created

Ids comma-separated database ids

Database id(s) of the object(s) to monitor for changes

Conditions string

Either a GNQuery search expression or the name of the search configuration object containing the search conditions - all the objects returned by the search will be monitored by the trigger.

Pars list of name-value pairs in the format 'name1:value1;name2:value2...'; e.g. 'folderId:30;cmd:up' to define a 'folderId' parameter with value 30 and a 'cmd' parameter with value 'up'.

Optional parameters used to replace variables in the GNQuery search expression or in the search conditions

Mode trigger mode

What to monitor: "Object" for changes in the objects, "Referencing" for changes in the set of referencing objects, "CheckOut" for check-out/check-in operations, "ObjectIndex" for full-text indexing of objects, "ReferencingIndex" for full-text indexing of referencing objects, "ReferencingObject" for changes in the referencing objects. Optional, defaults to "Object" (monitor objects changes)

Attr string

Attribute to monitor. Compulsory if monitoring referencing changes, optional - and defaulting to 'any attribute' if monitoring object changes and check-out/check-in operations.

Name string

Workflow name

WFPars list of name-value pairs in the format 'name1:value1;name2:value2...'; e.g. 'folderId:30;cmd:up' to define a 'folderId' parameter with value 30 and a 'cmd' parameter with value 'up'.

Optional extra parameters to pass to the workflow. Ignored when removing triggers.

Priority integer

Execution priority for the workflow. Workflows with higher priority values are executed first. If not specified it is assumed 0 = minimum priority. Ignored when removing triggers.

Profile string

Execution profile for the workflow. The profile configuration determines the number of retries and the log actions to take after execution. If not specified the default profile will be used. Ignored when removing triggers.