An Aggregation Case Study

When the model behavior is changed to aggregate, the model features listed under the model name in the Elements pane will change:

from

Fields, Conditions, and Actions

to

Aggregations, Conditions, Groupings, and Actions.

1. Click Aggregations. The property pane displays a list of fields. We want to aggregate on the Amount field to get a total amount for all opportunity records.

2. Click add Add next to the Amount field to create this new aggregation.

3. Under Aggregations, click the Amount aggregation.

   Note:  The aggregation may be prepended with one of the function options, such as "sum," "avg" or "count."

4. In the Aggregation properties pane, select:

   • Function: SUM
   • Alias name: Nintex Apps auto-populates this field.

Now that we've got an aggregation for the sum of the opportunity amounts, let's do a second one for the average of the opportunity amounts.

Note:  We'll be using the same field (Amount) as used in the previous step, but with a different aggregate function.

1. Click Aggregations to see the list of fields again.

2. Click add Add next to the Amount field to create a second aggregation.

3. In the Elements pane, under Aggregations, click the new Amount aggregation.

4. In the Aggregation properties pane, select:

   • Function: AVG
   • Alias name: Nintex Apps will auto-populate this field.

Now the model knows to aggregate opportunity amounts into totals and into averages. But this use case calls for a grouping to govern how the data will be displayed within Nintex Apps components.

1. Click Groupings:

   • Grouping method: Simple
   • In the Properties pane, search for and check Stage. (This is the field we want to group the opportunities by.) Nintex Apps displays a new grouping under Groupings.

2. Click Save.

Now the page has an aggregate model with a grouping. Time to add a component to the page, to display the data.

Rather than seeing all opportunities created since the team started tracking them, let's limit what comes into the model by a close date using a condition.

1. In the Elements pane, click the name of the Opportunity model.

2. Under the model name, click Conditions.

3. Click add Add to add a condition.

   • In the condition, set:

     • Field: CloseDate

     • Operator: is

     • Value:

       • Content: Single specified value
       • Value: Specific Date

     • State: Dynamic (Default off)

Now that the records can be limited by date, let's also limit whose opportunities are displayed.

1. Click add Add to add a second condition.

   • In the condition, set:

     • Field: OwnerID

     • Operator: is

     • Value:

       • Content: Single specified value
       • Value: Leave blank

     • State: Dynamic (Default off)

1. In the Table component, click Add Feature > Add Table Filter.

2. Click on the new filter and edit:

   • Filter type: Select option
   • Pick options and conditions: Manually
   • Filter label: Close Date
   • Model condition to affect: CloseDate
   • Create None Selected Option: Checked
   • "None Selected" option text: Any Close Date
   • Display as: Dropdown.

3. Click the Sources tab, then click add Add Option Source (Any Close Date - CloseDate).

   • Source type: Manual.

4. On the new option source, click add Add Option three times and then configure the three options:

   • First option:

     • What Condition(s) will this Option affect?: Affect the default condition
     • Label: Closing: This Year
     • Value: THIS_YEAR

   • Second option:

     • What Condition(s) will this Option affect?: Affect the default condition
     • Label: Closing: Last Year
     • Value: LAST_YEAR

   • Third option:

     • What Condition(s) will this Option affect?: Affect the default condition
     • Label: Closing: This Fiscal Year
     • Value: THIS_FISCAL_YEAR

5. Click Save, and click Preview.

Now the table has three closing-date filter options.

This will filter for a specific user.

Add a condition to the user model

First, to see only the users that actually own an opportunity (versus all the users in the org), limit the page's user model with a condition:

1. In the Elements pane, under the User object model, click Conditions.

2. Click add Add Condition and edit the condition:

   • Field: Id

   • Operator: is

   • Value:

     • Content: Result of a subquery
     • Join object: Opportunity
     • Join field: OwnerId

   • State: always on

3. Click Save.

Create the user filter

Now, let's add another filter to the Table component:

1. In the Table, click Add Feature > Add Table Filter.

2. Click on the new filter and edit:

   • Filter type: Select option
   • Pick options and conditions: Manually Select Conditions
   • Field Label: Opportunity Owner
   • Model condition to affect: The "limit opportunity owners" condition created here
   • Create None Selected Option: Checked.
   • "None Selected" option text: Any Owner
   • Display as: Dropdown

We also need to tell the filter who the possible owners are. We do this by adding an option source to the filter:

1. In the Properties pane, click the Sources tab, then click add Add Option Source on Opportunity Owner.

   • Source type: Rows in a model
   • Merge source: The user model.
   • Option label template: Owner: {{{Name}}}
   • Which Conditions will this Source's Options affect: Just the default condition
   • Value to Inject into Default Condition: {{id}}

Note:  This is the field (from the user model) that will be injected into the owner condition (on the opportunity model), enabling end users to see owner names in the filter.

2. Click Save, and click Preview.

1. In the Table component, click Add Feature > Add Table Filter.

2. Click on the new filter and edit:

   • Filter type: Select option

   • Pick options and conditions: Automatically

   • Filter field: Industry

     Note:  Click the arrow next to Account ID. This navigates to the Account fields, where the Industry field is located.

   • Show Label above Filter: Yes, use Field's label

   • "None Selected" option text: All Industries.

   • Display as: Dropdown

3. Click Save, and click Preview.