Maximo Automation Scripts: Overwriting Maximo Business Logic with MboConstants

Intro‍

Maximo, a comprehensive asset management system from IBM, allows users to manage their assets, work orders, and maintenance operations. One powerful feature of Maximo is the ability to use automation scripts to customize the system to meet specific business needs. In this article, we will discuss the best practices for using Maximo automation scripts, the importance of using proper validation and access checks, and alternative methods for achieving similar goals.

‍Overwriting Maximo Business Logic with MboConstants

When working with automation scripts and Java code written for Maximo, a wide range of MboConstants can be used to control how the script interacts with Maximo's business logic. It is crucial to choose the right constants for your code to ensure it works correctly and does not compromise the system's integrity. Approach each use case with the least intrusive MboConstants that work for the situation.   

For example, the NOVALIDATION_AND_NOACTION or 9L constant represents no validation and no action, meaning the script will not trigger any additional automation or check the entered values. While this may be useful in some cases, it can lead to undesired results or even break Maximo's business logic. A more appropriate constant for most situations is NOVALIDATION or 1L, which allows the script to run without validating the data that is being set or suppressing other MBO logic.

‍

Commonly Used MboConstants

‍

All available constants can be found in the Java Docs: https://ibm.ent.box.com/v/maximojavadocs 

‍

Different Ways to Utilize MboConstants 

There are a few ways to reference the MboConstants. IBM code often uses a long value like “2L,” which can be difficult to read unless you have the reference table memorized. Using the written-out constant value greatly increases readability. You can either do this by importing the MboConstants class or by referencing the MBO. In the examples below, the NOACCESSCHECK is set in three different ways.

‍

No Constant

        mbo.setValue("DESCRIPTION","Test Value")

Value MboConstants

        mbo.setValue("DESCRIPTION","Test Value",2L)

Importing MboConstants class

        from psdi.mbo import MboConstants

        mbo.setValue("DESCRIPTION","Test Value",MboConstants.NOACCESSCHECK)

MBO to Pull MboConstants

        mbo.setValue("DESCRIPTION","Test Value",mbo.NOACCESSCHECK)

Bonus: Combining Constants with Java Pipe

mbo.setValue("DESCRIPTION","Test Value",mbo.NOACCESSCHECK|mbo.NOVALIDATION)