How to manually export data for non-persistent tables using Maximo Integration Framework

Summary

In the Maximo Integration Framework, users have the option to manually export data using the Data Export button in the External Systems application to an external system if data needs to be resent for any reason, this functionality has a limitation for Object Structure that uses non-persistent tables. One way is to update data within the User Interface (UI), such as changing the description slightly, on those records that need to be resent. This action will trigger the event listener to fire and send the updated records to the external system.  However, this functionality has a limitation.  For object structures that contain non-persistent objects, this function is not available.  The object structure MXGLTXN is an example of object structure containing non-persistent objects.

In this case, a workaround is needed to resend MXGLTXN data to an external system.  Since these records cannot be updated directly using the UI, another method must be used such as Escalations, Automation Scripts, or a custom Java Class that will update an attribute on the records that you need to send to cause the event listener to fire and send the data outbound to the external system. Below you will find a simple way to accomplish this task using an Escalation.