Manual Trigger
Enables manual execution for Processes.
In order to specify parameters for running Processes manually, as well as for Subprocess executions, Manual Trigger is used.
You can learn more about Triggers in general here.
What is Manual Trigger?
Manual Trigger does not contain automation, instead the Trigger is executed only when user starts the Process. In Subprocesses, this is the only type of Trigger available, starting the Subprocess when called by a Process. Parameters can be added to the Trigger, which are then prompted from the user when running the Process, or in the Process development when Subprocess is added.
Usage
To use a Trigger in your Process, add it to your Process canvas, and connect it to the beginning of your Process using a Sequence flow. If you are using multiple Triggers in your Process, all Triggers must connect to the same shape, which is also the first non-Trigger shape in your Process.
Once added to your Process, you can change the Trigger's type to match your requirement and give it a unique name. By default, the Trigger's type will provide a corresponding name for the Trigger. You can then configure the parameters for the chosen Trigger type.
For Manual Trigger, you can configure as many input parameters as you need for your Process or Subprocess execution. Each parameter takes in a key, default value and description. You can use the parameter through Trigger reference values, for example #trigger.data.MyParameter for parameter named MyParameter.
When Process is started using Run once option from the Process list, the parameter values will be prompted from the user before executing the Process. When Call Subprocess shape is used to execute a Subprocess during Process execution, the parameters will be defined within the shape.
Configuration
To set up a Manual Trigger, add the shape to Process canvas and connect it as part of your Process. After that, you can select the Trigger type and configure the parameters for it.
The common parameters available for all Triggers are explained on the Trigger reference page. The following configuration parameters are available for Manual Trigger.
Use for Monitoring Rules
When enabled, this Process becomes selectable to be triggered by Monitoring Rules, whenever their conditions require alerting. Triggering a Process from Monitoring Rules is alternative to sending only an automated email message to alert recipients about a Monitoring Rule hit.
Also when enabled and triggered by Monitoring Rule, additional Trigger reference values are available to use, corresponding to values provided from the Monitoring Rule.
Only available for Processes, not Subprocesses. When used in Process, this replaces any additional input parameters that Manual Trigger normally provides.
Key
When adding a manual parameter to your Process, Key specifies the name for the parameter. It will be displayed as written for the user executing a Process manually or when Call Subprocess shape is used within a Process, and the parameter's value can be used through Trigger reference value as #trigger.data.MyParameter.
Default value
Default value for the parameter, suggested to user launching a Process manually, or when using Call Subprocess shape in a Process. If not replaced by the user, will be the value for the parameter during the execution.
Description
Explanation text field for the value's usage or format. Displayed to the user as a tooltip when exeucting a Process manually, and when using Call Subprocess shape.
Secret
Toggle option that when enabled, will hide the provided value for the parameter from Process Instance and logging. Default value and the input from user when parameter value is prompted will be shown to the user before execution, but logs do not show the value.
Reference Values
In addition to the default Trigger reference values, Manual Trigger provides the following additional values.
#trigger.data (Frends.ExecutableProcess.CaseInsensitivePropertyTree)
Object containing the data from input parameters. Any parameter defined in the Trigger will be accessible as #trigger.data.MyParameter.
#trigger.data.<MyParameter> (String)
When using Manual Trigger, the defined parameters will be available under #trigger.data reference value object as string values. Frends and Newtonsoft library working within the Process executions may deserialize the content in these parameters into other types implicitly, such as converting a date string into a date object automatically.
#trigger.data.monitoringRule (Frends.ExecutableProcess.CaseInsensitivePropertyTree)
When using Manual Trigger with Use for Monitoring Rules parameter enabled, this object will contain the parameters provided by the alerting Monitoring Rule. If Process is triggered manually, this will be null, otherwise it will contain the following fields.
emailRecipients (String[])
List of email recipients defined for the triggering Monitoring Rule.
error (String)
Error message from the Monitoring Rule, explaining why the Rule was triggered.
expectedValue (String)
Contains the Monitoring Rule's condition for triggering an alert, for example if number of matching Instances was expected to be below two, but was three.
name (String)
Name of the triggering Monitoring Rule.
triggeredProcesses (Object[])
List of objects, containing Process's GUID and Agent Group's name for all Processes triggered by the Monitoring Rule.
variableName (String)
Name of the Promoted value that the Monitoring Rule monitors.
Examples
You can learn more about Manual Trigger from the following guides and examples.
Last updated
Was this helpful?