|
CF_ADMIN_MENU |
Edit the labels of the Administration tabs |
|
CF_ALL_BEHAVIOR_SETTINGS |
The complete list of behavior settings (in alphabetic order) can be viewed and modified from this list. Write access is needed to control this |
|
CF_ALLOW_CHANGE_ROLE |
Display the Role: change option on the menu bar |
|
CF_ALLOWED_VALUES |
Access to the screen for maintenance of allowed value lists. These lists can also be maintained individually from the child list maintenance screen |
|
CF_ALLOWEDLOCALES |
Maintain the list of locales allowed to be set by users in this installation. Note that even though a locale is defined, the translated messages may need to be created. Write access is needed to control this |
|
CF_ALLOWEDVALUE_TYPE |
Define and specify a parent-child hierarchical relationship between two fields. Write access is needed to control this |
|
CF_API_SETTINGS |
Access to the configuration screen to maintain behavior settings that access ExtraView via the API. Write access is needed to control this |
|
CF_AREA |
Maintain the list of Business Areas for the inbuilt AREA field. Write access is needed to control this |
|
CF_CATEGORY |
Maintain the list of Categories for the inbuilt CATEGORY field. Write access is needed to control this |
|
CF_COMPANY_SETTINGS |
Access the administration screen to set your company name, address and contact information. Write access is needed to control this |
|
CF_DATA_DICTIONARY |
Access to the data dictionary where you create and maintain inbuilt and user defined fields & other objects, including modifying their title, display type, basic behavior and default values. Write access is needed to control this |
|
CF_DEBUG_SETTINGS |
Access the behavior settings for debugging options and the user custom classname. Write access is needed to control this |
|
CF_DISPLAY_INFO |
Access the behavior settings for fonts and colors to be used within ExtraView screens and layouts. Write access is needed to control this |
|
CF_DISPLAY_SETTINGS |
Control and set behavior settings that affect how screens and layouts are presented. Write access is needed to control this |
|
CF_EMAIL_SETTINGS |
Setup and administer email behavior settings. Write access is needed to control this |
|
CF_ENABLE_DISABLE_USER _ACCESS |
Access the administrative option to quiesce the ExtraView system for maintenance. Write access is needed to control this |
|
CF_ENVIRONMENT |
Access the behavior settings that maintain physical paths and URL information for accessing ExtraView. Write access is needed to control this |
|
CF_ESCALATION_RULES |
Escalation Rules |
|
CF_EXPIRE_PASSWORD |
This key controls access to allow the administrator to expire password in user accounts. Write access is needed to control this |
|
CF_FILE_IMPORT |
Access to the File Import Utility to upload and import a tab-delimited or comma-delimited data file containing records. Write access is needed to control this |
|
CF_HIERARCHY |
Reporting Hierarchies |
|
CF_HIERARCHY_LEVEL |
Reporting Hierarchy Levels |
|
CF_INSTALLATION_DETAILS |
Setup the basic behavior settings of the ExtraView installation. Write access is needed to control this |
|
CF_INTEREST_LIST |
Interest List access. Note that giving read and write access to this key will allow non-administrative users access to maintain interest lists. This access is from a prompt on the Notification section of their Personal Options screen. Be aware that the end-user will have full access to interest list maintenance if they are given this permission |
|
CF_ITEMDATA |
Access the administrative function to export item data to an XML formatted file. The file can be used for import to a different ExtraView schema. Read access is needed to control this |
|
CF_LAYOUT |
Create and alter the layouts for all screens and reports. Write access is needed to control this |
|
CF_LAYOUT_TYPE |
Maintain the list of types of screen and report layouts that can be defined. Write access is needed to control this |
|
CF_LICENSE |
The End User License Agreement (EULA) for ExtraView. Write access is needed to control this |
|
CF_LOCALIZE |
Access to this key allows locale-specific titles to be added to metadata field values. Write access is needed to control this |
|
CF_MANAGE_USER_CONNECTION |
Manage and disconnect users connection to ExtraView, releasing licenses back to the common pool. This is only used for concurrent license installations. Write access is needed to control this |
|
CF_METADATA |
Provide access to the export function where system metadata is dumped in XML format. Read access is needed to control this |
|
CF_METADATA_UPDATER |
Imports XML from a formatted file created with the XML export utility, and updates ExtraView with the information. Please make sure you backup your installation before using! Write access is needed to control this |
|
CF_MODULE |
Access to maintain the list of modules (MODULE_ID) within products (PRODUCT_NAME). Write access is needed to control this |
|
CF_MODULE_TYPE |
Create and manage the list of module types. Note that this key may be deprecated in a future release. Write access is needed to control this |
|
CF_OBJECT_IMPORT |
Access to import item data from an imported file prepared in XML format. Write access is needed to control this |
|
CF_PERSONAL_OPTIONS |
This key controls access to each user role's personal option link that appears in the title bar of the screen. Write access is needed to control this |
|
CF_PRIORITY |
Maintain the list of values for the inbuilt PRIORITY field. Write access is needed to control this |
|
CF_PRODUCT |
Maintain the list of values for the inbuilt PRODUCT_NAME field. Write access is needed to control this |
|
CF_PRODUCT_LINE |
Maintain the list of values for the inbuilt PRODUCT_LINE field. Write access is needed to control this |
|
CF_PROJECT |
Access and maintain the list of Projects (PROJECT) within Business Areas (AREA). Write access is needed to control this. There is no use case to have read or write access to this key unless the same access is given to the CF_AREA permission key |
|
CF_RELATIONSHIP_GROUP |
This key controls access to the global settings and names of issue relationship groups. Write access is needed to control this |
|
CF_RELATIONSHIP_GROUP_DELETE _BUTTON |
This key controls access to delete an issue from within a relationship group. Write access is needed to control this |
|
CF_RELATIONSHIP_GROUP_EDIT |
This key controls whether a user role may modify an existing relationship group of issues. Write access is needed to control this |
|
CF_RELATIONSHIP_GROUP_EDIT _PROBLEM_BUTTON |
This permission key controls the presence of the "Edit issue" button on the relationship group screen. Write access is needed to control this |
|
CF_RELATIONSHIP_GROUP_PROBLEM _ADD_PROBLEM_BUTTON |
This key controls whether a user role may add an issue to an existing relationship group of issues. Write access is needed to control this |
|
CF_RELATIONSHIP_GROUP_VIEW _PROBLEM_BUTTON |
This permission key controls the presence of the "View" button on the relationship group screen. Write access is needed to control this |
|
CF_REPORT_SETTINGS |
This key grants permissions to alter the behavior settings that affect reports and queries. Write access is needed to control this |
|
CF_REPORT_USER |
Create and manage reports created by individual users |
|
CF_RESOLUTION |
Maintain the list of values for the inbuilt RESOLUTION field. Write access is needed to control this |
|
CF_RUN_AS_ADMIN |
This permission setting allows the user who is performing a file import to ignore field level permissions. The primary purpose of this is to speed up the importation of extremely large volumes of records. It's unlikely that this setting is needed with less than 25,000 records within the import file |
|
CF_SESSION_SETTINGS |
This key controls access to the maintenance screen for system-wide behavior settings. Write access is needed to control this |
|
CF_SEVERITY |
Maintain the list of values for the inbuilt SEVERITY_LEVEL field. Write access is needed to control this |
|
CF_SSO_SETTINGS |
Set up ExtraView to work with SSO and LDAP servers |
|
CF_STATISTICS |
This provides access to summary information about users, user roles and usage patterns.. Read access is needed to control this |
|
CF_STATUS |
Maintain the list of values for the inbuilt STATUS field. Write access is needed to control this |
|
CF_STATUS_RULES |
This controls access to the definition screen for rules that apply to status changes. Sets up the business rules for workflow based on status. Write access is needed to control this |
|
CF_SYSTEM_LOG |
Controls access to reporting on all metadata changes in the administration log. Read access is needed to control this |
|
CF_SYSTEM_LOG_TYPE |
The list of activities in the administration log. New entries must be supported by program changes at the source code level |
|
CF_SYSTEM_SIGNON |
Controls access to view the log entries that track the sign on and sign off activities of all users. Read access is needed to control this |
|
CF_TEMPLATE |
Controls access to create and edit email templates to use in communication with internal and external users when updating issues |
|
CF_TRANSLATOR |
Controls access to translate all system messages and prompts into different languages. Write access is needed to control this |
|
CF_UDF_LIST |
Controls access to maintain the list of values for User Defined Fields stored within ExtraView. This is a single key that controls access to all lists. Each member of the list also has an individual security key. Write access is needed to control this |
|
CF_UPLOAD_COMPANY_LOGO |
Controls access to the feature that allows an administrator to upload a Company Logo |
|
CF_UPLOAD_USER_TEMPLATES |
Write access to this key allows the uploading of Server-Side Templates for use with the ExtraView API |
|
CF_USER_FILE_IMPORT |
Controls access to the File Import - User Information feature. Write access allows the administrator to create new users with this facility |
|
CF_USER_SETTINGS |
This key controls access to the behavior settings and options associated with user names and users. Write access is needed to control this |
|
CF_VERSION_INFO |
This key controls access to version information for ExtraView and its supporting software. Read access is needed to control this |
|
CF_VIEW_APP_SERVER_LOG |
Read access to this permission key will place a button on the System Log administration screen. Pressing this button will display the application server log in a new window. |
|
CF_WORKFLOW_DEFAULTS |
This key controls access to the behavior settings and options associated with workflow. Write access is needed to control this |
|
MENU_ADD_PROBLEM |
This setting controls access to the Add issue layout from the main navigation bar Add button. Write access is needed to control this |
|
MENU_ADMINISTRATION |
This setting controls access to the Administration system from the main navigation bar Administration button. Write access is needed to control this |
|
MENU_EDIT |
This setting controls access to the Update button on any Edit screen. Write access is needed to control this |
|
MENU_DRILLDOWN_ON_NAV_BAR |
This permission key controls the presence of the drilldown box on the navigation bar. Read access is needed to be able to access the drilldown box. |
|
MENU_HOME |
This key controls access to the Home button on the Navigation bar. Read access is needed to control this |
|
MENU_RESOLUTION |
This key controls access to the Query (Search & Reports) screen. Read access is needed to control this |
|
MOBILE_NAV_BAR |
This controls the visibility of the navigation bar within the mobile client. You require read permission to see the nvigation bar |
|
PR_ADD_PROBLEM.ALT_ID |
Alternate ID |
|
PR_ADD_PROBLEM.AREA |
Business Area |
|
PR_ADD_PROBLEM.ASSIGNED_TO |
Assigned To |
|
PR_ADD_PROBLEM. ATTACH_CONTENT_TYPE |
This controls the presence of the content type on an attachment record. This can be seen with read access, but cannot be written to |
|
PR_ADD_PROBLEM. ATTACH_CREATED_BY_USER |
This controls the presence of the user's name who created the attachment. This can be seen with read access, but cannot be written to |
|
PR_ADD_PROBLEM. ATTACH_DATE_CREATED |
This controls the presence of the date an attachment was created. This can be seen with read access, but cannot be written to |
|
PR_ADD_PROBLEM. ATTACH_DELETE |
This allows users to delete attachments from the ADD_PROBLEM screen layouts. If the ATTACH_SELECT button is placed on the layout and the user role has permission to this, then it also enables a button that allows the user to select and delete multiple attachments at one time |
|
PR_ADD_PROBLEM. ATTACH_FILE_DESC |
This controls the presence of the attachment description, when you are entering the file name to be uploaded to an attachment. Write access is needed to control this |
|
PR_ADD_PROBLEM. ATTACH_FILE_NAME |
This controls the presence of the attachment file name on an attachment record. This can be seen with read access, but cannot be written to |
|
PR_ADD_PROBLEM. ATTACH_FILE_SIZE |
This controls the presence of the file size on an attachment record. This can be seen with read access, but cannot be written to |
|
PR_ADD_PROBLEM. ATTACH_HIST_TIMESTAMP |
Controls the presence of a timestamp that shows when an attachment was accessed, This is viewable with the read permission key on the History screen of an attachment |
|
PR_ADD_PROBLEM. ATTACH_LAST_UPDT_COMPANY |
Controls the presence of the name of a user’s company that accessed an attachment, and viewable with the read permission key on the History screen of an attachment |
|
PR_ADD_PROBLEM. ATTACH_PATH |
This controls the presence of the original client attachment path to an attachment file, on an attachment record. This can be seen with read access, but cannot be written to |
|
PR_ADD_PROBLEM. ATTACH_THUMBNAIL |
Controls the presence of a thumbnail of an attachment of an image type, when the record that contains the attachment is viewed on the edit screen or on a report containing the ATTACHMENT record |
|
PR_ADD_PROBLEM. ATTACHMENT |
This is the controlling key for attachments. Without read and write permission to this key, attachments will not appear on the add issue screen layout. Once this key gives permission to the user role, the remaining attachment keys control the read / write permissions to the individual fields |
|
PR_ADD_PROBLEM. ATTACHMENT_ADD |
This controls the Add button on attachments. Write access is needed to control this |
|
PR_ADD_PROBLEM.ATTACHMENT_DELETE |
This allows the deletion of attachments from ADD_PROBLEM layouts. If the ATTACH_SELECT button is placed on the layout, then it also enables a button that allows the user to select and delete multiple attachments at one time |
|
PR_ADD_PROBLEM.CATEGORY |
Category |
|
PR_ADD_PROBLEM.CC_EMAIL |
Controls the presence of the CC Email input box on the add screen. The user role should have read and write permission to this field to allow the users to input email addresses on this line |
|
PR_ADD_PROBLEM. CC_EMAIL_BUTTON |
Controls the presence of a button by the CC Email input box on the add screen. The user role should have read permission to this field to allow the user to pop up a list of users that can be added to the CC Email box |
|
PR_ADD_PROBLEM.COMMENTS |
Comments |
|
PR_ADD_PROBLEM.CONFIRM_ALLOW_EDIT |
This permission key controls the visibility of the Edit button on the Add Confirmation screen |
|
PR_ADD_PROBLEM.CONTACT |
Contact |
|
PR_ADD_PROBLEM.DATE_CREATED |
Date Created |
|
PR_ADD_PROBLEM.DESCRIPTION |
Description |
|
PR_ADD_PROBLEM.EMAIL_CUSTOMER |
If the user role has Read permission to this field, the checkbox to allow email to be sent to external users will be visible |
|
PR_ADD_PROBLEM.EMAIL_SWITCH |
This key enables or disables the Generate Email checkbox for the user role. If there is no Read access to this key, the Generate Email checkbox is not visible, and its setting is obtained from the value of the behavior setting named GENERATE_EMAIL_BOX. |
|
PR_ADD_PROBLEM.ID |
Controls access to the inbuilt field named ID |
|
PR_ADD_PROBLEM.INTEREST_LIST |
If the user role has write access to this permission key, they will see a checkbox in the notification area of the add screen and will be able to add themselves to an interest list for the issue they are creating. The user will also be able to add other users to an interest list for the issue via an input box |
|
PR_ADD_PROBLEM.ITEM_ID |
Controls access to the inbuilt field named ITEM_ID |
|
PR_ADD_PROBLEM.MAILING_LIST |
Controls access to the distribution email list for the issue. When the user has Read access to this permission key, an icon is also available to refresh the list |
|
PR_ADD_PROBLEM.MODULE_ID |
Module ID - this is the main key that should be used to control the Module field on a form |
|
PR_ADD_PROBLEM.ORIGINATOR |
Originator of the problem |
|
PR_ADD_PROBLEM.OWNER |
The owner of the issue |
|
PR_ADD_PROBLEM.PRIORITY |
The priority of the issue |
|
PR_ADD_PROBLEM.PRIVACY |
The Privacy of the issue |
|
PR_ADD_PROBLEM. PROBLEM_RELEASE_DELETE |
This key controls the presence of a check box on a repeating row record, that allows you to delete the current row. Write access is needed to control the checkbox |
|
PR_ADD_PROBLEM.PRODUCT_LINE |
Product Line |
|
PR_ADD_PROBLEM.PRODUCT_NAME |
Product name |
|
PR_ADD_PROBLEM.PROJECT |
Project |
|
PR_ADD_PROBLEM.RELEASE |
This is the controlling key for repeating row records. If you have read and write permission to this key, the entire repeating row structure will be available to the user role, and access to the individual fields on the repeating row structure is controlled by the security permission keys for each field |
|
PR_ADD_PROBLEM. RELEASE_ASSIGNED_TO |
Release Assigned To |
|
PR_ADD_PROBLEM. RELEASE_DATE_CREATED |
Release Date Created |
|
PR_ADD_PROBLEM.RELEASE_FIXED |
Release Fixed |
|
PR_ADD_PROBLEM.RELEASE_FOUND |
Release Found |
|
PR_ADD_PROBLEM.RELEASE_OWNER |
Release Owner |
|
PR_ADD_PROBLEM. RELEASE_PRIORITY |
Release Priority |
|
PR_ADD_PROBLEM. RELEASE_PRODUCT |
Release Product |
|
PR_ADD_PROBLEM. RELEASE_RESOLUTION |
Release Resolution |
|
PR_ADD_PROBLEM. RELEASE_SEVERITY |
Release Severity |
|
PR_ADD_PROBLEM.RELEASE_STATUS |
Release Status |
|
PR_ADD_PROBLEM. RELEASE_TIMESTAMP |
Release Timestamp |
|
PR_ADD_PROBLEM.RESOLUTION |
Resolution |
|
PR_ADD_PROBLEM.SEVERITY_LEVEL |
Severity Level |
|
PR_ADD_PROBLEM.SHORT_DESCR |
Short description or Title of an issue |
|
PR_ADD_PROBLEM. SHOW_PRIVATE_IN_PRIVACY_LIST |
When you give a user role write access to this key, they will be able to enter Private issues within the privacy field |
|
PR_ADD_PROBLEM. SHOW_PUBLIC_IN_PRIVACY_LIST |
When you give a user role write access to this key, they will be able to enter Public issues within the privacy field |
|
PR_ADD_PROBLEM.STATUS |
Status |
|
PR_ADD_PROBLEM.TIMESTAMP |
Last date modified |
|
PR_RESOLUTION. ALLOW_EDIT_CLOSED |
Access to this key controls whether a user role can edit "closed" issues, as defined by the behavior setting named STATUS_CLOSED_NAME. |
|
PR_RESOLUTION. ALLOW_EDIT_NEXT_PREVIOUS |
Access to this key controls whether a user role can move from one issue in a list created from a report, to the next or the previous issue in the report list, reviewing and updating each issue in turn. When this is enabled for a role, there will be two additional buttons on the edit screen of each issue allowing the user to move back and forwards in the list of issues on the current page of the report in which the user first started to edit issues. |
|
PR_RESOLUTION.ALT_ID |
Alternate ID |
|
PR_RESOLUTION.AREA |
Business Area |
|
PR_RESOLUTION.ASSIGNED_TO |
Assigned To |
|
PR_RESOLUTION. ATTACH_CONTENT_TYPE |
This controls the presence of the content type on an attachment record. This can be seen with read access, but cannot be written to |
|
PR_RESOLUTION. ATTACH_CREATED_BY_USER |
This controls the presence of the user's name who created the attachment. This can be seen with read access, but cannot be written to |
|
PR_RESOLUTION.ATTACH_DATE _CREATED |
This controls the presence of the date an attachment was created. This can be seen with read access, but cannot be written to |
|
PR_RESOLUTION.ATTACH_DELETE |
This allows users to delete attachments from the EDIT_PROBLEM screen layouts. If the ATTACH_SELECT button is placed on the layout and the user role has permission to this, then it also enables a button that allows the user to select and delete multiple attachments at one time |
|
PR_RESOLUTION. ATTACH_FILE_DESC |
This controls the presence of the attachment description, when you are entering the file name to be uploaded to an attachment. Write access is needed to control this |
|
PR_RESOLUTION.ATTACH_FILE_NAME |
This controls the presence of the attachment file name on an attachment record. This can be seen with read access, but cannot be written to |
|
PR_RESOLUTION.ATTACH_FILE_SIZE |
This controls the presence of the file size on an attachment record. This can be seen with read access, but cannot be written to |
|
PR_RESOLUTION.ATTACH_PATH |
This controls the presence of the original client attachment path to an attachment file, on an attachment record. This can be seen with read access, but cannot be written to |
|
PR_RESOLUTION.ATTACHMENT |
This is the controlling key for attachments. Without read and write permission to this key, attachments will not appear on the edit issue screen layout. Once this key gives permission to the user role, the remaining attachment keys control the read / write permissions to the individual fields |
|
PR_RESOLUTION.ATTACHMENT_ADD |
This controls the Add button on attachments. Write access is needed to control this |
|
PR_RESOLUTION. ATTACHMENT_DELETE |
This is to enable and disable the delete attachment button |
|
PR_RESOLUTION.ATTACHMENT_EDIT |
Controls whether a user role may edit the attachment description of a previously uploaded attachment. Write permission is needed for this |
|
PR_RESOLUTION.ATTACHMENT_VIEW |
Controls whether a user role may view a previously uploaded attachment. Read or write permission is needed for this |
|
PR_RESOLUTION.CATEGORY |
Category |
|
PR_RESOLUTION.CC_EMAIL |
Controls the presence of the CC Email input box on the edit screen. The user role should have read and write permission to this field to allow the users to input email addresses on this line |
|
PR_RESOLUTION.CC_EMAIL_BUTTON |
Controls the presence of a button by the CC Email input box on the edit screen. The user role should have read permission to this field to allow the user to pop up a list of users that can be added to the CC Email box |
|
PR_RESOLUTION.CLONE |
Controls the presence of a Clone button on the edit screen toolbar. The user should have write permission to be able to clone issues |
|
PR_RESOLUTION.COMMENTS |
Comments |
|
PR_RESOLUTION.CONTACT |
Contact |
|
PR_RESOLUTION.DATE_CREATED |
Date Created |
|
PR_RESOLUTION.DELETE_BUTTON |
Controls the presence of the Delete button on the edit screen. If a user role has write access to this key they will be able to delete the issue |
|
PR_RESOLUTION.DESCRIPTION |
Description |
|
PR_RESOLUTION.EDIT_BUTTON |
Controls whether a user role has access to an Edit button within reports and email. Write access is needed for this control |
|
PR_RESOLUTION. EDIT_LOGAREA_FIELDS |
Controls whether a user role is allowed to edit historic logarea fields such as COMMENTS. Normally only administrators will be given this control, through write access to the key |
|
PR_RESOLUTION.EMAIL_BUTTON |
Determines whether a user role has the Email button on the toolbar of the Edit screen |
|
PR_RESOLUTION.EMAIL_CUSTOMER |
If the user role has Read permission to this field, the checkbox to allow email to be sent to external users will be visible |
|
PR_RESOLUTION. EMAIL_FILTER_SCREEN |
Read permission to this key controls access to the search filter screen for ad hoc email |
|
PR_RESOLUTION.EMAIL_SWITCH |
This key enables or disables the Generate Email checkbox for the user role. If there is no Read access to this key, the Generate Email checkbox is not visible, and its setting is obtained from the value of the behavior setting named GENERATE_EMAIL_BOX. |
|
PR_RESOLUTION.HISTORY_BUTTON |
Read access to this key gives access to the history (audit trail) of an issue. History buttons can be placed on the edit screen and reports. |
|
PR_RESOLUTION.ID |
Controls access to the inbuilt field named ID |
|
PR_RESOLUTION.INTEREST_LIST |
If the user role has write access to this permission key, they will see a checkbox in the notification area of the edit screen and will be able to add themselves to an interest list for the issue they are updating. The user will also be able to add other users to an interest list for the issue via an input box |
|
PR_RESOLUTION.ITEM_ID |
Controls access to the inbuilt field named ITEM_ID |
|
PR_RESOLUTION.KEYWORD |
Determines whether a user role may perform searches by keyword, through the KEYWORD field on a filter layout. Read access is needed |
|
PR_RESOLUTION. LAST_CHANGE_USER |
Last user to update an issue |
|
PR_RESOLUTION.MAILING_LIST |
Controls access to the distribution email list for the issue. When the user has Read access to this permission key, an icon is also available to refresh the list |
|
PR_RESOLUTION. MASS_UPDATE_ISSUES |
Controls access to the Mass Update button on report output. Write permission is needed to perform mass updates. Normally this facility is only given to key personnel |
|
PR_RESOLUTION.MODULE_ID |
Module ID - this is the main key that should be used to control the Module field on a form |
|
PR_RESOLUTION.MONTHS _IN_STATUS |
Number of months a problem has remained in its current status |
|
PR_RESOLUTION.MONTHS_OPEN |
Number of months a problem has been open |
|
PR_RESOLUTION.OWNER |
The Owner of an issue |
|
PR_RESOLUTION.PRIORITY |
The priority of the issue |
|
PR_RESOLUTION.PRIVACY |
The Privacy of the issue |
|
PR_RESOLUTION. PROBLEM_RELEASE_DELETE |
This key controls the presence of a check box on a repeating row record, that allows you to delete the current row. Write access is needed to control the checkbox |
|
PR_RESOLUTION.PRODUCT_LINE |
Product Line |
|
PR_RESOLUTION.PRODUCT_NAME |
Product name |
|
PR_RESOLUTION_PROBLEM. PROBLEM_RELEASE_DELETE |
This key controls the presence of a check box on a repeating row record, that allows you to delete the current row. Write access is needed to control the checkbox |
|
PR_RESOLUTION.PROJECT |
Project |
|
PR_RESOLUTION. RELATIONSHIP_GROUP |
Relationship Groups on Edit Screen |
|
PR_RESOLUTION. RELATIONSHIP_GROUP_ID |
Controls visibility of the relationship group ID on the edit screen |
|
PR_RESOLUTION. RELATIONSHIP_GROUP_OWNER |
Read access to this key provides the user role with visibility of the owner of relationship groups |
|
PR_RESOLUTION. RELATIONSHIP_GROUP_TITLE |
Read access to this key provides the user role with visibility of the title of relationship groups |
|
PR_RESOLUTION. RELATIONSHIP_GROUP_TYPE |
Read access to this key provides the user role with visibility of the type of relationship groups |
|
PR_RESOLUTION. RELATIONSHIP_GRP_ADMIN |
This permission key controls access to the Manage Relationship Groups button that is placed on the menubar of edit screens. When permission is granted to this key, users can access the management screen for relationship groups directly from the edit screen. |
|
PR_RESOLUTION. RELATIONSHIP_GRP_PARENT_ID |
Read access to this key provides visibility to the parent issue of the relationship group |
|
PR_RESOLUTION.RELEASE |
This is the controlling key for repeating row records. If you have read and write permission to this key, the entire repeating row structure will be available to the user role, and access to the individual fields on the repeating row structure is controlled by the security permission keys for each field |
|
PR_RESOLUTION. RELEASE_ASSIGNED_TO |
Release Assigned To |
|
PR_RESOLUTION. RELEASE_DATE_CREATED |
Release Date Created |
|
PR_RESOLUTION.RELEASE_FIXED |
Release Fixed |
|
PR_RESOLUTION.RELEASE_FOUND |
Release Found |
|
PR_RESOLUTION.RELEASE_OWNER |
Release Owner |
|
PR_RESOLUTION.RELEASE_PRIORITY |
Release Priority |
|
PR_RESOLUTION.RELEASE_PRODUCT |
Release Product |
|
PR_RESOLUTION. RELEASE_RESOLUTION |
Release Resolution |
|
PR_RESOLUTION.RELEASE_SEVERITY |
Release Severity |
|
PR_RESOLUTION.RELEASE_STATUS |
Release Status |
|
PR_RESOLUTION. RELEASE_TIMESTAMP |
Release Timestamp |
|
PR_RESOLUTION.RESOLUTION |
Resolution |
|
PR_RESOLUTION.RG_EMAIL_BUTTON |
Provides access to the email button on the Relationship Group Filter Screen. |
|
PR_RESOLUTION.RG_MERGE_BUTTON |
Provides access to the merge button on the Relationship Group Filter Screen |
|
PR_RESOLUTION.RG_SPLIT_BUTTON |
Provides access to the split button on the Relationship Group Filter Screen |
|
PR_RESOLUTION. SEARCH_ATTACHMENTS |
This key controls the searching of attachments on the query filter screens. When this key has Write access, a checkbox appears underneath the KEYWORD field, giving the ability to search through attachments for the user role |
|
PR_RESOLUTION.SEVERITY_LEVEL |
Severity Level |
|
PR_RESOLUTION.SHORT_DESCR |
Short description or Title of an issue |
|
PR_RESOLUTION. SHOW_PRIVATE_IN_PRIVACY_LIST |
When you give a user role write access to this key, they will be able to enter Private issues within the privacy field |
|
PR_RESOLUTION. SHOW_PUBLIC_IN_PRIVACY_LIST |
When you give a user role write access to this key, they will be able to enter Public issues within the privacy field |
|
PR_RESOLUTION.START_DATE |
This key offers the user role the ability to enter the Created Date as the lower value in a query filter when searching for an issue. Typically used in conjunction with PR_RESOLUTION.STOP_DATE |
|
PR_RESOLUTION.START_UPDATE |
This key offers the user role the ability to enter the Last Modified Date as the lower value in a query filter when searching for an issue. Typically used in conjunction with PR_RESOLUTION.STOP_UPDATE. Note that the data dictionary setting “Filter criteria” must be set to Yes for this field to work. |
|
PR_RESOLUTION.STATUS |
Status |
|
PR_RESOLUTION.STATUS_HIST |
Status History |
|
PR_RESOLUTION.STOP_DATE |
This key offers the user role the ability to enter the Created Date as the upper value in a query filter when searching for an issue. Typically used in conjunction with PR_RESOLUTION.START_DATE |
|
PR_RESOLUTION.STOP_UPDATE |
This key offers the user role the ability to enter the Last Modified Date as the upper value in a query filter when searching for an issue. Typically used in conjunction with PR_RESOLUTION.START_UPDATE. Note that the data dictionary setting “Filter criteria” must be set to Yes for this field to work. |
|
PR_RESOLUTION.TIMESTAMP |
Last date modified |
|
PR_RESOLUTION.VIEW_BUTTON |
Controls the visibility of the View button on reports. Read access is required for this |
|
SE_LOGIN_MESSAGE |
Provides access to alter the sign on message that appears on all users' Home Pages. Write access is required for this function |
|
SE_PRIVACY_GROUP |
Write access allows the creation and management of the list of privacy groups |
|
SE_SECURITY_GROUP |
Create and manage the list of user roles with this key. Write access is needed |
|
SE_SECURITY_MODULE |
Create and maintain the list of security objects. Normally these are created automatically by ExtraView. Write access is required |
|
SE_SECURITY_PERMISSION |
This key controls access to update the security permission keys within the installation. Write access is required. Without access to this key, no security permissions can be altered |
|
SE_SECURITY_USER |
Provides access to create and maintain user accounts and user account details. Write access is needed |
|
SE_USER_ATTRIBUTES |
If the user's role has permission to this key, then they are able to use the user defined attributes that have been configured within the data dictionary, as fields for a custom operation on the user account administration screens. The use of this feature is always accompanied by user custom code |
|
SR_ALLOW_ADVANCED_QUERIES |
When this setting is YES, the user role can create, edit, save, delete and execute reports composed with the Advanced Query option. When this is set to NO, reports composed with Advanced Query may only be run, and only if the user role has permission to the appropriate SR_PUBLIC_COLUMN_REPORT and SR_PERSONAL_COLUMN_REPORT permission keys |
|
SR_ALLOW_EXPANDED_QUERIES |
When the user role has read access to this key, the users can switch between condensed and expanded queries. When this key is set to no access, the users will only be able to create queries with the condensed mode and will not be able to switch into the expanded mode |
|
SR_DASHBOARD_ON_HOME_PAGE |
Read access provides the user role with access to an executive dashboard report on the home page. Note that this report must be configured in user custom code |
|
SR_KB_ON_HOME_PAGE |
Read access provides the user role with access to search the inbuilt Knowledgebase business area from the home page |
|
SR_SET_HOME_PAGE_REPORTS |
Read access to this key allows the user to select and set their Home Page reports |
|
SR_PERSONAL_AGING |
Read access determines access to save personal aging reports and to place personally created aging report on the user's home page |
|
SR_PERSONAL_CHART |
Read access determines access to save personal charts and to place personally created charts on the user's home page |
|
SR_PERSONAL_COLUMN_REPORT |
Determines the ability to create and run personal reports. Both Read and Write access can be used to determine the functionality required |
|
SR_PERSONAL_GEOSPATIAL |
Read access for this key gives the ability to view and run personal Geospatial reports. Write access gives the ability to create new personal Geospatial reports |
|
SR_PERSONAL_SUMMARY_REPORT |
Determines the ability to create and run personal summary reports. Both Read and Write access can be used to determine the functionality required |
|
SR_PUBLIC_AGING |
Read access determines access to save public aging reports and to place public aging reports on the user's home page |
|
SR_PUBLIC_CHART |
Read access determines access to save public charts and to place public charts on the user's home page |
|
SR_PUBLIC_GEOSPATIAL |
Read access for this key gives the ability to view and run public Geospatial reports. Write access gives the ability to create new personal Geospatial reports |
|
SR_PUBLIC_SUMMARY_REPORT |
Determines the ability to create and run public summary reports. Both Read and Write access can be used to determine the functionality required |
|
SR_PUBLIC_WORKSPACE |
This permission key controls end user access to view and select from the list of public workspaces to which the user has permission. Typically, this means the user must have access to the business area, project and user role in which the workspace is saved |
|
SR_PERSONAL_LINKED_REPORT |
This key controls access to the linked report button on the Search screen |
|
SR_PUBLIC_LINKED_REPORT |
Read access determines access to the linked report feature |
|
SR_PUBLIC_COLUMN_REPORT |
This key controls access to public reports. Read access gives the ability to run public reports, Write access gives the ability to create public reports |
|
SR_RELATIONSHIP_GROUP |
This key controls access to the Group Issues button on column reports and Quicklist reports. Write access is needed to control this |
|
SR_SAVE_PUBLIC_FILTERS |
This provides the ability to allow the user role to save and delete shared report filters on the Query screen and report editors |
|
SR_USERROLE_ADMIN |
This key enables access to admin reports by the user role. Read access is required to run the reports and write access is required to create and modify the reports |
|
SR_USERROLE_AGING |
Read access for this key gives the ability to see and run aging reports created for the current user role. Write access gives the ability to create these aging reports |
|
SR_USERROLE_CHART |
Read access for this key gives the ability to see and run charts created for the current user role. Write access gives the ability to create these charts |
|
SR_USERROLE_COLUMN_REPORT |
Read access for this key gives the ability to see and run reports created for the current user role. Write access gives the ability to create these reports |
|
SR_USERROLE_GEOSPATIAL |
Read access for this key gives the ability to view and run public Geospatial reports for the current user role. Write access gives the ability to create new Geospatial reports for the current user role |
|
SR_USERROLE_SUMMARY_REPORT |
Determines the ability to create and run summary reports for the current user role. Both Read and Write access can be used to determine the functionality required |
