Creating a Condition Template

The condition templates are in fact application-specific information (ASI) groups. The options in the Template field of a condition or a condition type are all the ASI groups configured in Civic Platform. The steps to prepare condition templates are the same as preparing ASI groups for records. This section describes the key tasks that you must perform.

Topics

Defining ASI Group Data for Conditions

When you create a template for a condition, you configure the ASI group first. The ASI group name displays in the Template field when creating a condition or a condition type.


Note:

The template that you specify for a condition overrides the template, if any, that you associated with the condition type of the condition.


To define an ASI subgroup in an ASI table group for a condition template, and to define more subgroups in an ASI group, see Defining Custom Fields (Application Specific Information).

Setting Condition Template Permissions

Either ASI security settings or a customized ASI form layout can block a user or user group from viewing certain ASI fields and ASI tables of a condition template.

The permissions set for a standard condition always override the permissions set for the condition type to which it belongs. User level permissions override user-group level permissions. If a user has ASI security or ASI form layout permission at the same time, the strictest access setting applies.

There are various methods to control user and group access to condition template fields.

You can assign permission based on the user login to restrict access to application-specific information and application‑specific information (ASI) table data, including ASI groups, ASI subgroups, ASI table groups, ASI table subgroups, ASI fields, and ASI table fields. See Setting Up Security Policies in Setting Up Security Policies.


Note:

If you do not have access permission to an ASI group, the ASI group can still display as a condition template option. However, when you select the ASI group as the condition template, the template field does not display.


You can set the condition template field permissions in the ASI Form Layout tool and apply security for module, group, and user. See Designing Application Intake Forms.

You can set access within the Condition portlet and layout the design of condition templates. Follow the see the steps in Designing a Layout for the Condition Details Portlet.

Designing a Layout for the Condition Details Portlet

You can choose which fields you want to show in the Condition Details portlet, and you can customize those fields. You can add a label for the field, specify its width, apply a mask, and indicate sort order and display order. You can also specify how many items to display in an expanded and contracted list.

You must separately design the layout of system-defined condition fields and then design the layout of the condition template fields (ASI fields and ASI table fields).

  • To design the layout of system-defined condition fields, apply the edit view feature in the Condition Details portlet. See Designing Forms for Portlets.

  • To design the layout of the condition template fields (ASI fields and ASI table fields), you can create ASI screens for ASI groups. See Designing Application Intake Forms.

    If you defined one or more ASI screens for an ASI group, and you select the ASI group as the condition template, all the fields and tables in the ASI group display below the system-defined condition fields, with the layout you designed in the ASI screens.

    If you did not define an ASI screen for an ASI group, or you do not have permission to the ASI screen for the ASI group, after you select the ASI group as the condition template, all the fields and tables in the ASI group display below the system-defined condition fields, with the default layout.