Maximo Business Objects attributes have built-in business logic, which is executed every time we interact with them. For example, when we open a record into a Maximo application, some business logic is already running, such as setting its behavior to read-only or required. Likewise, when we enter a value in a field, the business logic is also executed, such as validating the information entered or how to complete other fields based on the value entered.
Below I detail the typical sequence of execution of this business logic in the attributes:
1. initValue()
It is used to initialize the value of the attribute.
In case of Automation Script, the event is Initialize value for Attribute Launch Point.
The Maximo Best Practices indicate that defining business logic at this point should be avoided as much as possible, since it could impact performance and in case of an error, the field could be disabled.
2. init()
It is used to set the behavior of the attribute, such as Read Only or Required.
In case of Automation Script, the event is Initialize Access Restriction for Attribute Launch Point.
The Maximo Best Practices indicate that you should avoid defining business logic at this point as much as possible, as it could affect performance and, in the event of an error, the field could be disabled.
3. validate()
It is used to validate the new value entered in the attribute.
In case of Automation Script, the event is Validate for Attribute Launch Point.
4. action()
It is used to update other MAXIMO fields or objects.
In case of Automation Script, the event is Run action for Attribute Launch Point.
5. hasList()
Returns true if the attribute has an associated list, false otherwise.
It does not have its equivalent as a Launch Point event.
6. getList()
Creates an MboSet for the list associated with the attribute.
In case of Automation Script, the event is Retrieve list for Attribute Launch Point.
If you found my post interesting or useful and just want to say thanks, you can always buy me a coffee.
