Hashtags

Mobsted hashtags PWA maker helps you to get data from different parts of the system.

You can use hashtags in the Properties of the elements in the Constructor, _API Operations_, and when sending messages to the Objects.

Hashtags allow you to view and access data on:

There are system columns in the Objects and Custom Columns created by the administrator or servicer. Each of those columns can be accessed using hashtags.

For example: if the administrator created a column in the Objects table named “MyPersonalInfo”, the hashtag would be “#Object: MyPersonalInfo #”. Whenever and where this hashtag is set, our system will return the value of the column of the Object.

Example of using Hashtags

Let's take a live look at the usage and usefulness of the Hashtags by examining the following example:

In our Objects database we have Object Alex with this phone number and email provided and we want to say hi to Alex and invite him to install the App.

We need to select this Object and send him message:

In the Window Opened we want to say hi to Alex and ask him to install the App. That's where hashtags are being used.

On the left handside you can see the list of the hashtags available. We are selecting the Hashtag that contains the Object name and the Invite Link.

When the message is sent the Hashtags would be generated into the values that are stored in the corresponding fields.

List of supported hashtags:

1. Current Object:
  • #Object:id# - Unique ID of the Object
  • #Object:PIN# - Login PIN
  • #Object:Phone# - Phone number of the Object
  • #Object:Email# - Email of the Object
  • #Object:InviteUrl# - personal short link to enter the Aoo on behalf of the Object
  • #Object:Enabled# - Object Status, of 0 - OFF then the Object would not be able to access the App
  • #Object:LastLogin# - The last entry date of the Object in the application
  • #Object:InviteStatus# - The status of an invite sent to the Object
  • #Object:StartScreen# - ID of the start screen
  • #Object:Timezone# - Current time zone
  • #Object:AutomaticalTimezone# - setting status automatic time zone, could be 1 - ON or 0 - OFF
  • #Object:*anyColumnName*# - and column created in the Backend by the Servicer, for Example #Object:House number#.

_____________________________________________________________________________

2. Current Screen:
  • #Screen:id# - Unique ID of the Screen
  • #Screen:Name# - Screen Name
  • #Screen:SortOrder# - Sequential screen number created in the Constructor
  • #Screen:DateCreate# - Screen creation date

_____________________________________________________________________________

3. Current App
  • #Application:id# - App unique identified
  • #Application:Name# - App name when stored on a mobile device
  • #Application:Category# - App category. If the App was created from the template the ID of the category template belongs to would be stored in the Category, if Blank Application was selected, Category would store 0
  • #Application:ShortDescription# - Short Description of the App from the Naming Your Work step.
  • #Application:DateCreate# - App creation date and time
  • #Application:ThumbImageUrl# - Link to an image used as an App icon
  • #Application:LoginCount# - The number of valid entries in the application, is set on _Registration and Security step_
  • #Application:Geolocation# - Security setting status "Geoposition" (3 parameters are shared: range, latitude, longitude)
  • #Application:Range# - the allowed range for the App around the specified point on the map (when the "Geo position" security setting enabled)
  • #Application:Latitude# - the latitude at which the App will be allowed for use (when the "Geo-position" security setting enabled)
  • #Application:Longitude# - the longitude at which the App will be allowed for use (when the "Geo-position" security setting enabled)
  • #Application:EmailPhone# - identification type: Email or Phone Number
  • #Application:PIN# - if the PIN code is set to log into the App, could be YES or NO
  • #Application:CreateObjects# - auto-create object when accessing an App, could be YES or NO
  • #Application:Everytime# - identification at each entrance to the Application, could be YES or NO
  • #Application:EventNotify1# - type of initial notification: Email, Text Message, Push, or Not Selected
  • #Application:EventNotify2# - type of initial notification: Email, Text Message, Push, or Not Selected
  • #Application:EventNotify3# - type of initial notification: Email, Text Message, Push, or Not Selected
  • #Application:DesktopName# - App name in Mobsted PWA maker
  • #Application:Template# - App template. If the App was created from the template the ID of the template would be stored in the Category, if Blank Application was selected, Template would store 0
  • #Application:IP# - security configuration status "IP address" (used with parameters subnet mask 1 and 2)
  • #Application:Mask1# - subnet mask 1 (with the "IP address" security setting enabled)
  • #Application:Mask2# -subnet mask 2 (with the "IP address" security setting enabled)

_____________________________________________________________________________

4. System
  • #System:SentSMSCount# - Number of SMS sent in the current Tenant
  • #System:SentEmailCount# - Number of Emails sent in the current Tenant
  • #System:SentPushCount# - Number of Push notifications sent in the current Tenant

_____________________________________________________________________________

5. Current Tenant
  • #Tenant:Name# - Tenant name
  • #Tenant:UserName# - Name of the creator(Client) of the tenant, specified when registering
  • #Tenant:MobileNumber# - Phone number of the creator(Client) of the tenant, specified when registering
  • #Tenant:Country# - Country of the creator(Client) of the tenant, specified when registering
  • #Tenant:LastModified# - Date of the last change
  • #Tenant:Tariff# - Mobstead tariff for the tenant usage
  • #Tenant:PaidUntil# - the date up to which the Mobsted fare was paid

_____________________________________________________________________________

6. Filter
  • #ObjectsFilter:FilterName:FilterValue# - Objects filter data
  • #EventsFilter:FilterName:FilterValue# - Events filter data
FilterName is the Unique Name of the Filter.

In the hashtags above FilterValue can have the following values:

  • Value - Filter value
  • Count - Number of entries that apply to the Filter
  • PercentChange - Percent change
  • Units - Measure Units for the filter
  • LastUpdate - Filter value update date

SelfId, SelfPhone modifiers are allowed for filter hashtags.

For example: #ObjectsFilter:FilterName:FilterValue:SelfId# In this case, the restriction of using data of only the current Object would be added to the Filter.

_____________________________________________________________________________

7.Repeat

#Repeat:backend_BackendColumnName#

#Repeat:objects_ObjectColumnName#

_____________________________________________________________________________

8. Current event (is available after running the Event Trigger)

#CurrentEvent:BackendColumnName#

#CurrentEvent:Value:*DynamicBackendColumnNameInTheValueField*#

_____________________________________________________________________________

9. Current User (Servicer)
  • #CurrentUser:id# - Unique identifier of the Servicer
  • #CurrentUser:Name# - Servicer Name
  • #CurrentUser:Email# - Servicer Email
  • #CurrentUser:Phone# - Servicer Phone number
  • #CurrentUser:PIN# - Servicer PIN
  • #CurrentUser:Roles# - list of Roles available for the Servicer
  • #CurrentUser:Roles:StartScreenUrl# - full URL of the start screen for the role;
  • #CurrentUser:Password# - Servicer Password
  • #CurrentUser:Timezone# - Servicer time zone
  • #CurrentUser:Language# - Servicer language
  • #CurrentUser:IsSuperAdmin# - if the Servicer is SuperAdmin. 1-Yes, 0-No.

_____________________________________________________________________________

10. Backend Names (available for use in the Constructor, working with temporary data of AppUser)
  • #Backendname:textinput# - Value entered into the Text Input Element by the AppUser ("textinput" is the BackendName of the Text Input Element)
  • #Backendname:radio:text# - Text of the selected Option in the Radio Buttons Element by the AppUser ("radio" is the BackendName of the Radio Buttons Element)
  • #Backendname:radio:value# - Value stored in the selected Option in the Radio Buttons Element by the AppUser ("radio" is the BackendName of the Radio Buttons Element)
The described hashtag syntax is applicable for checkboxes as well

_____________________________________________________________________________

11.Variables

#variable:myvar1# - value that is stored in "myvar1" variable.

_____________________________________________________________________________

12. Operations
  • #Operation:OperationName:Response:Code# - HTTP status code after executing the operation
  • #Operation:OperationName:Response:Result[0].value# - data received as the response to the Operation execution ([0] - this array contains the entire response to the API request, value is an example of a key in the structure of the API response the value of which you want to receive. [nesting can be multi-level, nesting levels are separated by a dot]. )
  • #Operation:OperationName:Error:Code# - HTTP status code (in case of error), after performing the Operation
  • #Operation:OperationName:Error:Result[0].value# - data received as the response to the failed Operation execution ([0] - this array contains the entire response to the API request, value is an example of a key in the structure of the API response the value of which you want to receive. [nesting can be multi-level, nesting levels are separated by a dot]. )

OperationName – The operation name assigned in the list of operations.

For example:

#Operation:GetClientInfoOperation:Response:Result[0].data.result.sc_agreement_info.agr_number#

#Operation:GetClientInfoOperation:Response:Result[0].data.messages.text#

#Operation:CancelAllTimeslotsOperation:Error:Result#


How did we do?