Multiple Tabs/Users Edits

In Nected, collaborative work on the same entity (which can be a rule, data set, or connector) by multiple users can sometimes lead to conflicts and data integrity issues. To address this challenge, Nected utilizes a mechanism. The mechanism helps ensure that only one user is actively editing an entity at any given time, preventing data conflicts. Other use can still keep using and viewing the entities but would be blocked in case they try to edit any entity.

This documentation explains how this blocking mechanism works and offers guidance on effectively managing concurrent edits in Nected.

Multiple User Case:

When multiple users are working in the same workspace, Nected designates one user as the active editor and the others as non-active editor. The active editor has exclusive editing rights for the entity, while non-active editor are temporarily blocked from making changes.

Edit-Based Activation

It's important to note that the system identifies the active editor based on the latest save triggered by a user. An edit in this context refers to actions like editing, or saving an entity. Until a user performs an edit event, they are not recognized as the active editor.

Here's how the mechanism works in practice:

1. User X and User Y in a Workspace: Let's consider a scenario where two users, X and Y, are collaborating in a workspace. User X creates a rule and starts editing it, making X the active user for that rule.

2. Switching Active Editors: If User Y begins editing the same rule right after User X, the system designates Y as the active user, effectively switching the active user from X to Y. This switch ensures that only one user can actively edit the rule at a time.

3. Blocking Non-active Editors: While User Y is actively editing the rule, User X attempts to make edits. In this situation, User X gets blocked by the system, preventing simultaneous edits and potential conflicts.

   
4. Edit-Driven Activation: It's crucial to understand that the system's identification of an active user is edit-driven. The last user to perform an edit on an entity becomes the active user for that entity. User who would try to perform an edit after active editor will be blocked to edit.

Multiple Tab Case:

In the multiple tab case, when a user has multiple tabs open within the same workspace and is working on the same entity, it will block of the tab to edit. Nected operates on a sequential basis. It identifies the active editor based on the latest edit trigger, blocking inactive editors from making edits.

Here's how it works in the multiple tab case:

1. User with Multiple Tabs: A user has multiple tabs open in the same workspace, with each tab potentially editing the same entity.

2. Active User Identification: The system identifies the active user based on the latest event trigger(if the user starts editing). The last tab to perform an successful edit on the entity becomes the active tab.

3. Blocking Inactive Tabs: Any tabs that are not actively editing the entity are considered inactive, and the system blocks them from making edits. This ensures that only the active tab can make changes. You can still continue browsing rules / entity until you don't make any edits.

Managing Concurrent Edits

To work effectively in a multi-user environment and avoid potential conflicts, consider the following best practices:

1. Patience and Communication: When editing a shared entity, be aware of others who might be working on it simultaneously. If the entity is already being edited, wait for the initial user to complete their edits before making further changes. Effective communication within your team can help coordinate editing efforts.

2. Prevent Redundant Edits: Collaborate with your team to prevent multiple users from making redundant or conflicting edits to the same entity. Communication and coordination are essential in streamlining the editing process.

3. Refresh the Entity: Before making changes to an entity, refresh the page to ensure you're working with the latest version. This practice helps prevent potential conflicts and ensures you're working with the most up-to-date data.

4. Review and Confirm: Before saving your edits, review the entity for any changes made by other users. This review helps identify discrepancies and ensures that the final version accurately reflects the intended outcome.

By following these guidelines and understanding how Nected's blocking checksum mechanism works, users can collaborate efficiently and maintain data integrity while working on shared entities. The system's "last event" based approach ensures that edits are systematically managed, preventing data conflicts and supporting seamless teamwork.