Promotic
WikipediaLinkedInYoutubeTwitterFacebook

Preconfigurations Sending messages to "Maatrix" mobile application service

Creates PmFolder, PmSequencer objects and panel for sending messages to mobile application of the Maatrix service.
 
This preconfiguration can be activated when creating a new object (e.g. by "New object" in the local object menu or by pressing the Insert key after selecting the object) and is included in the group: " / Communications / XML, CSV, text files, Maatrix".

This preconfiguration can be used with the objects: PmFolder or PmRoot.

 
The "Maatrix" service (see www.maatrix.eu) provides mobile messaging to its registered users of the mobile application "Maatrix".

More at: Maatrix WEB service: communication with mobile apps.

For this purpose, configurable templates are used for different message types. The preconfiguration allows usage of four templates from the section:

Templates by connected systems
SCADA systems
SCADA PROMOTIC by Microsys
Templates for predefined system settings
Template1 - Information message about alarm of SCADA Promotic - Simple information message regarding alarm/incident. The users are just informed about the alarm and the only possible expected response is confirmation by OK.
Template2 - Reaction on alarm of SCADA Promotic - Message regarding alarm/incident. The users are informed about the alarm and the expected response can be "can come"/"cannot come"..
Template3 - Reaction on alarm of SCADA Promotic 2 - Message regarding alarm/incident. The users are informed about the alarm and the expected response can be "can come"/"cannot come". If in the first round nobody reacts or nobody responses "can come" then the message is sent in second round to additional users and also to tho who did not react in the first round.
 
At the end a message is sent to all users that a user able to come to solve the incident has been found or has not been found.
Template4 - Reaction on alarm of SCADA Promotic 3 - Message regarding alarm/incident. The users are informed about the alarm and the expected response can be "can come"/"cannot come". If in the first round nobody reacts or nobody responses "can come" then the message is sent in second round to additional users and also to tho who did not react in the first round.
 
Similarily, if nobody is available in the second round, third round follows. At the end a message is sent to all users that a user able to come to solve the incident has been found or has not been found.
 
User list is transmitted from PROMOTIC SCADA system as a list of specific users (e-mail addresses) or by role code. This way the users are contacted in the first round. In following rounds the user are informed based on their roles assigned to the communication block in the Maatrix system.
 
The preconfiguration communicates with the service by the HTTPRequest where the "message body" (<:Appeal>) contains JSON data. For each of the templates, it is possible to define the Interfaces in the configurator Call Service Interfaces as Interface SCADA Promotic. This way the service templates are made available for usage in this preconfiguration. Each of these then obtains the specific 9-character code ServiceID and also the M2Mpswd (M2M password). The InterfaceID is common (interface ID in "Open" state).
 
These codes must be entered at the beginning of the script in method Template_Send of the PmSequencer object. The method has five input parameters defined and can be called anywhere from the application:
Template - defines the template to be used for sending the message ("Template1" - "Template4")
sSubject - mobile application message subject
sAppeal - mobile application message content
idRole - role identifier (defined group of registered users)
sUsers - defines the registered users (recipients) of the mobile application message (mail addresses separated by comma).
These parameters are processed into the JSON type format and then are passed together with additional parameters by the PmSequencer.Add method to sending.
 
Methods m_JsonProp, m_JsonPropOption, m_JsonPropUsers and InterfaceID auxiliary and are used for message formatting. Method answerService is used for repeated requests and for obtaining message status (success/failure). Method Template_Sumary processes the reply result requested by answerService method.
 
There is a graphic panel included in the preconfiguration that can be used for testing purposes, but it is not necessary for communication.
 
The preconfiguration is created including the panel (PmPanel object) functionality as a WEB panel. In order to make the preconfiguration functional also for the WEB, it is necessary to enable the PmPanel object for the WEB (on the Web Server page).
These configurators can be set before the preconfiguration is created:
The name of created objectName of the object created in the application object tree. This is a system name and must not contain empty string, diacritics, spaces and the first character must not be a number.

Default: "Maatrix_Msg"

Login codes to Maatrix service. 9-characters without "-".
Interface identifier9-character code starting with letters int that identifies the interface type as "Interface SCADA Promotic". It is defined on the "interface" page located in the customer settings section.
Template identifier19-character code starting with srv letters (service ID) of the template used
M2M password19-character code (M2M password) of the template used
Template identifier29-character code starting with srv letters (service ID) of the template used
M2M password29-character code (M2M password) of the template used
Template identifier39-character code starting with srv letters (service ID) of the template used
M2M password39-character code (M2M password) of the template used
Template identifier49-character code starting with srv letters (service ID) of the template used
M2M password49-character code (M2M password) of the template used
© MICROSYS, spol. s r. o.Tavičská 845/21 703 00 Ostrava-Vítkovice