|Maintenance Notice - PDF Generation|
|Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.
Templates and their Script Objects
Role permissions for importing and exporting templates and rule packages must be set to the following values:
- To import a template, a user must have Create permission for the Rule Template.
- To export a template, a user must have read access to the Template Script Object representing the template.
- To import or export rule packages, a user must have full permissions granted. For example, if a user does not have the ability to view business calendars or test scenarios, they won't be exported in the rule package XML. Conversely, if a user doesn't have permission to create calendars or test scenarios on import, they will not be able to create these resources from the imported rule package.
Script objects are used to control visibility to templates. Whenever a template is created, a Script object is created automatically in the Template Access Control folder under the Scripts folder to represent that template. A user must have read access to that Script object to be able to view that template.
Genesys recommends that you give template developers View permissions to the Template Access Control folder and have that permission propagate to all sub-objects. This way, template developers can immediately view any template that they may create. All other users will not be able to see the newly created templates until View permissions are explicitly granted for that template.