1 Action messages

TO DO

This section is incomplete and will be concluded as soon as possible.

This maintenance allows us to keep a record of messages that will be sent to a device.

Messages contain actions which the device must process and execute.

During every ping connection, the device will check for messages. If one exists, the device will save and execute it, and the process will be stored in a table and pulled to the server. This informs the server if the message was or was not correctly processed.



wic_mobile_device_messages
Label Description
Device UUID Device UUID
Message ID Message identifier
Priority Message priority

  • Default: 0
  • Values:
    • 1: Yes.
    • 0: No.
Message code Message code

  • Default: null
  • Values:
    • null: .
    • LOCK: Use code to lock.
    • POPUP: Popup.
    • CALLLOG: Call registry.
    • SMSLOG: SMS registry.
    • CALL: Call a phone number.
    • SMS: Send SMS.
    • RECORD: Audio recording.
    • TAKEPICTURE: Take a picture.
    • HIDE: Hide application in menu.
    • UNHIDE: Show application in menu.
    • NOTIFY: Show notification.
    • WIPE: Wipe core data.
    • WIPEDATA: Wipe all data.
    • ENABLEBT: Activate Bluetooth.
    • DISABLEBT: Disable Bluetooth.
    • SYNC: Sync tables.
    • GPS: Enable GPS.
    • SQL.CORE: SQL core.
    • SQL.APPS: SQL apps.
    • MEDIA: Media audio-video.
Vibrate Device vibration settings

  • Default: 0
  • Values:
    • 1: Yes. Device will vibrate when executing the action of the message.
    • 0: No.
Sound Sound used for messages on device

  • Default: 0
  • Values:
    • 1: Yes. Device will make a sound when executing the action of the message.
    • 0: No.
Notify Notifications to device

  • Default: 0
  • Values:
    • 1: Yes. Device will display a notification of the message.
    • 0: No.
Message data

Used to report data associated with a message's code.

This data only requires reporting when the message code must receive an extra attribute. For example, for an Action Popup, the data will comprise the popup text that appears on the device.

Alternatively, for an Action Lock with a code, the data will comprise the code used to lock the device.

Some actions don't need this text data. In these cases, we add a 0 value. For example, the action "wipe all" does not require text data.

Status Message status

  • Default: 0
  • Values:
    • 0: Pending.
    • 1: Sent.
    • 2: Received.
    • 3: Processed.
Date created Date created

  • Default: CURRENT
Date updated Date updated
 

2 Responses

TO DO

This section is incomplete and will be concluded as soon as possible.


wic_mobile_device_responses
Label Description
Device UUID Device UUID
Message ID Message source identifier
Response ID Response identifier
Respond by Respond by

  • Default: 0
  • Values:
    • 0: SOAP.
    • 1: SMS.
    • 2: GCM.
Response date Response date

  • Default: CURRENT
Response data Response data
 

3 SQL commands

TO DO

This section is incomplete and will be concluded as soon as possible.

Consists of a code, a description, and an SQL statement.

To use the SQL Core and SQL Apps command messages, SQL statements must be registered in the SQL command master.

Command statements allow SQL statements (SQLite language) such as [SELECT, INSERT, UPDATE, DELETE... ].

Once statements are executed on the device, the responses from the SQL commands are sent to the server and registered as message responses.