Expression builder scenarios

This scenario explains how to create the expression criteria that automatically set the Status to “Processing” when a user creates a specific record type. The expression uses the “onLoad” function for the record type of Building/Plan Review/Zoning Analysis and identifies the Target Portlet of Record Detail.

To build the expression criteria, refer to the How to create the execute fields for onLoad function for a new record section below.

To see the effect of this expression from a user experience, refer to the Where the Status field populates as “Processing” for the user section below.

1. User creates a new record type of Building > Plan Review > Zoning Analysis .> Zoning Analysis.

   

   The new application type appears and the status automatically updates to processing.

   

1. Create a new expression and navigate to the Expression name field.

2. Enter an Expression name. This scenario uses "New Record Status."

3. Select Record Detail from the Target portlet list to specify that the expression takes effect in the Record detail area.

   

4. Select BLDG in the Custom fields group for this step. Expressions require the Target Portlet and the respective Custom Fields Group and Custom Lists Subgroup when creating or editing an expression.

5. Hover over the Custom Fields Group field, to display the associated Record type for the selected Custom Fields Group, for informational purposes.

   

6. Optionally, use the Execute Order field to define the order you want Civic Platform to process the expression.

7. Select the Execute fields picker.

   

8. Expand Additional options and select the onLoad function.

   Civic Platform loads the onLoad function in the Execute Fields list.

9. In the Expressions area, do the following:

   1. Select the Field name to activate it.

   2. Open the Variables list, and expand Record detail.

   3. From the Fields list select the Status field.

      The expressions Field name populates with the record type and the record Status functions.

      

10. Select the Calculate expression field to activate it.

11. In the Calculate expression field, surround the new status for this record type in double quotes and then enter this phrase exactly: “Processing”

    “Processing” is the default value displaying in the Status field when a user creates a new record type for Building/Building Permit/Residential/New.

    

This scenario explains how to create the expression that automatically adds a row into an asset attribute table when a user saves an asset.

To build the expression criteria, refer to the steps in the Adding a new attribute table row section.

To see the effect of this expression from a user experience, refer to the Where to add a new row section.

Where to add a new row in the attribute table of an asset.

1. User creates a new asset with the asset group as HVAC, and the asset type as Boiler. The asset type belongs to an asset template Mechanical - Boiler that links to the attribute table Attribute Table_1.

   

2. The asset saves successfully with a new row automatically added in the attribute table.

   

How to add a new row for the attribute table fields of an asset

1. Create a New expression and navigate to the Expression name field.

   Civic Platform displays the New Expression fields where you define the criteria.

2. Enter an Expression name. This scenario uses AddRowToTable.

3. Select Asset from the Target portlet list, select Mechanical - Boiler from the Attribute template list, and Attribute Table_1 from the Attribute table list. The attribute table list shows all the attribute tables that associate with the selected attribute template.

   

4. Select the Execute fields list picker to select

   Civic Platform displays the Execute Fields list.

   

5. Expand Additional options and select the onSubmit function.

   Civic Platform loads the onSubmit function in the Execute fields list.

6. Select Insert table row in the Expressions area.

   

7. Assign values to the attribute table fields in the expression.

   1. Select the Field name in the Expressions area to activate it.

   2. In the Variables list, expand the fields under Attribute table.

      

   3. Select the Acres field.

      

8. Set the Property in the Expressions area as “value,” and enter the numeric value in the Calculate Expression field: 220.

9. Select Add expression line to add more lines.

10. Select another field from the Variables list, and set its value.

11. Repeat step 10 until you assign values to all the necessary fields in the attribute table.

12. Select Submit to save the expression.

This section explains how to create the expression criteria that populates read-only fields in the Custom Fields Section of a record type, based on selections made. This expression uses columns and data from a Custom Fields Lookup Table named ZA-1. This expression’s name is Zoning Lookup, because it populates the appropriate references, based on the zones the user selects.

With Expression Builder, you can use the record type of Building/Plan Review/Zoning Analysis, and then identify the Target Portlet of a Custom Field, which is where the user accesses the fields. To build the expression criteria, refer to the steps in the How to prepare a Custom Fields lookup table for creating the expression section.

To see the effect of this expression from a user experience perspective, refer to the How a user completes Custom Fields that populate messages section.

1. User creates a record type of Building > Plan Review > Zoning Analysis > Zoning Analysis.

2. Locate the Custom fields section of the application. An alternate location to modify this information might be in the Zoning analysis portlet for the record type.

   

3. Enter the value

   110

   into the Total Area (in square feet) of the Eligible Front Porch Area field.

4. Select

   R4

   from the Zone list.

   

This scenario uses data from an existing table called Custom Fields Lookup Table called ZA-1.

The ZA-1 table contains the regulation data for zoning that populates when a user completes the Custom Fields section as they create a new record type of Building/Plan Review/Zoning Analysis/Zoning Analysis.

Reviewing this table now makes it easier to follow the scenario. The following screen illustrates the structure, columns, and data in the ZA-1 table.

How to create expression criteria for this custom fields target portlet scenario

1. Create a new expression and navigate to the Expression name field.

   

2. Enter an Expression name. This scenario uses

   BA-Zoning Lookup

   .

3. Select Record Detail in the Target portlet drop down list.

4. In the Custom fields group field, select the group that contains the record type and the fields you want to place an expression in. This scenario uses Custom Fields Group ZA-2, because it requires the record type

   Building/Plan Review/Zoning Analysis/Zoning Analysis

   

5. For these sub-steps, add each of the fields affected within the Target portlet into the Execute fields list. The Execute fields are the fields where users enter data and Civic Platform populates fields with read-only information based on the user’s selections. This scenario affects these four fields:

   ASI::PRINCIPAL USE AND STRUCTURE::Permit Use

   ASI::PRINCIPAL USE AND STRUCTURE::Principal Frontage

   ASI::ZONING ANALYSIS::Front Porch Deduction

   ASI::ZONING ANALYSIS::Zone

   1. Select the Execute Fields picker and expand Custom fields to locate and double-select ASI::PRINCIPAL USE AND STRUCTURE::Permit Use.

      ASI::PRINCIPAL USE AND STRUCTURE::Permit Use. The Permit use field populates with data based on what the user selects from the Zone list. In this scenario, when the user selects R4 the Permit use field populates with specific data from the ZA-1 Custom fields lookup table.

      

   2. Locate the other fields for this expression with the Execute fields picker. Double-click each field label to add it to the Execute field list.

      ASI::PRINCIPAL USE AND STRUCTURE::Principal Frontage. The Principal frontage field populates with data based on what the user selects from the Zone list. In this scenario, when the user selects R4 the Principal frontage field populates with specific data from the ZA-1 Custom fields lookup Table.

      ASI::ZONING ANALYSIS::Front Porch Deduction. This field populates with data based on the user who enters the Total eligible square feet area. See the screenshot below.

      ASI::ZONING ANALYSIS::Zone. This field provides the Zone items that affect what data populates in the Principal frontage, Permit use, and Front porch deduction fields.

      

6. Scroll to the Expressions area. The Expressions area is where you define the lookup criteria for each execute field that calculate or trigger an expression.

   

7. For each field that calculates an expression, select Add expression line to add the field name to the Field name field list.

8. Select the Lookup criteria search button to locate the table name and the column. Define the lookup criteria for each Calculated Expression field for this scenario, select Lookup custom fields table.

   

   When defining expressions, you can use Custom fields lookup Tables. You can add an item to a Custom list using an expression. You can populate a field with data from the Custom list.

   The benefit when using table data is that it eliminates data entry errors that might occur if the permit intake clerk has to manually open a separate document to locate the correct data and then type it into specific fields.

   1. To define the table and identify which columns to populate the data for the ASI::PRINCIPAL USE AND STRUCTURE::Principal Frontage field, follow these two sub-steps:

      Define the Lookup Table Name for the Principal Frontage field. Choose the Custom Fields Lookup Table Name ZA?1 for this scenario.

      Set the Return Column for Principal Frontage. The Return Column is a column in ZA-1 that contains the values that should populate data based on the values the permit intake clerk selects. The Custom Fields Lookup Table columns for the selected Lookup Table display in the drop-down. If a user selects a column from the Variables list portlet, it defaults into this field.

   2. Use the Field Name list and select the field for Principal Frontage.

   3. Set the operator to equal (=).

   4. Select the Value field and then use the variables to locate and add ASI::PRINCIPAL USE AND STRUCTURE::Principal Frontage.

   5. Select OK on the Lookup criteria page.

   6. Repeat the steps to provide a value for the Front porch deduction field with the correct references and correct value.

9. Select Submit in the Lookup criteria form to save the expression.