Event is the record in the Backend. It can be created on the following actions:
This new record can contain any data you wish to stored in it.
How to create an Event on button click
- Select "Actions" in the Properties of the Single Button / Link / Image
- Click "Create Event"
- Fill in the table where "Key" is the name of the field for the data and "Value" is the dynamic parameter to be stored in it. Can hold Hashtag reference.
- Click "Save"
Where to find an Event Created
Navigate to the Backend of the platform, the corresponding row was created and contains all the info that should be stored. If you click on the Event you would see some metadata about it like the Event name and the values it stores.
Reading the Event
Click on Event to open up its details.
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.
- 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.
- 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.
- The location of the of the device when the event was created.
- 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 drop-down selections, everything would be stored in this current event.
- Files if any file was attached event using the file element.
- The metadata on the Object like which browser he used to access the app, which version of operating system, etc.
- The information about the Object that this event applies to. This is used for convenience purposes to avoid the need to navigate back and forth between Backend and the Objects tabs.
- Chat block. Using this block the servicer can communicate with the Object regarding this particular event. 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). For the AppUser the chat would be available from the App and would also have dialog view. Is also accessible from instant messengers and social networks, if they are connected.
Working with Events using API Calls
In order to Create / Update / Delete an Event using API Request you should do the following:
- Get Access token - https://documenter.getpostman.com/view/4564343/S11LscyP#8cdbe179-7e2d-6218-9273-0df0bc8edfdf
- Create / Update / Delete the Event - https://documenter.getpostman.com/view/4564343/S11LscyP#cfffad1b-9646-94a2-e74a-7eb03235caf3
Good and Almost Good Practices
Events are mostly used when you want to submit some dynamic data.
Could be Better
You have a "Submit a complain form" with some dropdowns or text inputs as well the button to submit the complain. Since one AppUser can submit multiple complains, it's is good idea to create an event for the button press and store the data from the dropdown and text input in this Event.
You have a "Enter your personal info form" asking the AppUser for the name and DOB. Creating an Event for the button to submit the info entered is redundant since this info is static and would be probably asked only when the AppUser opens the App for the first time.