IBM Maximo consultant, geek, agile evangelist
The Maximo condition node allows to specify an condition in SQL format in order to drive the workflow in different ways depending on some custom logic. In some cases the logic that has to be implemented can be quite complex and not easy to implement using SQL syntax. In this case we can use an […]
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 […]
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 […]
In a previous post, I demonstrated how the Maximo audit tracking can be used to display the updates made on a record enabling the audit and adding a “history” tab in the application. This technique is quite common but has a major drawback; it displays all the audited field in a row even if only […]
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 […]
Many large clients require to deliver an as-built document as part of the deliverables to be produced before the go-live. This is typically a Word document where all the Maximo configurations must be listed and described. I think this document has little real value for several reasons: In this article I will propose a better […]
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 […]
In Maximo 7.6.1.1 IBM has greatly improved the service implicit variable to provide a lot of useful methods to interact with the user interface. Two good examples are: For a full reference of the service methods refer to this page. There is very important method that can be used to get a reference to the […]
This post is a copy of a PDF file published by IBM. I’m republishing it here to make it more accessible. Scripting allows users to extend maximo business logic using Python/JS or for that matter any other JSR 223 compliant scripting language. All the script code gets compiled to Java bytecode and are cached as […]
The Budget Monitoring application was introduced in May 2007 as part of the IBM Maximo 7.6.0.8 feature pack but its potential was largely underestimated by the user community. The application may seem complex and may be daunting at first, but in reality it is quite simple to configure for basic use, allowing later to extend […]