- 01 May 2025
- 3 Minutes to read
- Print
- DarkLight
Recording Statistics From a Flow
- Updated on 01 May 2025
- 3 Minutes to read
- Print
- DarkLight
Overview
In addition to the set of base statistics that Decisions can automatically record, there are Flow steps available that can be used to record data. This can be used to record specific statistics about an application build in Decisions. For example, the option to record statistics on which users are submitting approval requests vs. using a self-help option. This article covers how to record custom statistics from within a Flow.
Example
In a Flow, select the Toolbox and navigate to System > Advanced > Client Statistics. Here, there are four steps that can be used to record statistics. Each step adds an entry to the client_statistic table within the database.
Record Statistics
The Record Statistics step adds an entry using the input values to the client_statistic table.
Input | Description |
---|---|
Account Id | Account id of the user who took action in Flow |
Action Name | Name of action taken (e.g. "Clicked Approve Button" or "Deleted Record") |
Application Name | Name of the current application. This can be the Flow name or a general/project name. |
Email Address | The email address of the user who took action in Flow |
Section Name | Used to indicate a specific section of the application where action was taken. Depending on the size of the application, there could be some actions that share the same name. This field is used to specifically name where the action occurred. |
sub Section Name | Similar to Section Name, this field provides an additional location to help identify where an action was taken |
Record Statistics With Time And Sessions Step
The Record Statistics with Time and Session step is similar to the Record Statistics step but with the addition of two inputs: Session ID and Time Taken in Seconds.
Input | Description |
---|---|
Account Id | Account id of the user who took action in Flow |
Action Name | Name of action taken (e.g. "Clicked Approve Button" or "Deleted Record") |
Application Name | Name of the current application. This can be the Flow name or a general/project name. |
Email Address | The email address of the user who took action in Flow |
Section Name | Used to indicate a specific section of the application where action was taken. Depending on the size of the application, there could be some actions that share the same name. This field is used to specifically name where the action occurred. |
sub Section Name | Similar to Section Name, this field provides an additional location to help identify where an action was taken |
Session-Id | Records the current session id of this Flow. This ID can be found at FlowData.CurrentEventClientSessionId |
Time Taken in Seconds | Records the time taken for an action to be completed. This time needs to be calculated using steps such as Get Current Date or Get TimeSpan Between, passing the results to this step. |
Record Statistics For Current User Step
This step is similar to the Record Statistics step but automatically sets the values for the Account Id and Email Address to the values of the current user.
Record Statistics For Current User Step | |
---|---|
Action Name | Name of action taken (e.g. "Clicked Approve Button" or "Deleted Record") |
Application Name | Name of the current application. This can be the Flow name or a general/project name. |
Section Name | Used to indicate a specific section of the application where action was taken. Depending on the size of the application, there could be some actions that share the same name. This field is used to specifically name where the action occurred. |
sub Section Name | Similar to Section Name, this field provides an additional location to help identify where an action was taken |
Record Statistics With Time For Current User Step
This step is similar to the Record Statistics For Current User step but includes an input for Time Taken in Seconds.
Record Statistics With Time For Current User Step | |
---|---|
Action Name | Name of action taken (e.g. "Clicked Approve Button" or "Deleted Record") |
Application Name | Name of the current application. This can be the Flow name or a Project name. |
Section Name | Used to indicate a specific section of the application where action was taken. Depending on the size of the application, there could be some actions that share the same name. This field is used to specifically name where the action occurred. |
sub Section Name | Similar to Section Name, this field provides an additional location to help identify where an action was taken |
Time Taken in Seconds | Records the time taken for an action to be completed. This time needs to be calculated using steps such as Get Current Date or Get TimeSpan Between, passing the results to this step. |