Salesforce

MQTT - Dynamic Interface (Magic xpi 4.5)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

MQTT - Dynamic Interface (Magic xpi 4.5)

The MQTT connector is designed to work with Magic xpi’s dynamic interface. When you drag the MQTT connector into a flow, the Properties pane opens. Then, double-click or right-click on the connector and select Configuration from the context menu to open the connector's Configuration dialog box.

This dialog box contains the following fields:

Property

Description

Connection

Resource Name

The name of the resource that you selected in the component's Properties pane. The resources are defined in the Settings dialog box's Resources section..

Publish Settings

QoS

The Quality of Service when sending the message. Select one of the following from the drop-down list:

  • 0 (default): At most once.

  • 1: At least once.

  • 2: Exactly once.

Retained

Determines whether the broker will hold onto a message after it has been sent. Select one of the following from the drop-down list:

  • No (default)

  • Yes

Result Options

Store Result In

Defines where you want to store the resulting XML file. Select one of the following from the drop-down list:

  • Variable: Select a variable to hold the data that is returned by the MQTT.
    Click to open the Variables List. Select a variable where this information is to be stored (the default is C.UserBlob).

  • File: Select a file to hold the data that is returned by MQTT.
    Click to open the Expression Editor, or click and enter the file path where this information is to be stored.

Operation Success

This field lets you easily determine if the data was successfully located in MQTT. Select one of the following from the drop-down list:

  • None: Select this option if you do not want to save the connector’s success or failure status.

  • Variable: Click to open the Variables List. Select the variable where you want to store the connector's success or failure status.

Note:

In the step's Data Mapper, since the payload node is a BLOB, it will be published as-is in its original encoding.

Reference
Attachment 
Attachment