The application development process heavily utilizes the Object Migration (OM) functionality of the TRIRIGA application. Objects that have been developed in a lower environment are migrated to a higher environment via an OM package. In certain instances, you can receive errors in the OM validation process that are inconsistent when run multiple times. Likewise, the OM validation process may not show any errors, but the import process fails with or without errors.
When using the Object Migration tool in TRIRIGA, errors that may be found in that process can be misleading if there are network connectivity issues. This issue can manifest when running the validation process multiple times for a particular OM package and getting different results each time, even if you did not make changes to the OM package. Likewise, if the validation is successful and the import process starts, network connectivity can result in unpredictable results from the OM process.
Object Migrations should always be done on the local network to minimize the possibility of a network connectivity issue resulting in apparently random errors during validation or being unable to complete the import process and leaving the OM package in an “Import Pending” state. In this latter case, the cleanup agent may resolve the issue after a few days as it may leave an orphaned record in the database which prevents running further OM packages.