Home > Manager

Use UI Services

UI Services (User Interface Services) provide advanced features integrated to EBX.Manager. Examples of UI Services:

• Import data from an external source

• Export data to multiple systems

• Mass update records in a table

• Duplicate data from several tables

• ...

Execute UI Services

UI Services can be executed at several levels in EBX.Manager:

• At the adaptation instance level, if the UI Service concerns the whole adaptation instance (or the whole repository if on root adaptation).

  In this case, the UI Service can be accessed by clicking on the Services tab

• At the table level if the UI Service concerns the whole table . 

  In this case, the UI Service can be accessed from the upper right side of the table in the menu Actions

• At the table occurrence level if the UI Service concerns one or many occurrences . 

  In this case, after selecting the target occurrences, the UI Service can be accessed at the upper right side of the table in the menu Actions

Outside a table a UI Service is always identified by this icon: . Just click on this button to execute the UI Service.

Inside a table, all services (both for table and occurrences) are displayed in a selector (menu Actions ).

Once you have selected a UI Service, you access its features with your existing session in EBX.Manager.

UI Services provided by default

EBX.Platform comes with default UI Services (that can be accessed in the Services tab).

Optimize & Refactor

This UI Service allows to optimize your adaptation tree:

• Handle duplicated values: this procedure detects and removes each parameter value which duplicates the inherited one.

• Mutualize common values: this procedure detects and mutualizes descendants' common values to a common ancestor.

These optimization and refactoring functions do not handle default values declared in schema.

Instances are handle bottom-up meaning if level N is the instance on which optimization is executed, N+1 the level for its children and N+2 the level for its children's children, the service will handle first instances at level N+2 to see if they can be optimized compare to those of level N+1, then level N+1 with level N.

The following schema illustrates this mechanism:

The starting point is always the instance from which the children must be optimized. It means that when choosing an instance for removing duplicates, the service will look for duplicates of the instance's children and not for duplicates of the instance compared to its own parent. It works the same for the refactoring.

Table optimization is done for records with the same primary key.

Optimization and refactoring functions do not modify the resolved view of an instance if this one is activated or is an agreement.

Access rights

Optimization and refactoring functions are granted to any profile with write access on current instance values. It can be disabled by setting a restrictive access right to a profile.

For performance reasons, access rights are not checked on every node and every table record.

Home > Manager