You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduce a locking mechanism in Archi to safeguard views and elements, especially in collaborative environments such as CoArchi. This feature aims to prevent accidental modifications or deletions of stable and finalized model components.
Details:
Locking Views:
When a view is locked, it becomes immutable. Users cannot modify or delete the view or any elements contained within it.
Locked views can be unlocked by any user when necessary.
Locking Elements:
A locked element cannot be deleted or modified. However, it can still be moved to another location within the model.
Folder Locking:
Locking a folder applies the lock to all elements and sub-elements within that folder.
Locked folders prevent the movement or modification of their contents unless explicitly unlocked.
Use Case:
This feature helps maintain the integrity of finalized model components, ensuring that no accidental changes or deletions occur. It is particularly beneficial in collaborative modeling environments where multiple users may have access to the same model.
Simplified User Interaction:
Locking and unlocking should be straightforward and accessible through the UI.
Any user with access to the model should be able to lock or unlock views, elements, and folders as needed.
Benefits:
Enhances model stability and consistency by preventing unintended modifications.
Reduces the risk of accidental deletions or changes in shared models, making collaboration smoother and more reliable.
The text was updated successfully, but these errors were encountered:
That's a feature Phil and I discussed some years ago. I do think it really makes sense for the use-cases you've described.
So I guess we could work on it someday, but we have lot's of things already in the backlog and Phil has been the only one to code for the past years as I have almost no free time (unfortunately), so don't expect it anytime soon.
I would like this feature too. It would enable locking of automatically imported content (e.g. in CI/CD pipeline for coArchi commits), for example when working with segment models that need to reference (but not edit) common content.
Description
Summary:
Introduce a locking mechanism in Archi to safeguard views and elements, especially in collaborative environments such as CoArchi. This feature aims to prevent accidental modifications or deletions of stable and finalized model components.
Details:
Locking Views:
When a view is locked, it becomes immutable. Users cannot modify or delete the view or any elements contained within it.
Locked views can be unlocked by any user when necessary.
Locking Elements:
A locked element cannot be deleted or modified. However, it can still be moved to another location within the model.
Folder Locking:
Locking a folder applies the lock to all elements and sub-elements within that folder.
Locked folders prevent the movement or modification of their contents unless explicitly unlocked.
Use Case:
This feature helps maintain the integrity of finalized model components, ensuring that no accidental changes or deletions occur. It is particularly beneficial in collaborative modeling environments where multiple users may have access to the same model.
Simplified User Interaction:
Locking and unlocking should be straightforward and accessible through the UI.
Any user with access to the model should be able to lock or unlock views, elements, and folders as needed.
Benefits:
Enhances model stability and consistency by preventing unintended modifications.
Reduces the risk of accidental deletions or changes in shared models, making collaboration smoother and more reliable.
The text was updated successfully, but these errors were encountered: