The resulting window that opens for the copied requirement doesn't have all attribute values copied. This is different to opening the donor requirement first and then clicking the Copy button on the requirement form. All relevant values are copied in this case.
2. Open the requirement and go to the link section 3. Select "Create New & Link" on the right-side of the display In the new requirement all attribute values are copied across except those from the group attributes.
In the Desktop client when you have a single-field, multi- value attribute with two or more rows in it and you switch between the two roles in the roles section it will duplicate the rows displayed. Steps to recreate: 1. Create or modify an attribute on a request type to be a single field, multivalue attribute
The behavior will look as follows; If you have a deployed single selection field with two selectable values (lets say "YES" and "NO"), deploying your Global Process App will create duplicates of each value in that selection field when editing or creating a new record in that auxiliary table. So if you are originally seeing:
<element name="TransitionName" type="ts:LongNameType"/> If there is another copy of the file in the "xmlschemas" directory, then make the change there also. Fixed in 6.5 and above
This issue is caused by " Duplicating " a transition in a sub workflow. If you are editing a sub workflow and click the duplicate option on a transition that is Inheriting from it's parent then when you click on the "Options" tab of the newly created transition you will get the error above. If you try to deploy or export this app you will get the second error and you won't be able to deploy.
