Date: Fri, 29 Mar 2024 12:10:24 +0000 (UTC) Message-ID: <942882856.12857.1711714224372@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12856_886699505.1711714224372" ------=_Part_12856_886699505.1711714224372 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
JobScheduler comes with two types of job that can be used to carry out w= orkflow automation tasks - Standalone Jobs and Order Jobs.
Standalone Jobs are simple to configure but are neither as flexible nor = as powerful as Order Jobs. However, Standalone Jobs are quite often used in= simpler job scheduling environments and where users have migrated from oth= er job scheduling systems which use a similar concept such as TWS.
The following article provides a step-by-step introduction to creating a= nd using Standalone Jobs:
Order jobs and job chains are one of the most powerful arguments for imp= lementing JobScheduler, bringing an efficient, modular approach to implemen= ting workflow automation.
We have a number of articles providing a step-by-step overview of Order = Jobs and Job Chains.