Editing a field constraint for a milestone

The field constraints that you define for a milestone affect the behavior of the fields in an application at that milestone, and at any subsequent milestones.

For example, your agency might not allow the primary site to be changed after an application has reached an Inspections milestone. If you set the Primary Site constraint to display-only at that milestone, it is automatically set to display-only for the subsequent milestones as well.

  1. Select Project > Setup > Application Workflow.
  2. In the Application Types tree, browse to the constraints for the correct milestone.
  3. Click the Constraints node.
  4. Enable editing in the grid and select the constraint item that you want to edit.
    See Field constraint items.
    Note: If the Civics-specific Constraints feature is enabled, two tabs are shown when you select the Field Constraints node.
    • The IPS Setup tab defines the constraints that are applied in Infor Public Sector,
    • The Portal Setup tab defines a separate set of constraints for Rhythm for Civics.
  5. Select the correct option from the list in the Settings column.
  6. Optionally, select Required to make this field required.
    Note: If the Required check box is selected, the field must be available in Infor Public Sector. If you select Required and then select Display Only or Not Present from the Settings list, the value automatically changes to Default or Default Available when you save your changes.

    This restriction does not apply to the constraints on the Portal Setup tab.

  7. Click Save.