This is a simple example of how to schedule Orchestrations. Johan creates a batch post with notification and schedule this to run every 10 minutes during office hours.
In this step-by-step guide you will learn how to:
– Get the Number of batches in Error
– Create Rule not Zero
– Create Notification NT_BatchesInError
– Create the ORCH_PostInventoryBatches Orchestration
– Create and start your schedule
source
Orchestration has really made life easy as far as creating dependent UBEs flow. When the Report Service Request is executed then it gives all related attributes which we see in WSJ like Report Name, Report version, Job Number, Job Status (whether Done or Error) etc. E.g. "ServiceRequest1": {
"reportName": "R03B168",
"reportVersion": "XJDE0001",
"jobNumber": 341345,
"executionServer": "HEISD56JDE",
"port": "6017",
"jobStatus": "D",
"objectType": "UBE",
"user": "PRASAS04",
"environment": "JDV920",
"submitDate": "20201006",
"lastDate": "20201006",
"submitTime": 5622,
"lastTime": 5627,
"oid": "R03B168_XJDE0001",
"queueName": "QBATCH"
}
Only thing to keep in mind that we need to toggle off the "Fire and Forget" option in Report Service Request.
We can make use of the job status and create a rule which will execute the next UBE only if the previous UBE is executed normally i.e. with status "D". In this way we can add as many UBEs as we want in the cascading form.