Technical Blog Post
Scripting with Maximo
- Customizing MBOs through save-point and initialization-point validations and actions and MBO field validations and actions.
- Customizing workflow, escalation, conditional UI, menus, and push-button actions via scripted actions and conditions.
It is important to understand that the Automation scripts are a server-side artifact, as opposed to a client-side one. So all your scripts are executed on the server side as opposed to say in the browser.
The cool part about scripting is that you can use it without writing a line of Java code, or without restarting the server or rebuilding the EAR file. We understand that sometimes you need to customize using MBO code or the Maximo SDK and the scripting framework does not remove that power. You still have access to all of Maximo APIs as well the MBO instances in context. You can use a MBO to access any related MBO or set and can call all public APIs, such as those to invoke a Web service or a send an email from a script.
For more information, read the "Scripting with Maximo' best practices document located here. The document includes some scenarios and examples to help you get started with Automation Scripting. And please leave comments about the document to help us improve it and answer your questions.