Note: The Nintex Analytics Beginning Beacon action is available only if you have installed the latest Nintex for SharePoint 2013 version.
Logs the start of a process stage to Nintex Analytics.
For this action, you need to name the stage you are highlighting in the Stage Name field (required). You can also include an expected duration for the stage to complete. The Expected Duration property measures how long the process takes to complete against what you expect. For example, you may want this stage of the workflow to complete within 30 minutes, and test that number with the process intelligence lens report.
Note: To accurately capture the start and end of the process you are interested in, use both the Beginning Beacon and the Ending Beacon workflow actions.
The following two beacons are used to identify the start and end of a process stage. These two actions must be used together.
- Nintex Analytics - Ending Beacon
- Nintex Analytics - Beginning Beacon
To use the workflow action:
Locate the action in Workflow Actions Toolbox (located on the left hand-side);
Select the action, drag it onto the design canvas and drop it onto a design pearl.
Alternatively
Configuration for this action
The following fields are available in the configurationsettings dialog boxfor the action.
Stage name: (Required) Specify a name for the start of a new process stage within your workflow. Make sure to specify the same process stage name in the Nintex Analytics - Ending Beacon action.
Expected duration: Specify the expected duration in seconds for the stage to run. This property measures how long the process takes to complete against the expected results. For example, you may want this stage of the process to complete within 30 seconds, and test that number with the process intelligence lens report.
Example: 30
Beacons: Define one or more beacons to emit data from the workflow for reports. Examples include variables and list items.
Error handling: Configure settings as appropriate. With error handling you can capture errors that occur during the execution of the call to Nintex Analytics and add additional actions to handle any exceptions.