Access Control
For specific modules, you can update the Access Control information in the destination shell templates from a source shell template. To do so, use the Update Shell Templates toolbar option. After the update completes successfully, all the selected destination shell templates will have the Access Control information updated.
The modules that do not exist in the destination shell template will get added.
Also, Groups or Users associated with the modules are added. The modules that exist in the destination shell template will have the Access Control information replaced. In this case, new Groups or Users that do not exist in the destination shell template will get added.
To access and work with the Update Shell Templates toolbar option:
- Go to the Company Workspace tab and switch to Admin mode.
- In the left Navigator, select Templates, select Shells, and then select Projects.
- In the Projects Templates log, select and open a project.
- In the left Navigator for the project, select Access Control to open the Access Control window.
- From the toolbar, click Update Shell Templates.
- From the Update Shell Templates window select as many records (modules, BPs, and so on) as you need, click the Update drop-down list, and select the Shell Templates menu item to open the Select Shell Templates pop-up window.
- From the Projects list (Projects - Current View: All), select the projects that you want to update, and click Update.
- When the Confirmation appears, click Yes to update the selected shell templates.
- When the Update Shell Templates window appears, close the window to return to the Access Control window.
In the Update Shell Templates window, when you select as many records (modules, BPs, and so on) as you need and click the Update drop-down list, the following menu items are available:
- Shell Templates
- All other Shell Templates
- History
The Shell Templates menu item is explained above.
All other Shell Templates
If you click the All other Shell Templates menu item, click Yes to update all the shell templates when the Confirmation message appears, or click No to cancel. When you click Yes, the selected modules Access Control information (permissions) are sent (pushed) to all the other shell templates of same shell type, excluding the current source shell template.
History
If you click the History menu item, the Update Shell Templates: History window opens. This window shows the details—such as Requestor, Shell Templates, Submit Date, and so on—of the submitted update requests.
In the case of Access Control information, the history details the actions performed as part of Access Control information push to the destination shell templates (all shell templates or the user-selected shell templates).
In the case where in certain shell templates the job is not successful, the history details lists the shell templates where the update has failed and displays the reason for the failure.
Configuration Package and Access Control
For specific modules, you can send Access Control information of a component (or selection of components) into a destination shell template (or a selection of shell templates), from the source shell templates.
- If any of the selected components exists in the destination shell template, the Access Control information will be replaced in the destination shell template.
- If any of the selected components do not exist in the destination shell template, the Access Control information will be added in the destination shell template.
The associated Groups and Users will also be added into the destination shell templates.
See Also
Business Process and Workflow Setups
General Spends (SOV Structure)
Payment Applications (SOV Structure)
Summary Payment Applications (SOV Structure)
Setting Up Shell Templates with Multiple Base Commit BPs with Multiple Payment Applications and SOVs
Reports (User-Defined Reports)
Defining Activity Sheet and System Activity Sheet Views for Inclusion in Templates
Last Published Tuesday, April 8, 2025