Commit 7c548b6e authored by Oana Schiopu's avatar Oana Schiopu
Browse files

refactor-after-reviews

parent c8a8065a
......@@ -2624,16 +2624,17 @@ You can try the <<_examples_2,examples>> below to better understand how it works
In summary and for simple use, just go to <<_proactive_studio, ProActive Studio>> and use the predefined templates in the _Controls_ bucket, _4. Signal Templates_ project: for example: *Check_For_Signals*, *Wait_For_Signals*, *Wait_For_Signals_Reactive* or *Wait_For_Signal_With_Variables*.
Fill up the Task Variable *SIGNALS*, and use those templates in your own workflow to be able to receive input from, for instance, the Workflow Execution portal or Scheduler portal.
*Check_For_Signals* is a template workflow composed by two tasks. The first sends a ready notification for all of the signals specified in the variable SIGNALS. The second task checks if one signal is received, and if not, the workflow iterates in a loop where each iteration lasts one minute.
*Check_For_Signals* is a template workflow composed of two tasks. The first sends a ready notification for the specified signals in the 'SIGNALS' variable. The second task checks if one signal is received, and if not, the workflow runs in a loop with one-minute iteration duration.
This workflow allows users to do an iterative processing, and decide at each iteration to continue this processing or not, i.e., (i) declare being ready to receive one or more signals, (ii) do some processing, then (iii) receive signals and decide whether to continue the processing or not.
*Wait_For_Signals* is a template workflow that contains a single task, which sends a ready notification for the signals specified in the variable SIGNALS, then checks if one or more signals are received by the job. If not, the workflow iterates in a loop where each iteration lasts one minute.
*Wait_For_Signals* is a template workflow that contains a single task, which sends a ready notification for the specified signals in the 'SIGNALS' variable, then checks if one or more signals are received by the job. If not, the workflow iterates in a loop where each iteration lasts one minute.
This workflow allows users to iteratively wait for the reception of one or more signals, then trigger some processing.
*Wait_For_Signals_Reactive* is a template workflow that sends a ready notification for all the signals specified in the variable SIGNALS, then waits until one signal among those specified is received.
This workflow contains no loop. It performs a blocking wait, then immediately triggers some processing at the reception of a signal.
*Wait_For_Signals_Reactive* is a template workflow that sends a ready notification for all specified signals in the 'SIGNALS' variable, then waits until one signal among those specified is received.
This workflow contains no loop. It performs a blocking wait, then immediately triggers some processing at a signal reception.
*Wait_For_Signal_With_Variables* is a template workflow that deals signals having input parameters. It contains a single task that sends a ready notification for all the signals (with input parameters) specified in the variable SIGNALS, then waits until one signal (among those specified) is received. The signal's input parameters have predefined values that can be changed when sending the signal.
*Wait_For_Signal_With_Variables* is a template workflow that uses signals having input parameters. It contains a single task that sends a ready notification for all the signals (with input parameters) specified in the variable SIGNALS, then waits until one signal (among those specified) is received.
The signal input parameters have predefined values that can be changed when sending the signal.
At a more detailed level and advanced use, the Signal API allows jobs and users to exchange signals using a communication channel provided by the <<_task_synchronization_api,synchronization API>>.
The typical usage scenario of the Signal API is the following:
......
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