One of the possibilities realized in the platform is sending notifications. It allows controlling values of parameters, a current state of an object, and, as a consequence, execution of business processes. For that, the subsystem “Registration” is added to every model, to external program modules by default. It includes the list of actions that can be executed by device for some events registration. Particularly, sending notifications may be implemented with the benefit of three commands which can be used by designing logic:

  • “Message to operator”;
  • “Make HTTP request”;
  • “Send e-mail”.

When sending messages to the operator on the platform,    they are displayed in the platform interface on the right sidebar of the messages. Sending notifications via an HTTP request suggests sending information to an external service by using HTTP protocol technologies. The alternative variant of the sending notifications is sending by e-mail. At the same time, the user can use one or several methods of informing about the current state of the object.

In all three types of notifications, not only general information about the occurred event, but including actual current values of parameters may be transmitted to the user. They can be written both explicitly and by using the {{state.id_of_parameter}} construction: the state word is entered in double brackets, and after that, the parameter ID is specified through the dot.

For instance, the notification body may be formed in such way:

  "event": "temperature_increasing",
  "temperature": {{state.temp}}

Then in the first line, the data about the occurred event will be transmitted, in the second – the current value of the specified parameter.

It is worth noting that the notification format is not strictly regulated. There is just an example of what can be transmitted in the message. Its body itself may be formed in a more arbitrary way, depending on which the notifications type is used.

In all of these three cases, using the notifications will allow observing current alterations that occurred by the logic execution. If in the process of building a final state machine, one or more commands are added to any state, the system will send a necessary notification when the object will transmit to the current state. The message will inform the user that a certain event has occurred, in consequence of which the object now is in the corresponding state. As a result, by sending the notifications constantly, the user will always be notified about the business processes implementation and the logic realization.