Difference between revisions of "SYSCLS PUSH TOPIC"
(2 intermediate revisions by one other user not shown) | |||
Line 9: | Line 9: | ||
}} | }} | ||
+ | An object classified by the Push Topic classification is considered as Native Push Topic. | ||
+ | Based on the publish/subscribe model,Topic Messaging allows you to share a message across multiple devices that have a specific topic enabled. | ||
+ | The system takes care of routing and reliably delivering the message to the right devices if a composed messages on topics is sent. | ||
== MetaProperties == | == MetaProperties == | ||
Line 17: | Line 20: | ||
| TOPIC || {{string}} || Push Topic | | TOPIC || {{string}} || Push Topic | ||
|- | |- | ||
− | | ACTIVE || {{bool}} || Indicates | + | | ACTIVE || {{bool}} || Indicates whether pushes should be sent for this topic. |
|} | |} | ||
== See also == | == See also == | ||
− | * [[ | + | * [[SYSCLS_NATIVE_PUSH_ITEM|Push Item]] |
Latest revision as of 09:53, 10 October 2024
An object classified by the Push Topic classification is considered as Native Push Topic. Based on the publish/subscribe model,Topic Messaging allows you to share a message across multiple devices that have a specific topic enabled. The system takes care of routing and reliably delivering the message to the right devices if a composed messages on topics is sent.
MetaProperties
Name | Data type | Comment |
---|---|---|
TOPIC | String | Push Topic |
ACTIVE | Bool | Indicates whether pushes should be sent for this topic. |