Date: Thu, 28 Mar 2024 12:35:04 +0000 (UTC) Message-ID: <589692452.11433.1711629304304@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11432_446530599.1711629304304" ------=_Part_11432_446530599.1711629304304 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Question:
How to run a task manually standalone, that is shown as part of a job ch= ain?
Answer:
The short answer is: please copy your job, assign a new job name and omi= t the attribute order=3D"yes". To save the hazzle of repeatedly ty= ping the implementation you could include the same implementation in multip= le jobs:
<job name=3D"job_1"> <script language=3D"shell"> <include file=3D"my_shell_commands.cmd"/> </script> </job>
The reason for this behavior is: You can run any jobs manually standalon= e if they are not part of a job chain (attribute order=3D"no" or m= issing attribute). The JobScheduler Operations Center interface offers the = respective menu option to start such jobs. However, if a job is part of a j= ob chain, then you would want the complete job chain to be passed through.<= /p>
Moreover, there are some subtle differences between standalone jobs and = jobs in a job chain (which is why you would rarely use the same implementat= ion) that become evident if you use JobScheduler API in your jobs:
The standard jobs and examples of API jobs that you find in the solution= s section of JobScheduler web site support both modes for orders and standa= lone jobs.