Manage topic field accessibility by state
Once you have defined topic states and fields, you define the level of access that users have to each field when a topic is in each of the workflow states.
You specify whether each field is required, editable (but not required), visible (but not editable), or hidden in each state. If you make a field required for a state, a topic cannot be saved in that state until the user provides a value for the field.
The access levels that you define are enforced when:
- A user edits a topic that is currently in that state.
- A user assigns that state to the topic. For example, suppose that the RESOLUTION field is editable in the Reviewed state and required in the Closed state. While the topic state is Reviewed, users can leave the RESOLUTION field empty. However, the user who changes the topic's state to Closed is required to provide a resolution.
- In addition, when a topic is created during the process of saving an attachment to a topic from another page in the application (if enabled as an attachment type for the topic workflow configuration), the TOPIC_NAME is required but no other requirements for the Initial state are enforced until the first time that topic is edited.
Access levels apply only when a topic is edited. When a topic is viewed, all non-hidden fields are display-only.
Parent topic: Manage field access