Commit bee99b1e authored by Oana Schiopu's avatar Oana Schiopu
Browse files

refactor-documentation-for-signals

parent 7e0b95b2
......@@ -2626,7 +2626,7 @@ Fill up the Task Variable *SIGNALS*, and use those templates in your own workflo
*Check_For_Signals* is a template workflow that sends a ready notification for all the signals specified in the variable SIGNALS, then loops until one signal among those specified is received by the job.
This workflow is composed by two tasks. The first sends a ready notification for all of the signals. The second task checks if the signals are received and triggers the first task in a loop untill all of the signals are received.
*Wait_For_Signals* also sends a ready notification for all the signals specified in the variable SIGNALS, loops until one signal among those specified is received by the job and then removes the signal.
Unlike Check_For_Signals, Wait_For_Signals workflow contains a single task that sends a ready notification for all of the signals and then checks if the signals are received. This task is executed in loop untill all of the signals are received.
Unlike _Check_For_Signals_, _Wait_For_Signals_ workflow contains a single task that sends a ready notification for all of the signals and then checks if the signals are received. This task is executed in loop untill all of the signals are received.
*Wait_For_Signal_With_Variables* is a template workflow that waits until one signal (with input parameters) that is specified in the variable SIGNAL is added to the set of job signals.
The signal's input parameters have predefined values that can be changed when sending the signal.
The workflow contains a single task that sends a ready nofication for all the signals with input parameters and waits untill all signals with parameters are received.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment