Read Message from Event Hub activity

An activity that reads a device-to-cloud message from Event Hub that is registered in Microsoft Azure IoT.

Configure the Read Message from Event Hub activity

To configure the Read Message from Event Hub activity, do the procedure in this topic.

Prerequisites

AgilePoint NX OnDemand (public cloud), or AgilePoint NX Private Cloud or AgilePoint NX OnPremises v7.0 Software Update 1 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 MS Azure IoT tab.
On the MS Azure IoT tab, drag the Read Message from Event Hub activity onto your process.

General Configuration

Specifies the basic settings for the Read Message from Event Hub activity.

Good to Know

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

Fields

Field Name	Definition
Display Name	Function: Specifies the activity name that shows in your process. Accepted Values: One line of text that can have spaces. Default Value: None Accepts Process Data 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	Function: Specifies an optional text description for your activity. Accepted Values: More than one line of text. Default Value: None Accepts Process Data Variables: No

Field Name

Definition

Display Name

Function:

Specifies the activity name that shows in your process.

Accepted Values:

One line of text that can have spaces.

Default Value:

None

Accepts Process Data Variables:

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

Function:: Specifies an optional text description for your activity.
Accepted Values:: More than one line of text.
Default Value:: None
Accepts Process Data Variables:: No

Read Message from Event Hub Configuration

Configures how to store the message from Event Hub.

Fields

Field Name	Definition
MS Azure IoT	Function: Specifies the access token that connects to your Microsoft Azure IoT service. Accepted Values: A list of access tokens configured for your environment. Default Value: None Accepts Process Data Variables: No
Create	Opens this Screen: Access Token for Microsoft Azure IoT Function of this Screen: Configure an access token to connect to Microsoft Azure IoT.
Device ID	Function: Specifies the device ID for your IoT device to read message. Accepted Values: A device ID from Microsoft Azure IoT. Default Value: None Accepts Process Data 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?
Retry Count	Function: Specifies the number of times Microsoft Azure IoT tries to read messages from Event Hub. Accepted Values: A positive integer. Default Value: 60 Accepts Process Data Variables: Yes
Delay Between Retry (milliseconds)	Function: Specifies a time interval in milliseconds between each retry. Accepted Values: A positive integer. Default Value: 1000 Accepts Process Data Variables: Yes
Payload	Function: Specifies the payload to store at runtime. Accepted Values: Save Response To This Variable - Specifies a process data variable to store the JSON payload at runtime. Map Response to Process Schema - Connects the values in your payload with your AgilePoint process schema. Click Map Schema button to open the Schema Mapper screen. Use this screen to connect the response to process schema. Default Value: None Accepts Process Data 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?
Sample Payload JSON	Function: Specifies a JSON code snippet that connects your payload to the process schema. To Open this Field: On the Read Message from Event Hub Configuration screen, click Map Response to Process Schema. Accepted Values: A JSON code snippet. Default Value: None Accepts Process Data Variables: No
Map Schema	Opens this Screen: Schema Mapper screen To Open this Field: On the Read Message from Event Hub Configuration screen, click Map Response to Process Schema. Function of this Screen: Maps SharePoint fields, form fields, web methods, or other input sources to an XML schema.. 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?