Field states are persisted after an app is submitted. Fields that are hidden when the app is submitted will remain hidden when it is loaded the next time unless you choose to override this state. You may want to override this to control users' ability to see and change fields tightly.
You can:
•Use behaviors within the App is Submitted, App is Closed, or App is Opened behaviors. The Set State behavior command is used to control field state.
•Use the Object States Overview which provides a matrix to manage app objects and their states as the roles will see them during the various workflow stages. This is the recommended approach as it allows field states to be controlled visually and avoids the use of behaviors completely.
•Use a combination of both methods.
Return to: Limiting User Access to App Fields, Designing an App