Declarative model for building interface allows automatic adaptation of it
for a particular user. There are several possibilities for that.
Interface interaction with other
platform systems
Automatic
Processing of Roles and Access Rights
The user interface is built taking into account the user rights/permissions.
For example, some objects, which are not available for a particular user, will
be unavailable for him in the command interface.
For example, if there are predefined rights necessary for a shop assistant
only to enter and post 'GoodsOutgo' document and to browse 'Goods' and
'Contractors' catalogs, then the system automatically removes all objects from
the command interface, which are not allowed for that user.
User role defines user interface
Besides, a new capability was added in managed application to specify the
rights for individual object attributes. Using these settings, the system
automatically excludes corresponding form fields, or makes them 'read-only',
also hides some columns in lists and reports.
Rights specified for a form field
Visibility by Default
Default visibility can be specified for individual fields of various
interface elements (commands, form elements). This allows, depending on user
roles, to provide a user with the most important part of functionality, keeping
the possibility to enable (make visible) those elements which are not displayed
for him by default.
Field visibility setup
Functional
Options
The mechanism of functional options allows defining in a configuration the
functionality that may be used or not used at implementation stage, depending on
a particular business needs.
Various configuration elements (objects, attributes, commands) may be
assigned to functional options.
At the implementation stage, functional options can be enabled/disabled in
the information base.
The system then will automatically enable or disable corresponding interface
elements (fields, commands, list columns, elements of reports):
Besides, functional options can be used with parameters. This, for example,
allows implementing a form's appearance specific for a particular organization
selected at the form:
Functional options in action
User Settings
Users are provided the possibility to adjust the system interface according
to individual preferences. It is possible for them to customize command
visibility in the command interface, their order and grouping.
User settings windows
They can also change visibility and grouping of form elements, customize some
form elements' properties effecting visibility and availability: