Purpose: This document describes the properties associated with a permission.
Permission Properties

| Permission Properties |
 |
Key |
Enter a unique identifier that best describes the permission. |
 |
Category |
Enter a category for the permission or select one that has been previously entered. Typically, an application function that is easily recognized by an end-user is used for the text of a category. For example, financial reports, appointment scheduling, order entry, etc. |
 |
Description |
This property is used to further describe the permission. |
 |
Action |
Select the action to be invoked when this permission is denied.
- No Message - This option is used when no message needs to be displayed to the end user. For example:
- Programmatic Access - This option may be used for programmatic access when user intervention is not necessary.
- Field Level - If this is set for a field and its access is denied, the user will not be able to view the contents of the field (it will be blank). The actual data that is bound to the field is not changed, only its viewing state.
- Message - The message entered in the Message or Key text box will be displayed to the end-user.
- Message Key - The message key entered in the Message or Key text box will be looked-up and its corresponding text will be displayed to the user.
- Replace each Character - This selection is the same as the "No Message" selection, the only difference being that instead of blanks being displayed, the character "X" will be used to replace the field contents. Again, only the viewing state is changed with this selection, the actual data is unharmed.
|
 |
Message or Key |
Based on the selection made via the Action combo box, enter the text of the denied message or a localized key for display to the end-user. |
 |
Auditing* / Read Only |
- Application Events - When checked a log will be updated each time the permission is accessed. For example, if a Logon permission has this checkbox selected, a log entry will be created every time the event is accessed during the logon process.
- Data Events - This event works in conjunction with the actual form properties or business object settings. It is used to track data changes: creating records, editing records, or deleting records. Each CRUD function can be controlled via business properties settings providing developer control.
Note: These event exists at the permission level for flexibility. They are typically assigned to a permission at the role or user level. It is important to remember that a user cannot change a permission. Hence, if you select auditing at the root permission it cannot be disabled via the runtime application.
- Do Not Allow Read-only - This check box excludes the read-only choice from the action combo box at the role or user level. It simply does not make sense for some permissions to be allowed a read-only status. For example, form access should be either granted or denied, not read-only. For this reason, it is recommended all form permissions have this option checked.
|
* - Auditing functionality was not included with the 1.5 release of Strataframe. This functionality will become available with a future release.