Hi Denisa,

Depends on what Locking a branch would imply. We do have the Active checkbox for branches. This way you can indicate if a branch is worked on or has a reason being Active.

Locking in the sense of not allowing any data mutation for that particular branch is not possible currently. That would quite the impact on the size of the Software Factory in terms of logic procedures and triggers.

From version 2023.1 we did add the option to revert a branch to a point-in-time. This could be a point in time where the branch would be considered locked. In case any changes were made to the model after that point in time, you could always revert to the correct moment.

Edit: The current "Lock” the Software Factory knows is a type of lock that prevents multiple same-typed program objects and code being generated at the same time. 

Hello,

Yes, we can use the Active checkbox for what we need right now.

Thank you!

Small update on this topic: In the 2025.1 platform version we will introduce an option to set a branch read-only per user.

For more information, please see this idea: