Did you know that you can export data from Maximo based on some event automatically? Of course you did, but did you know that in Maximo 7.5 there is a new feature setting called ‘event propagation’? It allows you to export data based on when a child record is saved, but there are some gotcha’s.
Previously, when you created a WORKORDER Object Structure with a WORKLOG as the child object and enabled the event listener, it will only trigger the export when you modified the WORKORDER object, but not when you modified the child WORKLOG objects. For some, this is unexpected behavior. Well, now you can trigger the same export when you make any changes to the child object, like adding a new WORKLOG for example. When you create the Object Structure, make sure you enable the ‘propagate event’ checkbox.
For the most part, just doing this will work, but there are some gotcha’s. For this to work as expected, you have to carefully choose the right relationship between the parent and child objects. In this case, there are two relationships between the WORKORDER and WORKLOG objects: MODIFYWORKLOG and WORKLOG. In the database configuration, you can see that the MODIFYWORKLOG has a ‘where clause’ associated with it whereas the WORKLOG relationship is just blank. Some might think that when you create the Object Structure, you should use the MODIFYWORKLOG, the answer here is, no, you shouldn’t. If you tried that and tried to create a new worklog on a workorder, you will see that it doesn’t work as expected. The trick here is to use the WORKLOG relationship for the export to trigger and to export the WORKORDER and WORKLOG data.
