Process driven messaging service: Difference between revisions

Content deleted Content added
Dk3298371 (talk | contribs)
m cleaned up second paragraph.
Tag: gettingstarted edit
Bosbec (talk | contribs)
m Expanded the section jobs
Line 22:
 
=== Jobs ===
{{Expand section|date=March 2014}}
A job creates something such as a task (e. g., sending a message) or affects Standard Objects (e.g. way metadata in a unit). It is a task describing what the system should do and can be several things. A job, when activated, can lead to the execution of another job (for instance: message delivery). It represents what a system does with the data, an activity within the system ___domain.
 
Jobs provide a means to encapsulate a process. A Job is a configuration representing input options, the steps in the process, a filter expression that matches the nodes where those steps will execute, and execution control parameters that specify if steps are run in parallel. One might find certain command executions are done repeatedly, and perhaps, represent what has become a routine procedure. Routine processes need to be encapsulated and become the basis for other routine procedures.
 
=== Triggers ===