Do I always have to create a mapping for the technical ids of release field values in order to synchronize release fields?
Unfortunately, some APIs of CCF’s supported system can only update release fields of tracker items if you know the technical release of your id. However, the reader and writer components of these systems typically provide a boolean property called “translateTechnicalReleaseId” that allows you to use the human readable name of the release instead of the technical id. This property is set to false in our default wirings since the lookup involves additional web service calls that might decrease the update performance. If you can live with these additional web service calls, you may edit the wiring of your integration scenario and set the “translateTechnicalReleaseIds” property to true.
Related Questions
- Do I always have to create a mapping for the technical ids of release field values in order to synchronize release fields?
- When I create new entries in the table the field values are always in Uppercase. How do I get the data with mixed case?
- Can re-keying be minimised by providing default values for fields with drop down selection of field contents?
