These mechanisms automate the process of applied solution support by
developers. The problems solved by these mechanisms concern creation of new
versions of applied solutions and generation of updates for actual version (i.e.
those used by customers).
The task of applied solution update includes two types of mechanisms:
Distribution
Support
The scheme of distribution and update
generation
Distribution
The distribution mechanism helps developers to form applied solution updates.
There are two options for creation of a delivery kit:
Complete kit – includes the applied solution configuration file, properly
formed.
Update kit – includes only modified parts (objects, modules, etc) of an
applied solution.
A developer can define support mode for configurations, considering
modifications made in user configurations. For this, developers can specify
rules for modifications of an applied solution's objects.
Options for distribution kit generation
Support
Support – is a special state of a configuration which means that the applied
solution is capable of updating from update kit files. If a configuration is
'under support (contract)' then configuration objects are marked with a special
icon.
The support state is defined by rules specified by a vendor and current locks
of a user configuration. After first installation, applied solution is set under
full support and user cannot modify it. However, there is possibility for the
user to customize support options to enable modifications in his applied
solution and specify his own rules, down to the complete disabling support.
Support options window
If a configuration is 'under support' then it can be updated automatically,
for example, from a pre-defined Internet resource.
If the possibility to make changes was enabled, then automatic update will
not work. In this case a user will be offered to
compare and merge
configurations. The process allows to see what modifications were done and
in which configuration (updated or user's one).
