How Update Process is Performed If Administrator Roles Are Separated?

The update process is performed in three steps, if administrator roles are separated:

Creating an update (in the developer repository).
Updating by information security administrator (in cloned customer repository).
Updating by application administrator (in cloned customer repository).

The update file that contains data about the updated objects and their access permissions will be created, opened or installed by each of the administrators with a different set of available elements.

The information security administrator can work with:

Access permissions to repository objects and to special objects.
Folders.

The application administrator can work with:

Repository objects (new for the customer base and already existing in it).
Security subjects.
Special objects.
Folders.
Data about object deletion.
Comments.
SQL commands.

There are also differences in creating, opening, saving and installing update, on searching for an update element.

In accordance with user privileges object update options are not fully available. Parameter values inappropriate to privileges are not displayed. If a parameter contains values that do not correspond to privileges, it is displayed as read-only in the current value.

An information security administrator can also install updates containing update unit without ability to view unit contents.