Toggle menu

signalEvent

Signals any executions that are listening for a specific signal.

A specific execution ID can be specified and updated process variables can also be included.

Parameters 

NameTypeDescription
executionIdStringIf set, only signal the specified execution. Note that executions are not the same as instances, see the final section of the Messages and Signals knowledge base article for an example
fileReferencesObjectMap of field names to file reference objects. The supplied files will be referenced by the workflow and remain available until it completes. For an example see the startProcess function
proxyUserIdStringCan be used instead of userId
replaceExistingFilesbooleanTrue by default. If this property is true, files named in the "fileReferences" parameter replace any existing files provided under that name which will no longer be referenced by the workflow. Otherwise the new file and and any previous files referenced under that name will be kept
signalNameStringThe name of the signal event
userIdStringThis value will be logged in the signalName_received process variable. It needn't be the name of an actual user in iCM. See the Process Variables articles for more information
variablesObjectAn optional map of variables to add to the execution
signalName and either userId or proxyUserId are required, other parameters are optional
Last modified on January 23, 2024

Share this page

Facebook icon Twitter icon email icon

Print

print icon