Other scripts

You can automate the assigning of service requests to service groups, automate communication by using a custom role, and use Maximo® Business Rules (MBR) language in scripts.

Example: Automating assigning service requests to service groups
The development team at a manufacturing facility is asked to implement a business rule into the production system. When a pipeline leaks in the facility an operator creates a service request to report the leak. The pipeline volume determines the service group that is assigned to the service request. The development team creates a script that assigns the service request to the appropriate service group. If the volume of the pipeline is greater than a specified limit, the team must also ensure that a work log is created.
Example: Automating communication by using a custom role
The development team at a large maintenance organization must design a process that notifies people when quantities of certain parts are running low. Unexpected disruptions to the supply chain, for example due to adverse weather or industrial disputes, can affect the availability of parts for scheduled maintenance activities. With advance warning of shortages, work supervisors can reschedule non-essential work that requires these parts, conserving supplies and minimizing the effect on schedules.
Example: Maximo Business Rules scripts
Several examples are provided to illustrate how to use Maximo Business Rules (MBR) language in several common scripting scenarios.
Action launch point
The Maximo actions framework has a built-in library of actions which can be run from workflows, escalations, user interface menus, buttons and many other components. However, you might need actions that aren't included in this library. Scripting addresses this concern as you can script an action by using Jython and JavaScript.
Condition launch point
Maximo conditions are based on the javacc parser that is used in workflows, conditional user interfaces, and others. One aspect of custom conditions lets you write a condition by using Java code, in case the condition is complicated enough to be encoded by using the javacc-based condition grammar. This launch point lets you avoid Java coding and enables you to attach a scripted condition to workflows and conditional user interfaces.
Scheduling automation scripts to run as part of cron tasks
Cron tasks are jobs that run automatically on a fixed schedule on the application server. For example, the ESCALATION cron task processes escalations to ensure that critical tasks are processed on time. You can use several predefined cron tasks and you can also define new cron tasks. For new cron tasks, you must provide a Java™ class implementation that contains the business logic that is executed on a schedule.
Adding scripts that run as asynchronous jobs
You can add scripts that can run as asynchronous jobs in the product. Use the asynchronous job framework to submit jobs that need to be run one time asynchronously, such as when you want to run something quickly in the background.
Role automation scripts
Roles play an important part in workflow and communication templates. Roles often resolve to a specific person or email based on data in the record, such as the supervisor on the work order. In those cases, this functionality is not needed.
MXException automation scripts
MXException provides automation script developers a script point for MXException to run the script when an MXException is thrown from product code. This feature primarily helps add more information to an existing message, for example, adding a username, someone who caused the exception, to the message. This can also help in taking some automated action geared towards serviceability, like sending an email alert to an administrator.
Formula functions

Parent topic: Automation scripts