Metis Smart Modeling - Configuration Manager
From Metis Documentation
| Line 7: | Line 7: | ||
Using the same central database, each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules|Rules]], [[Metis_Smart_Modeling_-_Variables|Variables]] or [[Metis_Smart_Modeling_-_Masks|Masks]]) is "checked-out" when edited by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users. | Using the same central database, each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules|Rules]], [[Metis_Smart_Modeling_-_Variables|Variables]] or [[Metis_Smart_Modeling_-_Masks|Masks]]) is "checked-out" when edited by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users. | ||
| + | |||
| + | The Configuration Manager allows also to enforce versionning on all the model data to be made available in Metis Smart Suite. By creating ordered Packages, the User/Administrator can define multiple packages for all future versions of the models. The tool then allows to transfer updated part of a package to any of those packages in order to keep them all up to date and to have consistent data. | ||