Read Message from Device activity

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

Configure the Send Message to Device activity

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

Examples

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 Device activity onto your process.

General Configuration

Specifies the basic settings for the Read Message from Devive 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:

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

Read Message from Device Configuration

Configures how to store the message from your device.

Fields

Field Name	Definition
MS Azure IoT	Description: Specifies the access token that connects to your Microsoft Azure IoT service. Allowed Values: A list of access tokens configured for your environment. Default Value: None Accepts 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	Description: Specifies the device ID for your IoT device. Allowed Values: A valid device ID. 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?
Device Key	Description: Specifies a device key from Microsoft Azure IoT. Allowed Values: A valid device key from Microsoft Azure IoT. 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?
Retry Count	Description: Specifies the number of times Microsoft Azure IoT tries to read messages from the IoT devices. Allowed Values: An integer. Range: Greater than 0 Default Value: 60 Accepts Variables: Yes
Delay Between Retry (milliseconds)	Description: Specifies a time interval in milliseconds between each retry. Allowed Values: An integer. Range: Greater than 0 Default Value: 1000 Accepts Variables: Yes
Payload	Description: Specifies the payload to store at runtime. Allowed 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 to Schema button to open the Schema Mapper screen. Use this screen to connect the response to process schema. 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?
Sample Payload JSON	Description: Specifies a JSON code snippet that connects your payload to the process schema. To Open this Field: On the Read Message from Device Configuration screen, click Map Response to Process Schema. Allowed Values: A JSON code snippet. Default Value: None Accepts Variables: No
Map Schema	Opens this Screen: Schema Mapper screen To Open this Field: On the Read Message from Device 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?