Changes

Adding Standard and Custom Fields to Level 1

1,231 bytes removed, 19:56, 10 September 2007
Custom Fields UTA Status Permissions
[[Image:Uta37.png]]
==Custom Fields UTA Status Permissions==
When you use [[Custom Field|custom fields]] in conjunction with the UTA an additional set of permissions are available. These permissions control the visibility and modifiability of the field at different statuses.
 
[[Image:Uta60.png]]
There are four options:
 
* '''Allow View Field''' - Defines the level 1 statuses at which the field can be viewed.
* '''Allow Modify Field''' - Defines the level 1 statuses at which the field can be modified.
* '''Deny View Field''' - Defines the level 1 statuses at which the field cannot be viewed.
* '''Deny Modify Field''' - Defines the level 1 statuses at which the field cannot be modified.
 
 
* These permissions are used in conjunction with the standard [[Role|role]] based permissions. So you must be in role to see a field AND the field needs to be visible at that status.
* If no UTA status permissions are set then the fields are only through the role permissions.
* This feature is available for all [[Custom Field|custom fields]] at levels 1, 2 and 3 in the UTA.
 
1. Click the '''Settings''' tab.
 
2. Click the '''Custom Fields''' link.
 
[[Image:Uta61.png]]
The [[Custom Field|custom field]] window is displayed.
[[Image:Uta62.png]]
==Adding Custom fields to the Contract Entity==
4,401
edits