Company Access Control
The Company Access Control permissions can be selected and included in the component list required for creating configuration packages. The selected Company Access Control permissions overwrite, or insert, permissions related to groups in the destination environment. Overwrite only occurs if the Replace in Destination checkbox is selected for the component. If the component does not exist in the destination environment, the configuration package will always insert the component into the destination environment.
Displays the following access control permissions, in groups:
- Administrator Mode Access
- User Mode Access
For static modules, there are no error check performed during component analysis. For dynamic modules (such as BP setup in Admin mode access or Data Cubes as non navigational nodes in User mode access), if the user selects modules dependent on components which have not been selected, when the component analysis is performed, the system displays a warning message indicating that the dependent component has not been selected, but the permissions have been selected.
Upon a successful import, the system updates the permissions for the selected modules. If the permissions (transferred as a part of the configuration package for dynamic modules) do not have the dependent components in the destination environment, and the configuration package, then the permissions will not be imported into the destination environment, and the system displays a message; however, if the dependent components are present in the destination environment, then the system updates the permissions, when imported successfully. By default, for "creator users," the permissions will be set to the "importer user" upon the configuration package creation, and in the destination environment.
All Access Control permissions are available for selection.
The selected permissions (included in the package), when imported, overwrite in the destination environment only if the Replace in Destination field is checked. If the permissions do not exist in the destination environment, the new permissions, imported in as part of the configuration package, are inserted into the destination environment.
Last Published Monday, August 28, 2023