Skip to main content

Why don't approval forms include data analytics controls in Yeeflow?

Use a report-backed dashboard for approval analytics, check form-version mappings, and verify the intended records and reader access.

A common question we receive is regarding the absence of Data Analytics controls directly within Approval forms. This article aims to clarify the rationale behind this design choice and introduce an effective alternative solution to meet your data analysis needs.

The Challenge with Data Analytics Controls in Approval Forms

Approval forms in Yeeflow are designed to facilitate streamlined workflow management. Whenever an Approval form is updated and re-published, a new version is generated. Different versions can contain different variables, logic, and structures.

Multiple form versions may be in use at the same time. When analyzing submitted records, check how the form report maps their variables instead of assuming that every version uses the same definitions:

  1. Complex Data Aggregation: Different form versions may use different fields or types. Check that the records being grouped represent comparable data.

  2. Difficulty in Maintaining Accuracy: Changes to a variable’s type or ID, or removal of a variable, can leave a report field blank or produce a missing-variable warning. Review the report mapping and compare historical and new submissions. Handle approval variable changes in form reports.

  3. Keep Approval Tasks Focused: Use a separate dashboard for aggregate analysis while the approval form remains focused on submitting and processing individual requests.

The Alternative Solution: Dashboards with Data Analytics

Use a dedicated dashboard equipped with Data Analytics controls for analysis of submitted approval data. Connect the controls to a form report and configure the scope of the analysis:

  1. Unified Data View: Use a form report as the source for the dashboard’s charts. The report’s selected fields, mappings, and filters determine which data can be analyzed; a dashboard does not automatically reconcile different form versions.

  2. Advanced Analytics Features: With Data Analytics controls on the dashboard, you can use pie charts, summaries, and pivot tables to gain insights into the selected report data.

  3. Separate Analysis Page: Users can explore aggregate results separately from submitting or processing a request. Configure the chart source and filters for the audience and question being answered.

  4. Easy Access and Integration: Provide an application navigation entry or a link to the dashboard. A link gives users an entry point; it does not configure the chart’s data source or grant access.

Implementing the Solution

To implement this solution, follow these steps:

  1. Create a Form Report: Select the source approval form, choose the records to include, and add the variables needed for analysis. For a purchase request example, include department, amount, and approval status. Check the report fields and access settings, then publish the report. Create form reports.

  2. Create a Dashboard and Add Data Analytics Controls: Open the dashboard designer and add a Summary, Pie Chart, Column Chart, or Pivot Table. In the control’s data settings, select the application and the form report as its Data Source. Set the relevant grouping, measure, and data filter; for example, count approved requests by department. Use a form report as a data source.

  3. Provide an Entry Point and Check Access: Add the dashboard to application navigation or provide a page link. Use an intended reader account to check that the page and expected report data can be accessed. Review the report’s permissions where necessary. Edit form report permissions.

  4. Verify the Results and Guide Your Users: Compare the chart with a few known source requests. If the report spans form versions, check both a historical request and a new request. Confirm that the measure counts the intended records: a sublist-based report can contain several rows for one request. Explain the dashboard’s filters and scope to readers.

Data Source setting with PR Report selected in the original English Column Chart configuration screenshot.

The crop shows PR Report selected as the chart’s Data Source in the original form-report help image. Its capture date and product build are unknown.


Use approval forms to submit and process requests, and a report-backed dashboard to analyze them. Recheck report mappings, filters, and access when the source form changes.

Did this answer your question?