This allows the cloud (or other external system) target to assign it’s own identifier or primary key to export-marked points in the station, which can be used to locate them in future or included in exports to that cloud system.

You add this router to a station by expanding the in the palette and dragging this component to the Config folder in the Nav tree.
In addition to the standard property (Enabled), these properties support the JsonMessageRouter.
| Property | Value | Description |
|---|---|---|
| Last Result | read-only | Reports the results of the alarm acknowledgment to allow for logging or post-processing activity. Example output:
|
| Last Result Time | read-only | Reports when the handler ran last. |
| Last Input | read-only | Reports the last message routed to a component. |
| Status | read-only | Reflects the current status of the component.
Ok indicates the JSON processed successfully. fault indicates the JSON did not process for any reason, such as invalid JSON or missing expected values in the JSON. |
| Learn Mode | true or false (default)
|
true configures the JSON to add a dynamic slot on input for any newly-found message key.
|
| Key | text (defaults to messageType) | Defines which part of the incoming message to switch on) |
| Resend With Blank | true or false (default)
|
Turns on and off the resending of a message if a duplicate or matching message is received.
Without injecting an empty message, the link does not propagate the change, which could be an issue if the handler needed other values in place to respond to this message.
|
These actions are available when you right-click on the JsonMessageRouter.

String parameter and update the Out slot.