Hi Amey
Just a not 100% validated potential solution before I finished my first coffee.
Instead for promptsets go for object variables. MODIFY_TASK can set them as well (you likely will be using MODIFY_TASK if you dynamically build workflows right?). There won't be a popup, asking for the variable value.
In case that you have some edge-scenarios where the input must be interactively queried, you might find a trick using AE script to verify whether the variable was set already or whether the starting context (like is it a restart scenario or not) requires to re-:READ the variables or not.
------------------------------
☎️ Swisscom Automation Engineer & 🧙 PE Membership Creator
Automic Kurse, Tutorials, Tools und mehr auf:
https://membership.philippelmer.com/Zwei Wochen kostenlos testen!
------------------------------
Original Message:
Sent: Jan 12, 2022 12:20 AM
From: Amey .
Subject: Designing JOBS using template
Hi Pete,
We are using the same JOBS template , but when we add it in a workflow we are providing Alias names to the jobs so it will differentiate and we can track them or monitor them.
Even in notification we are assigning alias names using GET_STATISTIC_DETAIL(&UC_CAUSE_NR,ALIAS) for the job. and which is solving our purpose
But due to Prompts set being used in the JOBS we are observing during resubmit of a job, a notification is pop up for modifying it. which is giving us a problem
whenever we are trying to resubmit the job.
Also as due to the prompt set added to the Job template it is not allowing us to perform Bulk resubmit and Bulk Unblock options.
Regards,
Amey Deshpande
Original Message:
Sent: 1/11/2022 7:24:00 PM
From: Pete Wirfs
Subject: RE: Designing JOBS using template
The drawbacks of running 200 jobs through a single JOBS object include;
It will be harder to isolate the run history for any particular application.
All 200 jobs will share the same documentation tab.
You might find there are other AE features that you would like to use on some but not all of your jobs.
For these reasons I would consider cloning your JOBS 200 times. We typically clone, except for common utilities like FILE.COPY, FILE.DELETE, etc.
Regarding how to bulk resubmit/unblock, I think the user interface already supports some multi-select operations in the ProcessMonitoring view? And it also might be possible to write a script to automatically perform these operations in bulk? I would also be thinking about ways to stop Automic from initiating more tasks when one of these serious faults occur, for instance when a serious fault is detected close the queues for example.
------------------------------
Pete Wirfs
SAIF Corporation
Salem Oregon USA
Original Message:
Sent: Jan 11, 2022 05:25 AM
From: Amey .
Subject: Designing JOBS using template
Hi Team,
We are in migrating jobs from existing scheduler to Automic Workload Scheduler (AWA) and we have 4-5 Major application which consist of more that 200 jobs as daily workflow having various dependency.
Scenario - All 200 plus jobs scripts are present on a specific location on a server. and we need to trigger those based on specific time events and interdependency.
Solution which we have consider - We have created prompt set to access the script location by creating a single job template and adding the same Job template 200 plus times in a workflow and just passing different script name as prompt set text value and created interdependencies among them.
Problem we are observing - This solution is working perfectly fine on all days, but on a bad day if database server goes down or disaster recovery situation we observed multiple jobs get fail and due to prompt set we can not able bulk resubmit or bulk unblock those failed jobs .
So we need help on building a solution where with minimum development effort we can design workflows having 200 plus interdependent jobs. and can use bulk resubmit or bulk unblock features on a Disaster situation.
Thank you in advance
Regards,
Amey Deshpande