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.

For more information, see the CDR administration guides in the Infor Public Sector User and Administration Library on docs.infor.com.

The field constraints that are defined for application types in Infor Public Sector are also used in Rhythm for Civics.

If the Civics-specific Constraints feature in Infor Public Sector is not enabled, then the same constraints that are defined for Infor Public Sector are also applied in the portal.

If the Civics-specific Constraints feature is enabled, you can define a separate set of constraints for the portal. For example, a field that is display-only in Infor Public Sector might not be shown at all in Rhythm for Civics.

If this feature is enabled, then constraints for Rhythm for Civics are shown on a separate Portal Setup tab when you select the Field Constraints node in Application Workflow. Constraints for Infor Public Sector 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.