Importing a change command
Use of numbering schemes
If EcENTITY.name contains only the beginning of the number for Vault - this determines which numbering scheme to use.
The specific number of the newly created CO is logged in the DI as information
Routing
the EcENTITY.category field can optionally be used to determine the routing (Routing) when importing a change command
Status
supported state changes (EcENTITY . lfcycstate_name field) are:
OPEN (change from CREATE)
WORK (change from OPEN or CREATE)
APPROVED (change from REVIEW)
REJECTED (change from REVIEW)
CLOSED (change from APPROVED)
EcENTITY . lfcycstate_name - both "SystemName" and "DisplayName" can be used (AWS.WorkflowState.Name or AWS.WorkflowState.DispName)
EcENTITY.lfcycstate_id is preferred over EcENTITY.lfcycstate_name
Import user roles for change commands
if it is required to import also the roles (functions) of individual users for a given change command, it is necessary to add additional fields to EcENTITY with fixed names according to the role names - here is the complete list:
EcENTITY.co_user_role_change_requestor
EcENTITY.co_user_role_change_administrator
EcENTITY.co_user_role_reviewer (Reviewer)
EcENTITY.co_user_role_approver (Approving)
EcENTITY.co_user_role_checker (Verifier)
EcENTITY.co_user_role_responsible_engineer
EcENTITY.co_user_role_notification_user (Notification user)
Conditions:
the fields do not have to be all, only the roles to be imported are sufficient
the array must be of type NVARCHAR(x) - length does not matter
in the ec configuration, these fields do not need to be mapped to a change statement property (this is ensured by a fixed field name in the exchange interface), it is necessary to verify the direction of the mapping
value translation (Replace) can be used
The ERP system writes a user name or a list of users separated by one of the following characters: semicolon, slash, pipe (|), tab
user names must match the name under which the user logs into the Vault (case is not differentiated)
if the name is not found in the list of Vault users, the import is not stopped, but a comment is added to the change command that the user could not be identified/assigned to the role
Import comments
if import of a comment for a given change command is also required, additional fields with fixed names must be added to EcENTITY:
EcENTITY.co_msg_subject optional field - if it does not exist or has no value, "ERP message" is used
EcENTITY.co_msg_text
Last updated