IBM Maximo consultant, geek, agile evangelist
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 […]
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 […]
There are many blog posts in the Maximo technical community describing how to develop an automation script and schedule execution using a cron task (link1, link2). However, a custom cron task may run for a long period of time and this may block the system when trying to enable administrative mode. In this case you […]
I was recently struggling understanding how enable password expiration in Maximo when using native authentication. This IBM TechNote explains very well how the standard Maximo expiration configuration works but there is a very tricky sentence: In the case of a user belonging to any groups not containing a password expiration, the user’s password will never […]
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 […]
OmniEasyDataArchiving+ is a data archiving solution for Maximo delivered by OMNINECS. Supports any Maximo environment: Maximo 7.6 or MAS 8, DB2/Oracle/SqlServer database, on-premise and cloud deployments. Predefined archiving templates to start as fast as possible.
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 […]