Creates
PmaFolder,
PmaSequencer 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 context menu of the object or by pressing the
Insert key after selecting the object).
This preconfiguration is included in the
"/ Communication / Protocols and other communications / Email" group.
This preconfiguration can be created in the
PmaFolder,
PmaRoot or
PmaPrototype object.
The "
Maatrix" service (see
http://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 settings of the PROMOTIC system
Template1 - Information message about alarm in the PROMOTIC application - 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 the PROMOTIC system - 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 the PROMOTIC system 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 if 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 the PROMOTIC system 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 if 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, then 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 the PROMOTIC application 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 format data. For each of the templates is at
http://www.maatrix.eu on the
"Interfaces" tab in the
Call Service Interfaces configurator preset to
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 the state "Open").
These codes must be entered at the beginning of the script in the
"Template_Send" method of the
PmaSequencer object. The method has five input parameters defined and can be called anywhere from the application:
Template - specifies 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 - specifies 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
PmaSequencer.Add method to sending.
Methods
m_JsonProp,
m_JsonPropOption,
m_JsonPropUsers and
InterfaceID are auxiliary and are used for message formatting. The
"answerService" method serves for repeated requests and for obtaining message status (success/failure). The
"Template_Sumary" method processes the reply result requested by the
"answerService" method.
There is a graphic panel included in the preconfiguration that can be used for testing purposes for sending of messages, but it is not necessary for communication.
The preconfiguration is created including the panel (object of the
PmaPanel type) is functional also as
Web panel. In order to make the preconfiguration functional also on the Web, it is necessary to enable the object of the
PmaPanel type for the Web (on the "
Web server" tab).
These configurators can be set before the preconfiguration is created:
| The name of created object | Name of the object created in the Pma object tree.
The maximum name length is 30 characters.
This is a system name, so it must contain only alphanumeric and must not contain any diacritics (i.e. national dependent characters), empty string, spaces and first character must not be a number.
Default: "Maatrix_Msg" |
|---|
|
| Login codes to Maatrix service. 9-characters without "-". | |
|---|
| Interface identifier | 9-character code starting with letters int that identifies the interface type as Interface SCADA Promotic. It is defined on the "interface" tab located in the customer settings section. |
|---|
|
| Template identifier1 | 9-character code starting with srv letters (service ID) of the template used |
|---|
| M2M password1 | 9-character code (M2M password) of the template used |
|---|
|
| Template identifier2 | 9-character code starting with srv letters (service ID) of the template used |
|---|
| M2M password2 | 9-character code (M2M password) of the template used |
|---|
|
| Template identifier3 | 9-character code starting with srv letters (service ID) of the template used |
|---|
| M2M password3 | 9-character code (M2M password) of the template used |
|---|
|
| Template identifier4 | 9-character code starting with srv letters (service ID) of the template used |
|---|
| M2M password4 | 9-character code (M2M password) of the template used |
|---|