When deploying the Global Process App, additional copies of the selections in single selection fields are added to the field . This only happens with the Global Process App so this is only happening for auxiliary tables.
ERROR -- Import: Incoming field already exists within the context of the current table. Name: '<field name>', Incoming UUID: '2247ae4d-920e-4e38-adec-96a89107f51e'.
As of SBM 11.5, the default behavior for field mapping in post, copy, and create subtask transitions has changed. Prior to 11.5, when copying field values to another item, the system used default mappings for each field , but you could override those mappings by explicitly mapping fields . For example, when posting an item into the same primary table, all field values were copied to the new item and any manual field mappings that you made would override the default mapping.
This Defect, ENH277669 and ENH276111 are all related in that they try to achieve totally the opposite. The manuals state that the User running the transition should be the "submitter" of the new item after the Copy . However, an Enhancement was accepted to change the behaviour, hence this defect.
Composer shuts down. Expected Result: Should Copy the field with no errors from the one application to the second application, in the same mashup. Additional Comments: This may be a problem with other fields, but so far from the fields that were attempted to be copied, only the single select gave the error and shut down Composer.
