Developer Tool Guide

Back Next

Step 4. Prepare Mappings for Editing

If updated mappings fail testing, prepare the mappings for editing.

Set up continuous integration to perform the following integration operations:

1. Assign the mappings to the appropriate developer for editing.: To assign mappings to the appropriate developer, perform the following tasks:

Query the design-time mappings that have the tag
RequiresChanges
using the REST API
Get design-time objects
or the command
infacmd dis queryDesignTimeObjects
.
Based on the third-party tool that you use, you can parse the query result to get the user name of the developer that last modified each mapping.

To assign the mapping to the developer for editing, use the REST API
Perform version control operations
or the command
infacmd mrs reassignCheckedOutObject
.

Version control operations are available only if the Model repository is integrated with a version control system.
2. Notify the developer about the test results.: Optionally, you can use a third-party tool to notify developers about the mappings that require changes.

For example, you can query the design-time mappings that have the tag
RequiresChanges
using the REST API
Get design-time objects
or the command
infacmd dis queryDesignTimeObjects
.

Then, you can run a script in a third-party tool to perform the following tasks:

Read the query results to parse the response and get the user name of the developer that last modified the mapping.
Look up the e-mail address that is associated with the user name in the employee database.
Generate an e-mail message to convey information about the mappings that failed testing and the reason that the mappings failed.