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

refactor-after-code-reviews

parent 18469077
......@@ -2621,7 +2621,7 @@ The *Signal API* is a high-level API that enables users to interact with running
That is, it allows a job to expose specific signals (e.g., `soft_stop` to properly finish a job) that can be triggered by users from the *Workflow Execution portal* or *Scheduler portal*.
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*.
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_Signals_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 of two tasks. The first sends a ready notification for the signals specified in the variable SIGNALS'. The second task checks if one signal is received, and if not, the workflow runs in a loop where each iteration lasts one minute.
......@@ -2633,7 +2633,7 @@ This workflow allows users to iteratively wait for the reception of one or more
*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 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 loops until one signal among those specified is received by the job.
*Wait_For_Signals_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 loops until one signal among those specified is received by the job.
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>>.
......
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