IBM Maximo consultant, geek, agile evangelist
Maximo allows to create predefined queries in applications that can be used to filter records based on specific criteria and reuse them in Start Centers. However, there are some limitations in the capability and manageability of these queries. In this post I will describe how to create a Query Manager application to centrally manage application […]
MxLoader 8.5 has some improvements regarding the capability to upload and download files from Maximo. REST and OS services behavior is now aligned and upload/download is fully supported. MxLoader provides two special tags to manage files: Downloading files To download files you must specify the FileTxt/FileEnc tag in the header. MxLoader will recognize that you […]
Writing automation scripts in Maximo is easy and almost every Maximo specialist has some ort of skills to develop customizations using Python/Jython scripts. Every error in your code will be handled by Maximo and displayed to end user as an error message. However, in some cases you need to handle exceptions in order to explicitly […]
Maximo automation scripts became more and more powerful during the last years so we heavy rely on these capabilities to extend Maximo features and fulfill customer needs. When the amount of script code grows, it’s easy to end up into some sort of spaghetti code so you need a practical way split the code into […]
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 […]