Hi Steven,
Thank you very much, all the responses from you 3 experts are very instructive. I really appreciate it.
I am on a task to write an auto script to replace a java function for virtual asset removal, it is an action that responses OK button in a dialog in a customized WorkOrder application. The error will occur if I modify (and then saved) another field in the work order before the virtual asset removal. I think it is not a good time to do it.
My conclusion is that, on Maximo 7.6.1.*., even MAS 8 early version, it is not the time to replace all the customized java classes, such as bean classes, those involve UI interaction, with auto script right know. Am I correct?
In addition, I would like to ask another question. Since Maximo uses java behind, is the automation script in Jython better than in Python? Currently our script is *.py.
Thank you again.,
Eric
------------------------------
Eric Zuo
San Francisco Bay Area Rapid transit
------------------------------
Original Message:
Sent: 05-24-2023 10:35
From: Steven Shull
Subject: Possible to eliminate any customized java class in Maximo by automation scripts?
If you haven't seen it already, please look at our wiki on automation script development. https://ibm-maximo-dev.github.io/maximo-autoscript-documentation/
There's a lot more I'd like us to get added to it but finding the time to add more documentation is always a challenge. If there are particular areas you'd like to see in the documentation let me know.
As for what you can and can't do with automation scripts, as Jason & Mark explain it will depend on what you are trying to do. Around business objects we have a pretty robust set of capabilities. We started really adding some UI interaction capabilities in 7.6.1.X. In the latest MAS release (Manage 8.6), we started the work to add more hooks around bean classes. It's disabled out of the box and we haven't built the documentation around it yet, but I wanted to make it known that it is an area we're continuing to invest. There are areas around serviceability that we're focused on improving as well. For example, we added a way to automatically clean up sets that were opened via an automation script and weren't properly closed. This was added in Manage 8.5 or 8.6 and disabled by default (system property mxe.script.autocleanup). We added better support for testing automation scripts. And we have a lot more coming still.
------------------------------
Steven Shull
IBM
------------------------------