Permission Lists and Roles
This document provides basic definitions of the five GT-delivered permission lists:
G3FORMFUNCG3FORMTECHG3FORMDESIGNG3FORMADMING3FORMUSER
These permission lists are delivered with the framework, along with basic roles you may use for development and testing. It is expected that you will incorporate the permission lists into your existing roles or create new ones according to your preferences and naming conventions, though you may continue to use the GT delivered roles if you prefer.
GT eForms FunctionalGT eForms TechnicianGT eForms DesignerGT eForms AdministratorGT eForms Administrator
The Permission Lists
The following are the GT-delivered permission list definitions. It should be noted that none of the permission lists are mutually exclusive, meaning that there is overlap between some of the permission lists. For example, a user with the G3FORMFUNC permission list may have access to a particular component and page that the G3FORMTECH user also has access to. Furthermore, they are not hierarchical in nature. Instead of picturing the permission lists as ‘levels’ of access, it is better to think of them as ‘puzzle pieces’ of access. G3FORMFUNC and G3FORMTECH are designed to be independent of each other. In order to have access to all setup tables for GT eForms, you will need the following permission lists: G3FORMFUNC and G3FORMTECH.
G3FORMFUNC
The G3FORMFUNC permission list contains all of the components and pages that pertain to performing functional setup for a form. These include, but are not necessarily limited to, the components listed in the Functional Setup folder located in the Manage GT eForms 3.x menu and the Form Setup page.
G3FORMTECH
The G3FORMTECH permission list contains all of the components and pages that a technical user will need to use to support forms. These include, but are not necessarily limited to, the components listed in the Technical Setup folder located in the Manage GT eForms 3.x menu and the Form Setup page.
G3FORMDESIGN
The G3FORMDESIGN permission list is for use in Classic mode only. It is used to access the design mode cogwheel on forms in Classic Mode. If a user needs to use that cogwheel, they must have the G3FORMDESIGN permission list; otherwise, they will not see the cogwheel icon. This permission list cannot be used alone and should be used in conjunction with another permission list.
G3FORMADMIN
This is not a system administrator permission list. This is a form solution administrator permission list. This permission list is designed to provide tools for admins to assist in the processing of the forms. These include, but are not limited to, the Admin Tool and SQL/PeopleCode logging.
G3FORMUSER
The G3FORMUSER permission list gives users the ability to be given access to any eForms, wherever they are. While specific form access is controlled at a form level, all end users must have this permission list in order to be able to interact with eForms. It also grants access to the GT WorkCenter where forms are commonly added, updated, evaluated, or viewed.
What Does Each Permission List Provide Access To?
For a detailed explanation of the Pages, Web Libraries, Web Services, Queries and Component Interfaces included in each delivered permission list, users may query the following tables in Query Manager.
| Security Area | Table |
|---|---|
| Pages | G3PL_PAGE |
| Web Libraries | G3PL_WEBLIBRARY |
| Web Services | G3PL_WEBSERVICE |
| Queries | G3PL_QUERY |
| Component Interfaces | G3PL_CI |
Since there is no GT-delivered CI, the G3PL_CI record is currently empty.
Example Query Results:
Customizing Permission Lists
Every release, GT may update GT-delivered permission lists, which will wipe out any changes, so please remember that Framework permission lists and roles should not be modified. The GT delivered roles can be used or not used at your discretion. You should always use the GT permissions lists to provide access to the above functionality.
If there are additional permissions needed for certain solutions, those permissions should be added to the client-copies of appropriate roles. (E.g. A CI permission list may be added to the client-version of the GT eForms Administrator role or a permission list with access to custom setup tables may be added to the client-copy of the GT eForms Administrator Role.)