The "last save wins" scenario occurs when multiple copies of a transaction exist, and the last one saved is the version that gets committed to the database. For example, if two or more users open and edit the same transaction, the user who saves last will overwrite the changes made by the other user. This can result in data loss and be highly frustrating for everyone involved.
However, we understand collaboration is often crucial for project completion. That's why we've implemented measures to minimize the chances of a "last save wins" scenario occurring in OASIS to help protect your data as much as possible. This article will explain these measures and provide best practices for collaborative work in Legacy OASIS and O4.
Legacy OASIS Teams
When a user opens a transaction in Legacy OASIS, it becomes locked. Locking the transaction prevents other users in Legacy OASIS from editing it and ensures only one version of the transaction exists (available to the user who had it open first).
If a non-admin user opens an already-open transaction, OASIS will only allow them to view it in read-only mode. The user is limited to read-only mode until the other user closes the transaction.
Note: read-only mode does not allow the user to watch real-time changes. The user can only view the last saved and committed version of the transaction to the database. |
If users have admin access, they can unlock a transaction for editing. This can be helpful in urgent situations when the user with the transaction open cannot close it, and they haven't made any changes they wish to save.
However, unlocking a transaction does not close the transaction for the user who has it open. Once an admin unlocks the transaction, two versions will exist. A "last save wins" scenario will occur if both users save their changes.
Because of this, it's strongly recommended that unlocking transactions be a last resort for making changes. The best practice is to contact the user with an open transaction and have them save and close their work.
O4 Teams
For teams collaborating in O4, we've eliminated the possibility of a "last save wins" scenario by introducing live edits. Any changes completed by another user in O4 are immediately visible to all others viewing the transaction, ensuring only one version of the transaction exists.
The spotlight feature lets users see who else is on the transaction and observe others' changes, making collaboration more efficient.
- A bubble with their initials will appear in the top left corner of the screen.
- A box with the same color as the user's bubble will highlight the cells they select in the BOM.
Note: initials are pulled from the Initials field in the user's user account. If that field is blank, it will be drawn from the first and last name fields. |
Teams Working Across Legacy OASIS and O4
Teams that work collaboratively across Legacy OASIS and O4 pose significant risks of encountering a "last save wins" scenario. This is because OASIS cannot communicate the "open" status of a transaction across both systems, meaning:
- Legacy OASIS will not lock transactions when they are open in O4.
- O4 will not display a bubble for users who are viewing the transaction in Legacy OASIS.
Because this limitation results in a lack of safeguards, we strongly recommend teams only work in one system. The choice of which system depends on your team's needs.
- Legacy OASIS will prevent more than one user from working on a transaction at a time, but any user who has the correct security access can modify a transaction.
- O4 allows real-time collaboration with multiple users, and the spotlight feature helps users work more efficiently.
If you have any questions, give us a call at 501-843-6750. We're always happy to help.
Comments
0 comments
Please sign in to leave a comment.