Field constraints
Field constraints define the basic characteristics of the information that can be recorded for an application, such as whether certain information is required, display-only, or not present.
Different constraints can be defined for different application milestones. For example, you can make primary site and applicant information required for the first milestone of an application type, and display-only when the application reaches a later milestone.
Because Rhythm for Civics might have different requirements, you can define a separate set of constraints for the portal. For example, a field that is display-only in Infor Operations and Regulations might not be shown at all in Rhythm for Civics.
The constraints for Rhythm for Civics are shown on a separate Portal Setup tab when you select the node in Application Workflow. Constraints for Infor Operations and Regulations are shown on the IPS Setup tab.
Note: There is no Portal Setup tab for case type constraints because customers do not start cases in Rhythm for Civics.