Trend Records

Introduction

Trend Records collect a record of visitors that have connected to the TrustX system to improve fraud detection and provide trending information about the email, phone-number, document, and IP address typically used by the individual visitor when accessing the system. This is an important factor in fraud detection to measure the actions related to trend patterns. For example, if there are multiple process instances for the same IP address or with the same Visitor ID.

Alongside Device Integrity Signals and Watchlists, Trend Records provide users with a fraud detection and prevention system that focuses on understanding trends and how to prevent fraud when fraud is found.

Trend Records Page Overview

The Trends Records page is accessible from the Backoffice.

Log in to the Backoffice with a tenant that has admin or audit access.
Find the Trend Records menu item on the left-side navigation bar.

Records Overview

The Records Overview section provides a visual representation of visit distribution over time by identifier type.

Trend Records

The Trend Records table provides an comprehensive list of recorded visits. By default, the table is sorted by 'Date Recorded' with the most recent recorded visit appearing at the top of the table.

Each column contains the following information:

Field	Description
Value	The value recorded during the Process Instance. Possible values include a document number, email address, IPv4 address, and phone number.
Type	The record type that was recorded. Possible values include Document Number, Email, IPv4 Address, and Phone Number.
Process Definition	The name of the Process Definition used to capture the trend record.
Process Instance	The Process Instance ID.
Date Recorded	The date that the trend record was recorded.
Expires After	The date in which the trend record will expire. A trend record will be stored for 90 days following the date it is recorded.

Add and Check a Trend Record

The Process Designer includes several activities that can be used to record data as trend records in TrustX. This includes the following activities:

'Record IPv4 Address'
'Add IPv4 Address Trend Record'
'Check IPv4 Address Trend Records'
'Record & Assess Device Integrity Signals'
'Add Visitor ID Trend Record'
'Check Visitor ID Trend Records'
'Add Email Trend Record'
'Check Email Trend Records'
'Add Phone Number Trend Record'
'Check Phone Number Trend Records'
'Add Document Number Trend Record'
'Check Document Number Trend Records'

This section will describe how to configure Process Definitions to retrieve the necessary data and add them to trend records in TrustX.

Creating a Process Definition

To create a Process Definition from the Backoffice application, follow the steps outlined below.

Log in to the Backoffice and find the Process Definitions page in the left vertical navigation bar.
From the Process Definitions page, select the 'New Process Definition' button at the top-right of the page.
A popup modal will appear where various choices to get started can be made. For this guide, select to create Process Definition from scratch using the 'New Process Definition' button.
Set the name of the Process Definition. This is a mandatory field required for creating a new Process Definition.
To get started, add a 'Create Start Event' and and an 'Create End Event' to the Process Designer and join them using Global connect tool.

Optional: Create a Custom Data Form

Phone number and email trend records can be collected using various methods in TrustX. Some methods of data capture include:

This example will demonstrate an implementation using a Custom Data Form that can be used to request a phone number and email from the user.

Log in to the Backoffice and navigate to Integration Hub > Custom Forms.
On the Custom Forms page, click the 'New Custom Form' button at the top-right of the screen.

The Custom Form Builder

A Custom Form can be created using the form Visual Builder or the JSON Form Builder. For this example, the following JSON will be used:

JSON
    
xxxxxxxxxx
 
{    "title": {        "values": {            "en": "Personal information"        },        "isValid": true,        "type": "title"    },    "components": [        {            "type": "email",            "isValid": true,            "readOnly": false,            "id": "email",            "label": {                "values": {                    "en": "Email"                }            },            "default": "",            "transient": false,            "validate": {                "required": false,                "pattern": "^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+.[a-zA-Z]{2,}$",                "missingMessage": {                    "values": {                        "en": ""                    }                },                "invalidMessage": {                    "values": {                        "en": ""                    }                }            },            "index": 0        },        {            "type": "phone",            "isValid": true,            "readOnly": false,            "id": "phone",            "label": {                "values": {                    "en": "Phone number"                }            },            "default": "",            "defaultCountry": "",            "validate": {                "required": false,                "missingMessage": {                    "values": {                        "en": ""                    }                },                "invalidMessage": {                    "values": {                        "en": ""                    }                }            },            "index": 1        }    ]}
Copy

This form includes an 'Email' and 'Phone' form element, which can be found in the Visual Builder under the Inputs category.

Once the form has been finalized, click the orange 'Save & Deploy' button to complete the form.

IPv4 Address Trend Record

The 'Record IPv4 Address' activity can be used to record the IPv4 address of the user completing the Process Instance. After the IPv4 address is recorded, it can be added to the trend records using the 'Add IPv4 Address Trend Record'. Finally, a recorded IPv4 Address can be checked to see whether it appears as a trend record using the 'Check IPv4 Address Trend Records'.

After the 'Start Event', add a 'Record IPv4 Address' activity and connect using the 'Global connect tool'.

After the 'Record IPv4' Address activity, add an 'Add IPv4 Address Trend Record' activity to the Process Designer and connect it using the 'Global connect tool'.

The activity includes the following input parameters:

Input Parameters

Parameter	Description	Type	Required	Default
Expires After Days	The number of days after which the trend record will expire. Supports a maximum of 90 days and a minimum of 1 day.	Integer	Yes	14
IPv4 Address	IPv4 address to record (max 18 chars, e.g., "192.168.100.100"). If not provided, IPv4 Address Key must be provided.	String
IPv4 Address Key	The key used to identify the IPv4 address from `_signals.ipv4s`. If provided, the IPv4 address can be resolved from the signal.	String	No	ipv4Address1
Trend Group	Optional trend group for grouping trends by business context (alphanumeric and underscore; max 32 chars),	String

The activity also includes an "Invalid Trend Record format" error boundary event that is triggered when the input parameters are not configured correctly.
After the 'Add IPv4 Address Trend Record' activity, add a 'Check IPv4 Address Trend Records'. This activity will query historical IPv4 address trend data for a specified time period and checks if the trend count exceeds a configurable threshold. This activity records a check result indicating whether the threshold was exceeded.

This activity includes the following input parameters:

Input Parameters

Parameter	Description	Type	Required	Default
Check Key	The key under which the check result will be stored in the checks object.	String	Yes	ipv4Address1TrendCheck
IPv4 Address	IPv4 address to check (max 18 chars, e.g., "192.168.100.100"). If not provided, IPv4 Address Key must be provided.	String	No
IPv4 Address Key	The key used to identify the IPv4 address from `_signals.ipv4s`. If provided, the IPv4 address can be resolved from the signal.	String	No
Query Period	ISO 8601 period for the query window. Minimum 1 second (PT1S), maximum 14 days (P14D). Examples: PT1S, PT1H, P1D, P14D.	String	Yes	P14D
Threshold Count	Maximum number of trend occurrences allowed in the time period. If the count exceeds this threshold, the check will FAIL.	Integer	Yes
Trend Group	Optional trend group for grouping trends by business context (alphanumeric and underscore; max 32 chars),	String	No

Additionally, the activity features two error boundary events:

Error Event	Description
Invalid Trend Record format	Error event is triggered when the provided trend record is in an invalid format.
Exceeded the threshold count	Triggered when the value entered in the 'threshold count' input parameter is exceeded.

Document Number Trend Record

For this section, a document number will be recorded using a standard document capture flow. The recorded document number will be added as a trend record using the 'Add Document Number Trend Record' activity.

The example below demonstrates a simple document capture flow that will be used to capture the document and utilizes the 'ID Document Processor' to extract the document number.

Example Document Capture flow

A full document capture example Process Definition can be downloaded from the Github link below.

Download Example on Github

The steps below demonstrate how to add a document number trend record using the Process Definition above.

After the 'Acceptable Document Type' activity, add an 'Add Document Number Trend Record' activity to the Process Designer and connect them using the 'Global connect tool'.

The 'Add Document Number Trend Record' activity includes the following input parameters:

Input Parameters

Parameter	Description	Type	Required	Default
Expires After Days	The number of days after which the trend record will expire. Supports a maximum of 90 days and a minimum of 1 day.	Integer	Yes	14
Document Number	Document number to record (max 100 chars). If not provided, 'Document Number' must be provided.	String	No
Document Key	The key used to identify the document number from `_idDocs`. If provided, document number and document type can be resolved from the document.	String	No	ipv4Address1
Trend Group	Optional trend group for grouping trends by business context (alphanumeric and underscore; max 32 chars),	String	No

By default, the document number will be filled using the doc1 Document Key input parameter. It is also possible to populate the document number using variable substitution:
The Check Document Number Trend Records activity can be used to query historical document number trend data for a specified time period and checks if the trend count exceeds a configurable threshold. This activity records a check result indicating whether the threshold was exceeded.

The 'Check Document Number Trend Record' activity includes the following input parameter:

Input Parameters

Parameter	Description	Type	Required	Default
Check Key	The key under which the check result will be stored in the checks object.	String	Yes	documentNumber1TrendCheck
Document Number	Document number to check (max 100 chars). If not provided, Document Key must be provided.	String	No
Document Number Key	The key used to identify the document number from `_idDocs`. If provided, the document number and document type can be resolved from the document.	String	No
Query Period	ISO 8601 period for the query window. Minimum 1 second (PT1S), maximum 14 days (P14D). Examples: PT1S, PT1H, P1D, P14D.	String	Yes	P14D
Threshold Count	Maximum number of trend occurrences allowed in the time period. If the count exceeds this threshold, the check will FAIL.	Integer	Yes
Trend Group	Optional trend group for grouping trends by business context (alphanumeric and underscore; max 32 chars),	String	No

This activity also features an 'Exceed the threshold count' error boundary event. This is triggered when the value entered in the 'threshold count' input parameter is exceeded.

Phone Number Trend Record

A phone number can be recorded as a trend entry in the trends system. The 'Add Phone Number Trend Record' activity creates a trend data point for a specific phone number, allowing the system to track usage patterns and detect anomalies over time. In this iteration, the phone number is direct BPMN input only; a future iteration will support resolution from a user in the identity store.

For this example, a phone number will be collected using a Custom Form. See Optional: Create a Custom Data Form above for more information on creating Custom Forms.

Create a new Process Definition or modify an existing Process Definition in the Backoffice.

After the 'Start' event, add a 'Custom Data Form' activity and connect them using the 'Global connect tool'

The 'Custom Data Form' activity includes the following configurable input parameters:

Input Parameters

Parameter	Description	Type	Default
Data form name	A drop-down list of all available custom forms created in TrustX. The chosen form will be displayed to the end user in the ID&V flow.	String
Data form version	Determines which version of the selected custom form will be displayed.	Integer	1
Dynamic data form name	The name of the dynamic data form.	String
Edit Mode	If set to true, the form will display the retry and continue buttons and any editable fields. If set to false, only the continue button will be shown. If "Readonly" and "edit" modes are enabled, "Readonly" mode will override the "edit" mode settings.	Boolean	${false}
Form data key	When multiple Custom Data Forms are used in one Process Definition, the form data key will be used as a unique identifier to distinguish Custom Form activities from each other.	String	form1
Hide buttons	When set to true, all form buttons will be hidden	BOOLEAN	${false}
List of Screens	The list of screens to be presented to the user during the capture process. Possible values include: instructions, capture, and preview.	LIST_STRING	[ custom-data-form ]
Max Attempts	The maximum number of attempts to retake the form before an error is thrown.	Integer	${3}
Readonly	This field determines whether the displayed form is readonly.	Boolean	${false}
Starting Component ID	The name of the capture step to be sent to the UI.	String	custom-data-form
UI Component ID	The name of the screen used in the capture UI.	String	custom-data-form

Set the 'Data form name' and 'Data form version' input parameters to a form that will accept a phone number as input.
After the 'Custom Data Form', add an 'Add Phone Number Trend Record' activity.

The 'Add Phone Number Trend Record' activity supports the following input parameters:

Input Parameters

Parameter	Description	Type	Required	Default
Expires After Days	The number of days after which the trend record will expire. Supports a maximum of 90 days and a minimum of 1 day.	Integer	Yes	14
Normalize	Whether to normalize the phone number before recording.	Boolean	No	${true}
Phone Number	Phone number to record (max 24 chars).	String	Yes
Phone Number Region	Optional region code for phone number normalization. A maximum of 2 characters is supported.	String	No
Trend Group	Optional trend group for grouping trends by business context (alphanumeric and underscore; max 32 chars),	String	No

For the 'Phone Number' input parameter, enter the following to perform variable substitution with data captured from the Custom Data Form: ${_customFormData["form1"]["currentCapture"]["customDataFormDataMap"]["phone"]} .
1. _customFormData - Accesses the _customFormData class.
2. ["form1"]- Represents the form ID defined in the input parameters of the 'Custom Data Form' activity.
3. ["currentCapture"] - Retrieves data from the current active Process Instance.
4. ["customDataFormDataMap"]- Retrieves a map of Custom Form results.
5. ["phone"]- Retrieves the phone number contained within the Custom Form map.

The 'Check Phone Number Trend' activity queries historical phone number trend data for a specified time period and checks if the trend count exceeds a configurable threshold. This activity records a check result indicating whether the threshold was exceeded.

The 'Check Phone Number Trend Records' activity includes the following input parameters:

Input Parameters

Parameter	Description	Type	Required	Default
Check Key	The key under which the check result will be stored in the checks object.	String	Yes	documentNumber1TrendCheck
Normalize	Whether to normalize the phone number before querying.	Boolean	No	${true}
Phone Number	Phone number to check (max 24 chars).	String	No
Phone Number Region	Optional region code for phone number normalization (max 2 chars).	String	No
Query Period	ISO 8601 period for the query window. Minimum 1 second (PT1S), maximum 14 days (P14D). Examples: PT1S, PT1H, P1D, P14D.	String	Yes	P14D
Threshold Count	Maximum number of trend occurrences allowed in the time period. If the count exceeds this threshold, the check will FAIL.	Integer	Yes
Trend Group	Optional trend group for grouping trends by business context (alphanumeric and underscore; max 32 chars),	String	No

In the input parameters, enter a phone number or use variable substitution to identify the number. For this example, the same expression from step 7, ${_customFormData["form1"]["currentCapture"]["customDataFormDataMap"]["phone"]} , can be used.
Additionally, the activity features two error boundary events:

Error Event	Description
Invalid Trend Record format	Error event is triggered when the provided trend record is in an invalid format.
Exceeded the threshold count	Triggered when the value entered in the 'threshold count' input parameter is exceeded.

Email Trend Record

Adding and checking an email trend record is similar to the process outlined in the Phone Number Trend Record section above.

For this example, an email will be collected using a Custom Form. See Optional: Create a Custom Data Form above for more information on creating Custom Forms.

Create a new Process Definition or modify an existing Process Definition in the Backoffice.

After the 'Start' event, add a 'Custom Data Form' activity and connect them using the 'Global connect tool'

The 'Custom Data Form' activity includes the following configurable input parameters:

Input Parameters

Parameter	Description	Type	Default
Data form name	A drop-down list of all available custom forms created in TrustX. The chosen form will be displayed to the end user in the ID&V flow.	String
Data form version	Determines which version of the selected custom form will be displayed.	Integer	1
Dynamic data form name	The name of the dynamic data form.	String
Edit Mode	If set to true, the form will display the retry and continue buttons and any editable fields. If set to false, only the continue button will be shown. If "Readonly" and "edit" modes are enabled, "Readonly" mode will override the "edit" mode settings.	Boolean	${false}
Form data key	When multiple Custom Data Forms are used in one Process Definition, the form data key will be used as a unique identifier to distinguish Custom Form activities from each other.	String	form1
Hide buttons	When set to true, all form buttons will be hidden	BOOLEAN	${false}
List of Screens	The list of screens to be presented to the user during the capture process. Possible values include: instructions, capture, and preview.	LIST_STRING	[ custom-data-form ]
Max Attempts	The maximum number of attempts to retake the form before an error is thrown.	Integer	${3}
Readonly	This field determines whether the displayed form is readonly.	Boolean	${false}
Starting Component ID	The name of the capture step to be sent to the UI.	String	custom-data-form
UI Component ID	The name of the screen used in the capture UI.	String	custom-data-form

Set the 'Data form name' and 'Data form version' input parameters to a form that will accept an email as input.
After the 'Custom Data Form' activity, add an 'Add Email Trend Record' activity and connect them using the 'Global connect tool'.

The 'Add Email Trend Record' activity includes the following input parameters:

Input Parameters

Parameter	Description	Type	Required	Default
E-mail Address	Email address to record (max 254 chars, valid email format).	String	Yes
Expires After Days	The number of days after which the trend record will expire. Supports a maximum of 90 days and a minimum of 1 day.	Integer	Yes	14
Normalize	Whether to normalize the phone number before recording.	Boolean	No	${true}
Trend Group	Optional trend group for grouping trends by business context (alphanumeric and underscore; max 32 chars),	String	No

For the 'E-mail Address' input parameter, enter the following to perform variable substitution with data captured from the Custom Data Form: $${_customFormData["form1"]["currentCapture"]["customDataFormDataMap"]["email"]} .
1. _customFormData - Accesses the _customFormData class.
2. ["form1"]- Represents the form ID defined in the input parameters of the 'Custom Data Form' activity.
3. ["currentCapture"] - Retrieves data from the current active Process Instance.
4. ["customDataFormDataMap"]- Retrieves a map of Custom Form results.
5. ["email"]- Retrieves the email address contained within the Custom Form map.

Add the 'Check Email Trend Records' activity to the Process Designer after the 'Add Email Trend Record' activity. The 'Check Email Trend Records' activity queries historical email trend data for a specified time period and checks if the trend count exceeds a configurable threshold. This activity records a check result indicating whether the threshold was exceeded. Email is direct Process Designer input only in this release.

The activity includes the following input parameters:

Input Parameters

Parameter	Description	Type	Required	Default
Check Key	The key under which the check result will be stored in the checks object	String	Yes	email1TrendCheck
Email Address	Email address to check (max 254 chars, valid email format). Direct input only.	String	Yes
Normalize	Whether to normalize the phone number before querying.	Boolean	No	${true}
Query Period	ISO 8601 period for the query window. Minimum 1 second (PT1S), maximum 14 days (P14D). Examples: PT1S, PT1H, P1D, P14D.	String	Yes	P14D
Threshold Count	Maximum number of trend occurrences allowed in the time period. If the count exceeds this threshold, the check will FAIL.	Integer	Yes
Trend Group	Optional trend group for grouping trends by business context (alphanumeric and underscore; max 32 chars),	String	No

In the input parameters, enter an email or use variable substitution to identify the email address. For this example, the same expression from step 7, ${_customFormData["form1"]["currentCapture"]["customDataFormDataMap"]["email"]} , can be used.
Additionally, the activity features two error boundary events:

Error Event	Description
Invalid Trend Record format	Error event is triggered when the provided trend record is in an invalid format.
Exceeded the threshold count	Triggered when the value entered in the 'threshold count' input parameter is exceeded.

Visitor ID Trend Record

The Visitor ID associated with a Device Signal Record can be added as a trend record, supporting a number of use cases including:

Recording Device Integrity Signals for trend analysis.
Building historical patterns for multi-accounting detection.
Tracking Visitor ID frequency across time periods.
Supporting device-based fraud detection algorithms.

Device Integrity Signals collect rich, high-fidelity telemetry from every web and native session. For more information, see the Device Integrity Signals documentation.

The 'Record & Assess Device Integrity Signals' activity can be used to record a Visitor ID that will be used to add a new trend record.

In the Process Designer, add a 'Record & Assess Device Integrity Signals' activity and connect it to the 'Start' event using 'Global connect tool'.

The Record & Assess Device Integrity Signals' activity features the following input parameters:

Input Parameters

Parameter	Description	Type	Default
Browser bot Detection Check Enabled	Check that determines whether the browser is using an automated bot.	Boolean	${true}
Browser Developer Tools Detection Check Enabled	Check that determines whether the browser is using developer tools.	Boolean	${true}
Browser Incognito Detection Enabled	Check that determines whether the browser is using an incognito mode.	Boolean	${true}
Browser Privacy Focussed Detection Check Enabled	Check that determines whether the web browser is a privacy focussed browser.	Boolean	${true}
Browser Tamper Detection Check Enabled	Check that determines whether intentional changes to the browser settings, configuration or extension have been made.	Boolean	${true}
Browser Virtual Machine Detection Check Enabled	Check that determines whether the browser is running on a virtual machine.	Boolean	${true}
Browser VPN Detection Check Enabled	Check that determines whether the browser is runing on a VPN.	Boolean	${true}
Circuit Breaker Failure Rate Threshold Percentage	Percentage of calls that must fail before the circuit is broken. Minimum value is 1. Maximum value is 100.	Integer	${10}
Circuit Breaker Window Size	Time in seconds over which the circuit breaker is calculated. Default value is 5 minutes. Minimum value is 5 minutes. Maximum value is 600 minutes.	Integer	${300}
Cloned App Detection Check Enabled	Determines whether the device is running a cloned application to complete the process.	Boolean	${true}
Device Integrity Signal Key	The identifier of the Device Integrity Signal.	Boolean	${true}
Emulator Detection Check Enabled	Check whether the Process Instance is performed on an emulator.	Boolean	${true}
Enable Fail Open Circuit Breaker	A configuration that enables a circuit breaker if there is a flood of failures to decrypt the Device Integrity Signal payload.	Boolean	${true}
Factory reset Detection Check Enabled	Check whether the device has been factory reset.	Boolean	${true}
Factory reset Detection Check Enabled	Check whether the device has been factory reset.	Boolean	${true}
Frida Detection Check Enabled	Check that determines the use of the Frida dynamic instrumentation toolkit.	Boolean	${true}
Jail Broken Detection Check Enabled	Check that determines whether the device has been jail broken.	Boolean	${true}
MitM Attack Detection Check Enabled	Check to determine whether a Man in the Middle (MitM) attack has been detected. This check is only avaivalable for Android devices.	Boolean	${true}
Network Proxy Detection Check Enabled	Determines whether the user's internet traffic is being routed through a network proxy.	Boolean	${true}
Network Tor Detection Check Enabled	Determines whether the user's internet traffic is being routed through the Tor network.	Boolean	${true}
Replay Time (seconds)	The time in seconds that Client Data is allowed to be generated and processed. Minimum value is 30s. Maximum value is 990s.	Integer	${60}
Root Apps Detection Check Enabled	Determines whether the application has been rooted (given superuser privileges).	Boolean	${true}
Starting Component ID	The name of the step to be sent to the UI.	String	signals
Tampering Detection Check Enabled	Determines whether the application has been tampered with.	Boolean	${true}
Test Mode	When enabled, replay checks are not performed and the user is able to submit a JSON objct instead of the sealed response from the Device Integrity Signals service.	Boolean	${true}
UI Component ID	The name of the screen used in the capture UI.	String	signals

After this activity, add an 'Add Visitor ID Trend Record' activity. This activity will add the specified Visitor ID as a trend record.

The activity feature the following input parameters:

Input Parameters

Parameter	Description	Type	Required	Default
Expires After Days	The number of days after which the trend record will expire. Supports a maximum of 90 days and a minimum of 1 day.	Integer	Yes	14
Device Signal Key	The key to look up Visitor ID from `_signals.deviceIntegritySignals` (with configured device-signals-version). If provided, the Visitor ID can be resolved from the signal.	String	No	deviceIntegritySignal1
Visitor ID	Unique device/browser fingerprint identifier (max 100 chars). If not provided, the Device Signal Key must be provided.	String	Yes
Trend Group	Optional trend group for grouping trends by business context (alphanumeric and underscore; max 32 chars),	String	No

In this example, the Visitor ID will be identified and populated using the 'Device Signal Key' set in the input parameters of the 'Record & Assess Device Integrity Signal' activity.
After the 'Add Visitor ID Trend Record', add a 'Check Visitor ID Trend Records' activity. This activity queries historical visitor ID trend data for a specified time period and checks if the trend count exceeds a configurable threshold. This activity records a check result indicating whether the threshold was exceeded.

This activity features the following input parameters:

Input Parameters

Parameter	Description	Type	Required	Default
Check Key	The key under which the check result will be stored in the checks object.	String	Yes	visitorId1TrendCheck
Device Integrity Signal Key	The key to look up Visitor ID from `_signals.deviceIntegritySignals` (with configured device-signals-version). If provided, the Visitor ID can be resolved from the signal.	String	No	deviceIntegritySignal1
Query Period	ISO 8601 period for the query window. Minimum 1 second (PT1S), maximum 14 days (P14D). Examples: PT1S, PT1H, P1D, P14D.	String	Yes	P14D
Threshold Count	Maximum number of trend occurrences allowed in the time period. If the count exceeds this threshold, the check will FAIL.	Integer	Yes	1
Trend Group	Optional trend group for grouping trends by business context (alphanumeric and underscore; max 32 chars),	String	No
Visitor ID	Unique device/browser fingerprint identifier (max 100 chars). If not provided, the Device Signal Key must be provided.	String	No

This activity also features an 'Exceed the threshold count' error boundary event. This is triggered when the value entered in the 'threshold count' input parameter is exceeded.
In the input parameters, enter a Visitor ID or use the 'Device Integrity Signal Key' input parameter to identify the Visitor ID. In the example above, the 'Device Integrity Signal Key' matches the same parameter set in the 'Record & Assess Device Integrity Signal' activity.

Test and View Results

Results of trend checks can be viewed from the Process Instance page in the Backoffice application.

Navigate to the 'Process Instance' page and search for the Process Instance using the provided search options.
From the list of search results, select a Process Instance where trend checks have been performed.
Under the 'Checks' section of the individual Process Instance, find the 'Trends' dropdown menu.

Further trend history, including historical analysis and associated Process Instances, can be viewed from the 'Trend History' page. For more information, see the Trend History guide.