The MRT rule is already there onto the object that is the external dependency (Object B).
So we are alerted when that job (Object B) is running long. That is a different application object, so that application would be notified when that object runs long.
Object A belongs to another application and we would like to have a mechanism where we want to alert when object A is actually waiting on external dependency (object B).
So the alert should basically say "Object A is running long because it is waiting on the external dependency Object B to be completed"
How to achieve that? Any ideas?
Original Message:
Sent: 06-26-2019 11:58 AM
From: Pete Wirfs
Subject: How to retrieve the name of the external dependency in a job plan?
Seems to me it would be better to just add an MRT rule onto that object that is your external dependency.
In our case, we developed a generic MRT alert object that after sending the initial alert, launches another object that will run 15 minutes later to audit the state of the long running object and either send a "object has completed" alert or "object is still active" alert. I can probably share it if you are interested.
Original Message:
Sent: 06-26-2019 11:30 AM
From: Esther Sekar
Subject: How to retrieve the name of the external dependency in a job plan?
We have instances where we set up Maximum Run Time settings and send alerts once the MRT has reached.
If it just an object that is running long, we send out an alert with the object name by retrieving the name using the UC4 Script function (SYS_ACT_PARENT_NAME).
There are cases where we set up MRT for external dependencies that are running long.
Is there a way to retrieve the name of the external dependency? so that the alert can be generated with that name.