scripting

Speedup Maximo scripts development with VSCode plugins

When developing automation scripts I always like to have a shared filesystem with all the latest automation scripts. This allows me to use code editors or to better navigate across the entire code and eventually use source code versioning tools like Git or CVS. One technique I usually use is to use Notepad++ and edit […]

Display custom icons in application’s list view

Last week, a client asked if it was possible to display a warning icon on asset records based on certain business rules. Initially, this request posed a challenge, but I was able to find a solution to implement it effectively. The technique is based on a non persistent attribute populated an automation script that evaluates […]

How to get application name in automation scripts

IBM claims the you can use the implicit variable ‘app’ in automation scripts if you need to know the name of the Maximo application that is currently running. Unfortunately, this technique works only on the main object on which the application is defined. As an example, try to define the following automation script on the […]

How to create follow-up Work Order with script

Maximo provides a useful action in many applications to create a follow-up work order or a linked service request from many applications. The same result can easily be automated using the WO.createWorkorder() or the Ticket.createWorkorder() API methods. The standard WO2WO or TICKET2WO crossover domains can also be used to copy some attributes from the source […]

Handling workflow from automation script

If you need to handle workflows (start, stop, route, etc.) from an automation script you can use the following two Maximo API classes: WorkFlowService and WFInstance. Here are few examples. The WorkFlowService.initiateWorkflow metod can be used to start a workflow: To stop an active workflow you can use WFInstance.stopWorkflow method: To route a workflow I […]

Set long description from automation script

Today I have discovered a strange behavior when setting long descriptions from an automation script. You know that almost every DESCRIPTION field in Maximo has a corresponding “Long Description” field that is a CLOB attribute that can hold big amounts of text. This is driven by the “Long Description Owner” checkbox in Database Configuration. When […]

Scroll to top