Home > Manager

Manage Life Cycle

EBX.Platform allows to manage Master Data Life Cycle through branches and versions (see chapter Important Concepts ).

After logging into EBX.Manager, the first page displays branches in the left pane. The versions created from the branch being selected are displayed in the right pane.

Create and manage branches

Branches allow to make many concurrent changes in a repository. There are several icons for branches:

This icon indicates that the connected user has a read write access to the branch or that the branch's owner is a role

This icon indicates that the connected user is the branch's owner

This icon indicates that the connected user has a read only access to the branch

To create branch, select the parent branch on the left side of the screen and click on Create a branch.

By default, you are the owner of the branch. It means that the branch can only be edited by yourself (consider it as a personal project or a draft). You can change the owner using the drop-down menu.

To view or edit the contents of a branch, click on View / Edit Content. Please note that the initial branch, called the Reference Branch is read-only.

To validate the contents of a branch, click on Validate branch content. This will validate all data contained in the branch. Please note that this operation can take time if your repository contains large volumes of data.

You can also change the branch information by clicking on Modify branch information . 

Change branch access rights

You can change Access Rights on the branch by clicking on Access Rights . Rights are defined in a standard table (see chapter Working With Tables ).

Merge a branch

Changes in a branch can be applied to the parent branch by using the merge function. For example, if you are working on a branch called "Branch1_Child2", you can merge all your modifications to the parent branch "Branch1".

To merge a branch, click on Merge branch . A screen displays all the changes between the current branch and its parent ( see figure below).

Merge process indeed "reconciles" two differences, called "change sets":

This "three points" (current branch, current branch's initial version, parent branch) merge allows to detect conflicts. Sometimes, a data has been modified both in the current branch and in the parent branch.

In general, we distinguish the following types of updates:

Similarly, we can distinguish the following conflicts:

Before the definitive merge, the user has to perform some decisions: choose whether or not to apply changes done in the current branch. By default, all the changes are selected. The user can then unchecked those he does not want to take into account in the parent branch. This operation can be done for all elements of a branch: adaptation instance, table, node.

Note that merge process concerns also access rights that are described in a table. Hence, the user can also apply decisions on permissions if they have been updated.

At each level (adaptation instance, table, node) appears a button named "Mark as decided" . This button is used to confirm decisions once made. The merge button named "Merge now" , appears only when decisions has been confirmed on all instances for which differences have been raised. A shortcut to that, if you agree with the decisions selected, will consist in selecting the link "Differences" and then clicking on the button "Mark as decided" that appears in the corresponding window and finally, the merge button will appear. You have then to click on it in order to execute the definitive merge.

Note that after the merge process, the current branch is closed. It means that it can no longer be edited but can be read (read only access right).

Close branch

If you want to give up a branch without merging it, you can close it. To close a branch, click on Close branch.

Please note that this operation cannot be undone. If you close a branch, you will be able to read its contents (read-only) but not to change it anymore.

Create versions

A version is a "snap-shot" of a branch, identified by a name and a time stamp. Versions allow you to keep track of your branches' values and also to view them.

To create a version, select a branch, then click on Create a version on the right side of the screen.

By clicking on a version name, you will access to its contents in read-only mode.

Home > Manager