Managing Model Configuration

Last modified on January 31st, 2017.


This section contains instructions for how to manage model configuration in Innoslate.

Innoslate includes the ability to baseline, branch, and copy (fork) entire projects. Changes to projects can easily be compared via a change table and in 3D, as shown below. Changes made in branch projects can quickly be pushed to the trunk projects. Conversely, Trunk projects can also push changes to branch projects.

Model Configuration Management Example

Each Innoslate project includes a full version control system that versions entity additions, entity changes, and entity deletions. Every change to entity attributes, relationships, labels, and class identification is recorded and revertible by the version control system.

Often users find it desirable to group entity changes with baselines or to branch a project to strictly control revisions to the model.

 

Baselining a Project

To baseline a project navigate to 'Database View' using the top navigation bar. Click to open the 'Branch' dropdown and select the 'New Branch...' menu item. Type in a 'Name' and 'Description' for the new branch and then click on the 'Create & Go' button.

Any changes made to the source project since the baseline can be viewed by clicking to open the 'Branch' dropdown and then clicking on the menu item containing the name of the baseline.

Note that only project owners have permission to baseline a project.

 

Baselining a Document

Innoslate can also baseline individual documents. For more information on how to baseline a document, see Baselining Requirements Documents.

 

Branching a Project

To branch a project, navigate to 'Database View' using the top navigation bar. Click to open the 'Branch' dropdown and select the 'New Branch...' menu item. Type in a 'Name' and 'Description' for the new branch and then click on the 'Create & Go' button.

The branch can be pushed back to the trunk project and the trunk can also pushes changes down to the branch. The changes between the trunk and branch can be visualized in 3D by clicking to open the 'Branch' dropdown and then clicking on the menu item containing the name of the branch.

Note that only project owners have permission to branch and push projects.

 

Pushing a Project

To push a branch to the trunk project, navigate to 'Database View' in the branch project. Click to open the 'Branch' dropdown and select the menu item containing the name of the trunk you'd like to push to. Finally, click on the 'Push to Trunk' button.

To pull changes from a trunk into a branch, navigate to 'Database View' in the trunk project. Click to open the 'Branch' dropdown and select the menu item containing the name of the branch you'd like to pull from. Finally, click on the 'Push to Branch' button.

 

Copying (Forking) a Project

An Innoslate project can be copied (forked) by any user with read permission to the original project. For more information on how to copy a project, see Copying Projects.

Managing Model Configuration

Last modified on January 31st, 2017. 


This section contains instructions for how to manage model configuration in Innoslate.

Innoslate includes the ability to baseline, branch, and copy (fork) entire projects. Changes to projects can easily be compared via a change table and in 3D, as shown below. Changes made in branch projects can quickly be pushed to the trunk projects. Conversely, Trunk projects can also push changes to branch projects.

Model Configuration Management Example

Each Innoslate project includes a full version control system that versions entity additions, entity changes, and entity deletions. Every change to entity attributes, relationships, labels, and class identification is recorded and revertible by the version control system.

Often users find it desirable to group entity changes with baselines or to branch a project to strictly control revisions to the model.

 

Baselining a Project

To baseline a project navigate to ‘Database View’ using the top navigation bar. Click to open the ‘Branch’ dropdown and select the ‘New Branch…’ menu item. Type in a ‘Name’ and ‘Description’ for the new branch and then click on the ‘Create & Go’ button.

Any changes made to the source project since the baseline can be viewed by clicking to open the ‘Branch’ dropdown and then clicking on the menu item containing the name of the baseline.

Note that only project owners have permission to baseline a project.

 

Baselining a Document

Innoslate can also baseline individual documents. For more information on how to baseline a document, see Baselining Requirements Documents.

 

Branching a Project

To branch a project, navigate to ‘Database View’ using the top navigation bar. Click to open the ‘Branch’ dropdown and select the ‘New Branch…’ menu item. Type in a ‘Name’ and ‘Description’ for the new branch and then click on the ‘Create & Go’ button.

The branch can be pushed back to the trunk project and the trunk can also pushes changes down to the branch. The changes between the trunk and branch can be visualized in 3D by clicking to open the ‘Branch’ dropdown and then clicking on the menu item containing the name of the branch.

Note that only project owners have permission to branch and push projects.

 

Pushing a Project

To push a branch to the trunk project, navigate to ‘Database View’ in the branch project. Click to open the ‘Branch’ dropdown and select the menu item containing the name of the trunk you’d like to push to. Finally, click on the ‘Push to Trunk’ button.

To pull changes from a trunk into a branch, navigate to ‘Database View’ in the trunk project. Click to open the ‘Branch’ dropdown and select the menu item containing the name of the branch you’d like to pull from. Finally, click on the ‘Push to Branch’ button.

 

Copying (Forking) a Project

An Innoslate project can be copied (forked) by any user with read permission to the original project. For more information on how to copy a project, see Copying Projects.