Constraint Set Field Usage

Prerequisite: You must have the 'Constraints' role function enabled.

There are a few things to keep in mind when designing constraint sets:

• Partial Constraints – if the constraint set is made up of five fields and only four of them appear on the form, the constraint set still takes effect.
• Field Types – typically, constraint sets are made up of a series of drop-down fields. The constraint set may also contain text fields that are defaulted or computed. For example, you can use the Follow-Up1. (For Infection) Another term for a surveillance file, which is created when the user selects Yes from the Choose a follow-up action control. 2. (For RL6) A file related action taken after the file has been submitted. Examples of follow-ups include investigative notes, meetings with different parties, consultation with patient family. Type field, a text field that defaults to the type of follow-up being added, to determine the list items available in the one or more fields in the follow-up dialog. A constraint set may also contain one (and only one) multi pick-list field; if used, the multi-pick list cannot be embedded into the form.
• Constraint Overlapping – two different constraints on a form can share one or more fields. The field options in available for the shared fields come from an inner-join between the two constraint sets.
• Multi-Level Use – fields that make up a constraint set don’t all have to be on the main form or all in a sub form. Some of the fields can reside on the main form (parent) while the others appear in a dialog box (child). When this configuration is used, the selections made on the form affect the values that appear in the dialog box. The opposite is not true (e.g., selecting the Unit from the dialog does not filter the list of Programs/Services in the main form).
• Inline Grids – constraint sets are not supported in inline grids.