oqapi/webgui
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

The concept of "realtime" workflow has been eliminated. Instead all workflows are now realtime (synchronous), and roll over to be asynchronous if they cannot complete succesfully and immediately.

Browse source
This commit is contained in:
JT Smith 2008-05-03 05:38:13 +00:00
parent 51019e5dca
commit 01d9af6222
15 changed files with 105 additions and 72 deletions
Download patch file Download diff file Expand all files Collapse all files

17
lib/WebGUI/i18n/English/Workflow.pm
View file

@ -62,24 +62,17 @@ our $I18N = {
message => q|Parallel|,
},
'realtime' => {
message => q|Realtime|,
},
'mode' => {
message => q|Mode|,
},
'mode help' => {
message => q|The mode of a workflow determines the precidence of when and how a workflow is run.
<p><b>Parallel</b> workflows asynchronously run as many instances of the workflow as there are in existence.</p>
<p><b>Singleton</b> workflows asynchronously run exactly one instance of a given type at any one time, and if a
message => q|The mode of a workflow determines when and how a workflow is run.
<p><b>Parallel</b> workflows run as many instances of the workflow as there are in existence.</p>
<p><b>Singleton</b> workflows run exactly one instance of a given type at any one time, and if a
new workflow of that type is created while the original is running, it will be discarded.</p>
<p><b>Serial</b> workflows asynchronously run one workflow instance of a given type at a time, in the order it was
created.</p>
<p><b>Realtime</b> workflows synchronously (immediately) run all activities associated with it, because of this
not all triggers support realtime workflows, and you can't use any asynchronous workflow activities (like
version tag approval) in realtime workflows.</p>|,
<p><b>Serial</b> workflows run one workflow instance of a given type at a time, in the order it was
created.</p> |,
context => q|the hover help for the mode field|,
lastUpdated => 0,
},