Hi Krum,
Thanks I understand now, you are right.
In Time&Dependencies Tab of the SCRI object the Status was
ENDED_OK Else Skip.
Tt means that the SCRI was never launched so no postconditions started.
To test, I changed the ENDED_OK by ENDED_NOT_OK and the script is running now.
For the point below :
"Execute the CALL object when the dependencies are not met (Abort + Execute another object)"
I don't want to do it like because if in the dependencies I have 3 Taks for example, then I will receive 3 emails.
As it is the same workflow I want to receive only one email even if the 3 jobs failed.
So this is why I wanted to do it with the script, like that in postconditions It will trigger only one email.
Based on what you said,I can do it the opposite way,
In the script I test if
at least on status matches ENDED_NOT_OK/ANY_ABEND,
if yes I run the script and I make the script failing in UC4, then it will trigger the postconditions and send the email
and if No, I skip the script.
Unless there is another way to do it.
thanks again
------------------------------
[JobTitle]
[CompanyName]
[State]
------------------------------
Original Message:
Sent: May 10, 2022 02:54 AM
From: Krum Ganev
Subject: Notification call in postcondition
Hello,
From what you've described i would say that your logic is incorrect.
The dependencies between your jobs and the script with the post-condition are set to "ENDED_OK else ABORT" right?
Hence the SCRI task does not start at all as the dependencies are not met and the whole workflows goes in abend state ENDED_JP_ABEND.
As the task does not execute at all, the postcondition is also not triggered.
Best method would be to trigger the email notification on the objects that actually is failing (in your case the jobs) rathar than on the next task.
OR
Execute the CALL object when the dependencies are not met (Abort + Execute another object)
------------------------------
------------------------------
Automic SME @ DXC.Technology
------------------------------
Original Message:
Sent: May 09, 2022 05:02 AM
From: Benny Blanco
Subject: Notification call in postcondition
Hello,
I'm trying to sent a notification using a CALL object in Postconditions but it does not work.
I've 3 jobs connected to a script object, if one of them is in failure I'll failed the script.
Script is failed because I've have dependencies configured, so if one of the 3 jobs do not finish ENDED_OK then I abort the script.
So the script end up with status :
ENDED_JP_ABEND - not executed due to abnormal Workflow end.
In the script I've have a postconditions saying :
------------------------------
[JobTitle]
[CompanyName]
[State]
------------------------------