Multi-User Access
Mapping Manager allows simultaneous access to projects by multiple users, but there are locking mechanisms in place to protect someone from making certain changes while projects and mapping values are in use by another user.
How it Works
While an entity is in use, a lock is activated so that no other user can edit the same entity (Purchase Order for example) or any token mappings associated with that entity.
Token and lookup mappings for a specific trading partner and/or map entity will be locked and while the lock is activated, no other user will be able to edit the associated entity. However, other users can edit token and lookup mappings of the same entity provided it is for a different trading partner.
Mapping Alerts
Selecting a locked map entity from the Partner Maps grid results in a popup message that indicates the current user and their last access date/time.
In the following example, a popup message shows that the selected entity is already in use.
In the next example, User 1 has a project's purchase order open in the Mapping editor. User 2 is logged into the same project, attempting to select the same map for editing. At this point, User 2 receives a message indicating that "Mapping Values" are already in use.
Deployment Alert
When it comes time to deploy projects to Transaction Manager, locks must be released in order for deployment to take place.
If you click Deploy while a project has been opened by another user, you will recieve an alert that presents the option for you to release their lock. Of course, it is strongly recommended that you contact the other user before proceeding. Another option is to go back and deploy changes by individual entity.
Continuing with the previous example, User 2 chooses to edit a 940 (warehouse shipping order).
When User 2 completes their work, they click Deploy. If User 1 happens to be logged into the same project at this time, User 2 would receive a message indicating that "Mapping Values are in use by another user" with the option "Do you want to release this lock?".
|
IMPORTANT You should contact the user named in this message before releasing their lock and proceeding with deployment. |
Related Topics