Using the Calculate Summary Action in Infowise Ultimate Forms
In many business processes, you need to aggregate data across multiple list items. It could be summing values, counting related records, finding minimums/maximums, or even enforcing rules based on aggregated data. The Calculate Summary action in Ultimate Forms gives you this power. It enables workflows to compute summary statistics across any list in the site collection and then either update the current item with that summary, or enforce constraints by raising errors when conditions are not met.
How the Calculate Summary Action Works
Here are the key parameters and how the action is configured:
| Configuration Item | What It Does |
|---|---|
| Site | Pick a site within the current site collection. You can also use run-time values for dynamic behavior and/or specifying a different site collection. |
| List | The list from which items are pulled for summarization. This can be static or dynamic (based on column values). |
| Affected Items | Define which items to include. You must set at least one filter: could be by column values, IDs, date ranges, etc. This allows targeting of specific subsets (e.g. only “approved” items or items in a certain timeframe). |
| Column to Summarize | Choose the numeric or date column whose values you want to aggregate. If the column isn't numeric, count operations are available. |
| Operator / Summary Type | The type of summary: sum, count, average, minimum, maximum. If the result is used to raise an error, additional types like “All” or “Any” may be used. |
| Result Type | Two main options: Update a column in the current item with the summary value, or Raise an error if the summary does not meet a specified condition. |
| Column to Update | If you're updating, select which column in the current item gets set to the summary result. The current item is the one triggering the action. |
| Conditions / Errors | When raising errors, you configure condition logic (comparisons, threshold values) and an error message. If used synchronously, the action can block saving the item until conditions are met. |
Benefits of Calculate Summary
-
Aggregated Insight: Provides totals, counts, averages without having to visually scan multiple items. Ideal for parent‐child scenarios.
-
Enforced Business Logic: Use summaries to prevent undesirable states—like overbooking, overspending, or completing a record before required sub-items exist.
-
Cross‐List Capability: The list you summarize items from does not need to be the same as the current one; you can reference lists in any site or via run-time values.
-
Error Handling & Validation: Instead of silent mismatches, you can enforce constraints by erroring out, ensuring data integrity.
Real-World Scenarios & Examples
Here are several ways organizations can use the Calculate Summary action in practice:
-
Room Reservation / Scheduling
Example: Prevent a user from creating a reservation if there is already an existing reservation for the same timeslot. The summary action aggregates reservations for a given date/time and raises an error if the count is > 0. -
Expense Budget Management
For a department submitting expenses, you might sum all submitted or approved expenses this month, compare against budget, and prevent new submissions if the sum would exceed the budget. -
Order Items / Line Totals
In an order management setup, each order has line items; you use Calculate Summary to sum the line items' value and then store it in the parent (order) record. If the sum is below a minimum or above a threshold, trigger an alert or block. -
Task / Subtask Completion Check
Only allow a project to be marked “Completed” if all associated tasks are finished. Use summary to count tasks with status ≠ Completed; if count > 0, raise error on project item so it cannot be completed prematurely. -
Quality Control / Compliance
Consider a scenario where certain inspections are required. Summarize past inspections from related items and prevent closure of a compliance record until required number of inspections or checks are passed.
Best Practices & Tips
To get the most from the Calculate Summary action, consider these recommendations:
-
Careful Filtering: Use precise filters so summary includes exactly those items relevant. Overbroad selection can lead to inaccurate or misleading results.
-
Optimize for Performance: Large lists or many filtered items can slow actions. If possible, use indexed columns, limit item scope, or schedule summary actions at low-load times.
-
Meaningful Error Messages: When raising errors, be explicit so users understand what needs correction (“Cannot complete until 2 outstanding tasks remain”, etc.).
-
Use Synchronous Mode When Needed: If you need to block save operations until summary conditions are met, configure the action synchronously. But be aware this may impact save performance.
-
Document Setup: Maintain clear naming and documentation of actions so admins understand which summary actions affect which forms and lists.
How to Set It Up: Step-by-Step
Here’s how you might configure a Calculate Summary action in Ultimate Forms:
-
Open the list concerned in SharePoint and click on Design → Actions.
-
Create a new action, selecting Calculate Summary as the action type.
-
Set the trigger (when run): on item creation, modification, or possibly manually via a button, depending on your need.
-
Choose the site and list you want to summarize items from. For example, if you are summarizing other reservations in the same site, select that list.
-
Define filter logic to pick which items matter (e.g. same date, same room id, status = “Active”) so the summary doesn’t include irrelevant items.
-
Select the column in the source list whose values you want to aggregate (numeric columns for sum/average, date for min/max, etc.).
-
Choose whether to Update a column in current item, or Raise error. If updating, specify the destination column. If raising error, set condition (operator, threshold) and error message.
-
Save and test. Create or edit items to verify the summary works. Check that error conditions block when needed; also that the updated column properly reflects the summary result.
Comparison with Associated Items Summary vs Calculate Summary
While both relate to summaries, there are distinctions:
-
Associated Items Summary column is tied to child items of an Associated Items column; its summary updates automatically based on associated child records.
-
Calculate Summary Action, in contrast, is more flexible in list choice, filter criteria, and can be used in actions (i.e. triggered by events or manual or timer) or raise errors proactively. It works outside just “associated items” relationships.
Potential Challenges & Mitigations
-
Big datasets: If the list from which items are being summarized is large, performance may degrade. Mitigation: limit filters, use indexing.
-
Permissions issues: If the action tries to read or update lists/items the user lacks access to, errors may occur. Ensure appropriate permissions are in place or use Impersonation.
- Understanding thresholds: Users may need training so they understand what summary conditions mean (e.g. “sum of related amounts” etc.)
Summary & Why It Matters
The Calculate Summary action in Infowise Ultimate Forms adds powerful data aggregation and conditional enforcement to workflows, without writing code. It’s a bridge between raw list data and business intelligence, enabling automated checks, error prevention, and enriched parent-item displays.
Whether for budgeting, compliance, scheduling, or quality control, Calculate Summary helps teams enforce rules, make decisions, and maintain data integrity. If you're planning your workflows, this action often becomes a key building block—providing insight and control across lists.
