Virtual (Non-persistent) Mbo support in REST API
A lot of Maximo business processes have been developed using virtual (non-persistent) mbos. These mbos have subtle differences in the life cycle callbacks/events compared to their persistent equivalents. MIF/REST did not full support for those callbacks like setup() and execute() until recently. Starting 761 this support is available. Using this, we can now leverage a lot Maximo functionality using apis/mif that was previously not easily accesible. Below is an example of downtime reporting using object structure MXAPIASSET. Note that the virtual mbo DOWNTIMEREPORT has been added to the MXAPIASSET as a child object to ASSET.
POST /oslc/os/mxapiasset?lean=1x-method-override: SYNCpatchtype: MERGE
Body:
{"assetnum": "13150","siteid": "BEDFORD","downtimereport": [{"isdowntimereport": "1","startdate": "2019-07-17T22:57:56-04:00","enddate": "2019-07-17T22:58:59-04:00","code": "BRKDWN"
The above example also demonstrates the usage of the SYNC header, which is used when we want to avoid providing the individual asset url (with the rest id) and instead just want to use the collection url. The same could have been achieved using the asset url with the rest id and a x-method-override value as PATCH.