PerfectApps will consider each of the combinations using a hierarchical model as follows:
First Level: |
Stage = All |
Role = All
|
|
Second Level: |
Stage = Specific |
Role = All (Overrides 1st level)
|
|
Third Level: |
Stage = All |
Role = Specific (Overrides 1st and 2nd level)
|
|
Fourth Level: |
Stage = Specific |
Role = Specific (Overrides 1st, 2nd and 3rd level)
|
The possible state selections are as follows (not applicable to all objects):
Default |
No state marker |
The object will retain the same state that it had the last time the app instance was submitted.
|
|
Normal |
|
The object is visible and editable.
|
|
Read-only |
|
The object is visible but not editable.
|
|
Disabled |
|
The object is visible but grayed out and not editable.
|
|
Hidden |
|
The object is hidden from view.
|
Within the State section of an object's properties, you may also choose to set the field as required by checking the Mandatory answer check box. For additional information on this option see the Mandatory Answer Property topic in this help guide.
See also: Sequence of Events for Field States
Return to: Limiting User Access to App Fields, Designing an App
