Glad you like it and I really appreciate you sharing it. These types of features often go unnoticed because we don't do a great job publishing them out there. When Anamitra talked about adding it, I was extremely excited. There are scenarios where an error is a direct indicator of the health of the system (like a closed database connection error) and customers might want to send this to some sort of monitoring system.
On your scripts, you can simplify it a bit. UserInfo has a method getUserLoginDetails() that returns a UserLoginDetails object that has additional information about the user, including the first & lastname. We use this to build our whoami request for the REST API. You should be able to do something like:
userInfo.getUserLoginDetails().getFirstName()
That way you're operating with data in memory instead of opening a set.
------------------------------
Steven Shull
IBM
------------------------------
Original Message:
Sent: 01-04-2023 10:52
From: Jason VenHuizen
Subject: Triggering automation scripts on errors
For those of you interested, we have published a post on how to launch an automation script when an error occurs in Maximo.
Hopefully you find it helpful.
Sharptree | Blog | Responding to errors with an automation script.Sharptree | remove preview |
| Sharptree | Blog | Responding to errors with an automation script. | While looking up documentation on how to properly obtain the display message for a Maximo exception we came across something quite interesting. In Maximo 7.6.1.2 a hook was added for triggering an automation script every time an error occurs. | View this on Sharptree > |
|
|
#Administration
#Architecture
#Customizations
------------------------------
Jason VenHuizen
Sharptree
------------------------------