Query Ticket activity

Configure the Query Ticket activity

Prerequisites

AgilePoint NX OnDemand (public cloud), or AgilePoint NX PrivateCloud or AgilePoint NX OnPremises v8.0 Software Update 2 or higher.

Good to Know

To send an email notification, click Advanced > Email Notifications .
For more information, refer to Email Notifications screen (Process Activities).
In most text fields, you can use process data variables as an alternative to literal data values.
You can configure whether this activity waits for other activities before it runs.
For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?
This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

How to Start

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, open the HubSpot tab.
On the HubSpot tab, drag the Query Ticket activity onto your process.

General Configuration

Specifies the basic settings for the Query Ticket activity.

Good to Know

Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field Name	Definition
Display Name	Description: Specifies the activity name that shows in your process. Allowed Values: One line of text (a string). Accepted: Letters Numbers Spaces Default Value: None Accepts Variables: No Example: This is a common configuration field that is used in many examples. Refer to: Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.
Description	Description: Specifies an optional text description for your activity. Allowed Values: More than one line of text. Default Value: None Accepts Variables: No

Field Name

Definition

Display Name

Description:

Specifies the activity name that shows in your process.

Allowed Values:

One line of text (a string).

Accepted:

Letters
Numbers
Spaces

Default Value:

None

Accepts Variables:

No

Example:

This is a common configuration field that is used in many examples. Refer to:

Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Description:: Specifies an optional text description for your activity.
Allowed Values:: More than one line of text.
Default Value:: None
Accepts Variables:: No

Query Ticket Configuration

Specifies the information about the ticket to retrieve from HubSpot.

Fields

Field Name	Definition
HubSpot	Description: Specifies the access token that connects to your HubSpot service. Allowed Values: A list of access tokens configured for your environment. Default Value: None
Create	Opens this Screen: Access Token for HubSpot Function of this Screen: Configure an access token to connect to HubSpot.
By Ticket ID / Filter Condition	Description: Specifies whether to retrieve information about one or more tickets with a ticket ID or a SQL WHERE clause. Allowed Values: Ticket ID - Retrieves information for a ticket with a ticket ID. Filter Condition - Retrieves information about one or more tickets with a SQL WHERE clause. You can configure the filter condition on the Query Ticket Configuration > Where tab > Create Conditions screen. Default Value: Ticket ID Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Ticket ID	Description: Specifies the ID of the ticket whose information to retrieve. The ticket ID comes from HubSpot. Allowed Values: A ticket ID from HubSpot. Default Value: None Accepts Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Map Response To App Schema	Description: Maps information about the ticket from the HubSpot data model to your process schema. Allowed Values: Click the Schema Mapping button to open the Schema Mapper screen. Use this screen to connect the request to the data model for your process. Default Value: None Example: Refer to: (Example) Schema Mapper

Query Ticket Configuration > Where tab

Shows the WHERE clause for your query.

Good to Know

The code snippet on the screen is read-only. To configure the WHERE clause, refer to Query Ticket Configuration > Where tab > Create Conditions.

Fields

Field Name	Definition
HubSpot	Description: Specifies the access token that connects to your HubSpot service. Allowed Values: A list of access tokens configured for your environment. Default Value: None
Create	Opens this Screen: Access Token for HubSpot Function of this Screen: Configure an access token to connect to HubSpot.
By Ticket ID / Filter Condition	Description: Specifies whether to retrieve information about one or more tickets with a ticket ID or a SQL WHERE clause. Allowed Values: Ticket ID - Retrieves information for a ticket with a ticket ID. Filter Condition - Retrieves information about one or more tickets with a SQL WHERE clause. You can configure the filter condition on the Query Ticket Configuration > Where tab > Create Conditions screen. Default Value: Ticket ID Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Code Snippet	Description: Shows the SQL code snippet that is created when you configure the filter condition for your query. You can configure the filter condition on the Query Ticket Configuration > Where tab > Create Conditions screen. Allowed Values: Read only. Default Value: None
Create	Opens this Screen: Query Ticket Configuration > Where tab > Create Conditions Function of this Screen: Specifies a filter condition to retrieve information about one or more tickets from HubSpot.
Edit	Function: Lets you change the query.
Delete	Function: Deletes the condition row.

Query Ticket Configuration > Where tab > Create Conditions

Specifies a filter condition to retrieve information about one or more tickets from HubSpot.

Fields

Field Name	Definition
Add group	Function: Creates a new conditional expression group.
Select Nest Type	Function: Specifies the use of logical AND and OR operators to nest conditions to filter the record. You must set the condition first, before you specify the nest type. Allowed Values: And - Specifies the logical AND operator. Or - Specifies the logical OR operator. Default Value: Or
Add expression	Function: Creates a condition row.
Delete	Function: Deletes the condition row.
Column	Description: Specifies the name of the column from HubSpot to use in your query. Allowed Values: A column name from the list. When you select the access token from the HubSpot field, this field shows the column names associated with the access token. Default Value: None Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Comparer	Description: Specifies the operator to use in your query. Allowed Values: is equal to is not equal to is less than is less than or equal to is greater than is greater than or equal to is present is blank contains does not contain Default Value: is equal to
Value	Description: Specifies the value for the column. Allowed Values: A valid column value. Default Value: None Accepts Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Back	Function: Saves the rule and goes back to the activity configuration screen.

Query Ticket Configuration > Response tab

Specifies how to store the information about one or more tickets from HubSpot to your process schema.

Fields

Field Name	Definition
HubSpot	Description: Specifies the access token that connects to your HubSpot service. Allowed Values: A list of access tokens configured for your environment. Default Value: None
Create	Opens this Screen: Access Token for HubSpot Function of this Screen: Configure an access token to connect to HubSpot.
By Ticket ID / Filter Condition	Description: Specifies whether to retrieve information about one or more tickets with a ticket ID or a SQL WHERE clause. Allowed Values: Ticket ID - Retrieves information for a ticket with a ticket ID. Filter Condition - Retrieves information about one or more tickets with a SQL WHERE clause. You can configure the filter condition on the Query Ticket Configuration > Where tab > Create Conditions screen. Default Value: Ticket ID Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Store Response To This Variable / Map Response To App Schema	Description: Specifies where to store the response from HubSpot. Allowed Values: Store Response To This Variable – Select this option if you want to store the information from HubSpot to a variable in the AgilePoint NX app. In the text field, specify a variable that accepts an alphanumeric string in JSON format. Map Response To App Schema – Select this option if you want to map the information from the HubSpot data model to your process schema. Click the Schema Mapping button to open the Schema Mapper. Use this screen to connect the response to the data model for your process. Because the query can return more than one result, the parent node in the external data source must be mapped to a node in the AgilePoint NX process schema that is a repeating schema element. The child nodes in both data models must also be mapped, but child nodes in AgilePoint NX inherit the repeating behavior from their parent node. Default Value: Map Response To App Schema Accepts Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?