Backend

What is Backend

Let's take a look at one of the three elements of Mobsted PWA Platform is based on - the Backend. The other two are the Constructor and the Objects.

Backend can store data that is relevant to Obect(s). It could be actions(Events) performed by the Objects (Event of clicking the particular button), resources that are available for the Object (Payment Bill or Products Selected) or actions performed by the Servicers on the Objects.

What is Event

Each action or an Event is stored as the separate line in the Backend.

Event can keep any kind of activity made by the Object of App, like: login info, the button pressed and the info entered / selected on the corresponding screen, status changes by the servicer, etc.,

For example: the AppUser (Object) clicked the button that some printer has paper missing. And we can set up the particular Event to be created when the button is clicked and the particular Responsible Servicer (Hardware manager, who would assign the someone to go and insert the paper into the printer) to be notified when the Event is created (read more about that in _Triggers_ section). Also, and the particular _Status_ would be assigned to the Event created. Once the printer would be filled with the paper, the Responsible Servicer can change the Status of the Event (for example from Open to Complete) in the Backend, or by clicking the correlating button in his PWApp. After that we can say that this event was Completed.

How to find Backend on the Platform

You can access Backend by mouse overing mouse button of the App on the home screen of the platform and selecting Backend from the list.

Custom Columns

Custom Columns for the Backend are added for the purpose related only to the Event, but not the Object attribute.

For example: the AppUser Object presses the button in the PWApp that Printer Object needs Ink cartridge to be replaced. The corresponding event would be created in the Backend

By clicking "Add Custom Column" you would start the process of adding new Column(Property) to your Objects. First, properties tab will slide from the side, where you'll be asked to feel in some fields to set up the column.

The fields are:

  • Column name
  • Its Default Value: meaning what would be stored in it before any parameter would be assigned,

and one checkbox:

  • Hide column from object: Means that in the History system screen _link to history system screen description_ this column would be hidden from the Object.

Set up View of the Backend Table

Sometimes we need to hide one set of columns and show another one.

We can easily do that by clicking the Setup Table button you can customize the columns you would see in the table by checking the checkboxes in the menu appeared. You can also customize the order of the columns by drag and dropping them in the menu. In the menu columns are displayed as rows.

Reading the Event

By clicking on the Event you would open up the details of the Event.

The pop-up would contain all the information about the object like the geolocation, details on the device that he accessed the App as well as the new data that was submitted by the button press. As we remember each action is created upon the setup of the app and can be created by the button press image press or the link press. In addition to this we have a chat window built-in using which you can communicate with the object. So let's have a closer look on what info for does the event provide us and a how to properly read it.

  1. The first dropdown shows us the responsible servicer that would be responsible for this event. The servicer would receive the notifications on the new Events of this kind created, as well as the status changes of the existing events. If the event doesn't require any servicer involved, the field would be blank.
  2. The second drop-down shows us the current Status of the event. the status can be tracked by using filters or the status can be ignored if it is not needed. The status is also could be changed here. Click here to access Statuses section.
  3. The Third Field shows us the location of the of the device when the event was created.
  4. In the highlight numbered Four you can see all the info on the current event. The event that was created when the AppUser pressed the corresponding Button contains all the information from the screen, like the text that was entered into Text Areas or the Switchers that were switched or the drop-down selections, everything would be stored in this current event.
  5. The fifth section would contain files if any file was attached event using the file element.
  6. The sixth section would contain all the metadata on the Object like which browser he used to access the app, which version of operating system, etc.
  7. The 7th section contains all the information about the Object that the event applies to. This is used for convenience purposes so you don't need to navigate back and forth between Backend and the Objects tabs.
  8. The 8th section is the chat block. Using this block the servicer can communicate with the Object regarding this particular event. The object can access the chat by using history button on their App, that connects with that _history system screen_. The chat is used mostly if something needs to be clarified the Object or the servicer needs to send an update on the Event (which could be done using statuses as well).

Chat Event for the Servicers

The Chat event allows Servicers to chat with AppUsers, The chat is also accessible from instant messengers and social networks, if they are connected.

Filter by Column

You can perform simple filtering by just start typing the required string in the column header and pressing enter to see the results applicable.

For the complex filtering please visit the Filters Page.

External Connections

Please check this article to learn about passing the events to external systems.


How did we do?