Change processing of rules by using the mboRules(ctx) function
The mboRules(ctx) function can skip the processing of a
business object, skip a transaction, continue processing, or create
a business object. This function operates before the creation of each Maximo business object.
Set values in fields by using the beforeMboData(ctx) function
The beforeMboData(ctx) function is available when the Maximo business object is created but before the values in the business object are set by the integration framework. Processing of the object structure can change the setting of business object data. Processing can also set flags on the fields, such as the samevaluevalidation flag, which triggers field validations even when the field value is set with the current value of the field.
Add business objects and change values in fields by using the afterMboData(ctx) function
The afterMboData(ctx) function implements custom logic to create an extra related
Maximo business object for inclusion in the
transaction or change data in a Maximo business object. The function is available after the
business object is created and the values are set in the Maximo business object by the integration
framework.
Change the transaction before saving to the database by using the preSaveRules(ctx) function
The preSaveRules(ctx) function allows for extra processing
that is related to the transaction as a whole. You can use the preSaveRules(ctx)
function to create a related object and add it to the transaction.
The function is called before the Save action and is called for each
noun in the message.
Change status or status date by using the changeStatus(ctx) function
The changeStatus(ctx) function implements a status change outside the statefulMicSetIn class that is available in the integration framework. You can also use this function to set the status date with a value instead of using the system date.