Mapping Manager: Multi-User Capabilities | TrueCommerce Foundry Help Center

Product: Mapping Manager

Article Link: http://help.truecommerce.com/en/articles/6952380-mapping-manager-multi-user-capabilities

Multi-User Capabilities have been added to Mapping Manager to allow multiple users to work within a Project, including testing across more Trading Partners by various users. It also serves to protect the integrity of your work and the work of other users in Mapping Manager, and to allow access by more users simultaneously.

The following Multi-User Capabilities are available in Mapping Manager:

Entity Lock - An Entity (row/column definition) will be locked and while the lock is activated, no other user can edit the same entity (a Purchase Order/PO, for example) or any token mappings associated with that entity.
Mapping Lock - Token mappings (and lookup mappings) for a specific customer, trading partner, and/or entity will be locked and while the lock is activated, no other user can edit the associated entity (row/column definition). However, other users can edit token mappings (and lookup mappings for a different customer and/or trading partner) in the same entity.

Entity Lock

Continuing with the example of a PO, if User A is in the PO and User B attempts to Edit the PO within the same Project at the same time, User B will be notified via a pop-up that the PO entity is currently in use by another user. The pop-up displays the username and last access date and time.

Mapping Lock

In the following image, User A is logged in (screen #1 on the right) and within the project's PO map. User B is logged in to the same project (screen #2 on the left) and attempting to access the PO map as well. At the point that User B selects Edit for the PO, the pop-up message displays, alerting User B that the map is currently in use by the username and their last access date and time.

However, if, for example, User B instead decides to access the Warehouse Shipping Order (940) to view it, Mapping Manager will allow it. But if User B attempts to Deploy All, User B must select to release other document maps that may be indicated as 'in use' by another user in order for the deployment to occur, or User B can deploy the individual entity associated with the map on which they are working.

IMPORTANT: It is a strongly recommended best practice to first communicate to the other user or Deploy the individual entity instead to avoid loss of individual work data.