Supporting Shell Attribute View Forms
Since you can include View Forms in shell attributes and restrict users and group (who are members of the shell) to view the forms added to the shell properties (View Forms tab), you can use the Configuration Package to export and import the View Forms tab information (along with other tabs) of the shell properties of your selected shell templates or single instance shells.
In general, you can export and import the shell attribute design (which includes both the action forms and the view forms), and the view form permission settings (added in the View Forms tab of the shell or shell template properties), by way of Configuration Package.
Configuration Package export for shell templates and single instance shells
When you tag one or more shell templates that have view forms setup in the Component List, then along with other shell tabs the View Forms tab information will be exported, when you create the Configuration Package.
Along with the view forms, the users, groups, and shell administrator, who are part of the permission settings of view forms, will be exported. For other modules in the BP setup, the users, groups, and shell administrator associated to the permission settings will not be exported. In other word, the users, groups, and shell administrator associated to the permission settings in the View Forms tab of the BP setup will not be exported; however, the users, groups, and shell administrator permission settings in the view forms setup (in the shell attribute form) will be exported.
When the published shell design does not have all the view forms added in the tagged shell template in the Component List, then the design dependency error is displayed, when you conduct error check in the Component List. Add the dependency component to fix this error.
If you tag a shell template (that has view forms) in the Component List, and the published design has those view forms already, then the system does not validate for the latest deployed design. Also, if the tagged shell template does not have any view forms, and the shell design is published, then the system does not validate for any latest deployed design while creating the Configuration Package. Similarly, when you tag a single instance shell, and the selected shell instance has view forms setup, then along with the other tab information all of the view forms and permission settings (for the users, groups, and shell administrator) will be exported.
Import of Configuration Package containing shell templates with view forms
When you import the Configuration Package containing shell templates with view forms into the destination server:
- If the shell template does not exist, then a new template will be created and view forms setup information (forms and permission settings for groups) will be added.
- If the destination server already has the shell template, then the view forms setup information will be updated by way of importing the Configuration Package.
- If Configuration Package created has a single instance shell with the view forms setup, then in destination server the single instance shell will be imported when the component does not exist. The view forms setup information are also imported along with the other tabs. In the case the destination server already has a single instance shell, then the single instance shell information will not be updated, including view forms information.
Last Published Saturday, July 13, 2024