Hi Maximo Wizards!
I encountered a strange thing. I was updating an automation script that is launched on WORKORDER.save, after commit. The important point here is that it is after commit. I like to use service.error to debug my scripts (because it acts as a breakpoint). However, for this specific scenario, my service.error was never being thrown!
I noticed that service.error messages are never displayed on after-commit launchpoints. If I change the launcpoint to before save, then the error is displayed.
Has anyone encountered this issue before? I assume the error is not displayed because the transaction has already been committed to the database, therefore the error does not stop the object being saved? But I would assume that the error should still be displayed and my script should be stopped, regardless of whether the transaction was committed.
Thanks!
------------------------------
Aneesh Joseph
Director and Solutions Architect
objec3d
Melbourne, Australia
https://www.objec3d.com------------------------------