Setting Up Conditions

There are two kinds of conditions: conditions of approval and general conditions. The two classes share the same logic but you use them for different purposes. Use conditions of approval to define a list of requirements that citizens must meet to receive the approval for a permit or an inspection. Use a general condition to indicate a problem on the record, inspection, address, contact, or another application component. Generally, the condition severity is Lock, Hold, Notice, or Required. Administrators can manage conditions of approval and general conditions separately through the Conditions Maintenance portlet. For example, you can create a standard condition of approval for users to apply to a record and you can define the status options for conditions of approval.

All conditions and condition types support using template fields that you create using application-specific information (ASI) and application-specific information table (ASI Table) groups. To define an ASI and ASI Table Groups for a condition template, see the section, Creating a Condition Template.

Administrators establish security policies for condition types, and then set permissions in the Conditions Administration portlet. You configure the policies in the Security Policies Administration portlet as explained in Setting Up Security Policies in Setting Up Security Policies. To manage permissions and privileges, use the Conditions Administration portlet as explained in Assigning Conditions.

Click a topic title below for full details.