Hashtags

Updated 1 month ago by Mobsted Support V

Mobsted hashtags is the way to access or reference data on any part of the platform - such as HTML Element, Screen, App, etc - from any part of it.

Hashtags are used in the Properties of the elements in the Constructor, API Operations, Filters and when sending messages to the Application Users.

Use examples:

Constructor:

Hashtags are used to display Object data:

Constructor View

Application User View

_____________

API Operations:

Hashtags are used to send dynamic data (city name) in API calls:

Sending personalized messages to Application Users:

Where hashtags can be used:

Current Tenant (Mobsted Account)
  • #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# - fee for the Mobsted platform usage.
  • #Tenant:PaidUntil# - the date up to which the Mobsted fare was paid

System
  • #System:SentSMSCount# - Number of SMS sent from the current Tenant (Mobsted Account).
  • #System:SentEmailCount# - Number of Emails sent in the current Tenant (Mobsted Account).
  • #System:SentPushCount# - Number of Push notifications sent in the current Tenant

Current User (Business 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.

Current Application
  • #Application:id# - Unique Application identifier
  • #Application:Name# - App name when stored on a mobile device
  • #Application:Category# - App category. Would store the template ID. If the App was created as Blank Application, the column 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 application opens, 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. Is used in Guaranteed Smart Delivery.
  • #Application:EventNotify2# - type of secondary notification: Email, Text Message, Push, or Not Selected. Is used in Guaranteed Smart Delivery.
  • #Application:EventNotify3# - type of third notification: Email, Text Message, Push, or Not Selected. Is used in Guaranteed Smart Delivery.
  • #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)

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

Variables

#variable:myvar1# - value that is stored in "myvar1" variable. Please reference Variables article to get familiar with them with greater details.

Constructor Elements Backend Names
  • #Backendname:textinput# - Value entered into the Text Input Element by the AppUser ("textinput") is the BackendName of the Text Input Element)

______

  • #Backendname:radio:label# - Text of the selected Option in the Radio Buttons Element by the AppUser ("radio" is the BackendName of the Radio Buttons Element). Example: #Backendname:radio:0:label# - to reference the label of the first element of the radio 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). Example: #Backendname:radio:0:value# - to reference the value of the first element of the radio element.

_____________

Special case: checkboxes

Use #Backendname:PolicyAgreeCheckBox[0]:label# to reference the label of the first selected element of the checkbox

Use #Backendname:PolicyAgreeCheckBox[0]:value# to reference the value of the first selected element of the checkbox

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:LoginUrl# - personal short link to enter the Aoo on behalf of the Object
  • #Object:Enabled# - Object Status, if 0 - OFF - the Object would not be able to access the App
  • #Object:LastLogin# - The date of the User launched the Application the last time
  • #Object:InviteStatus# - The status of an invite sent to the Object
  • #Object:HomeScreen# - 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 Object, for Example #Object:Balance#.

Creating Loops
  • #ObjectsFilter:FilterName:Data# - creating loop that contains data based on the Objects filter
  • #EventsFilter:FilterName:Data# - creating loop that contains data based on the Events filter
  • #Operation:OperationName:Response:Result:0:response:holidays# - creating loop that contains data on the API call

Example:

Referencing filter in the loop definition.

Referencing Loops
  • #Loop:LoopName:OperationParameterName# - referencing the repeated element of the API Operation that is specified in the LoopName
  • #Loop:LoopName:objects@Phone# - referencing the Phone column of the Objects based on filter that is set in the LoopName

Example:

Displaying columns of the Objects, that fall to the Filter condition.

Application User View:

Filter
  • #ObjectsFilter:FilterName: FilterValue# - get count on the Objects filter
  • #EventsFilter:FilterName: FilterValue# - get count on the Events filter
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 feature of using data of only the current Object would be added to the Filter.

Merge Filters

The filter can contain either AND or OR. In order to merge OR and AND conditions use hashtags within the new filter.

For example: Let's create the filter that would display everyone with email on Mobsted OR Outlook domain, and who have US phone number.

Venn diagram demonstrating the logic of the filter on Mobsted PWA platform

  • First filter would contain the required Email condition, we will name it as Email.
Simple filter created on Mobsted PWA platoform

  • Second filter would contain the required Phone condition merged with the condition filtering Emails that fall into the First Filter
Filter with nested Filter in it created on Mobsted PWA platform

  • #ServerSide:ObjectsFilter:Email:Data@join(",", "objects@Email")#

Current event (is available after running the Event Trigger)

#CurrentEvent: BackendColumnName#

#CurrentEvent:Value: *DynamicBackendColumnName InTheValueField*#

______

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. Nesting can be multi-level, nesting levels are separated by a dot OR semicolon.
  • #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. Nesting can be multi-level, nesting levels are separated by a dot OR semicolon.

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

Example:

After running the operation of checking the weather at the location highlighted yellow, you might get the following data:

{ 
"meta": [],
"data": {
"Response": {
"Result": [{
"location": {
"name": "London",
"region": "City of London, Greater London",
"country": "United Kingdom",
"lat": 51.520000000000003,
"lon": -0.11,
"tz_id": "Europe\/London",
"localtime_epoch": 1555318097,
"localtime": "2019-04-15 9:48"
},
"current": {
"last_updated_epoch": 1555317913,
"last_updated": "2019-04-15 09:45",
"temp_c": 9,
"temp_f": 48.200000000000003,
"is_day": 1,
"wind_mph": 15,
"wind_kph": 24.100000000000001,
"wind_degree": 90,
"wind_dir": "E",
"pressure_mb": 1023,
}
}, 200, { ... }],
"Code": 200
},
"Error": {
"Result": [],
"Code": 0
}
}
}

Please Note:

  • you can refer to the element of the array by using [array element number]
  • use dots instead of colons to refer to a nested JSON element

If you want to display the weather, you might want to have the following call: #Operation:weather Operation:Response:Result[0]:current.temp_c#

You can always check the structure of the received data (after performing the Operation) in the Developer Console of your browser.

#Operation:

GetClientInfoOperation:Response:

Result[0].data.result.

sc_agreement_info.agr_number#

_______

#Operation:

GetClientInfoOperation:Response:

Result[0].data.messages.text#

_______

#Operation:

CancelAllTimeslotsOperation:

Error:Result#

Route

Current page route (URL)

  • #Route:fullPath# - absolute path
  • #Route:path# - relative path
  • #Route:query:appid# - Application ID
  • #Route:query:screenid# - Screen ID
  • #Route:query:os# - OS the application was launched on операционная система (ios / android). Если не указано, будет определена автоматически
  • #Route:query:objid# - current Object ID
  • #Route:query:ref# - referrer. Possible options:
    • ref=PWA - the Application was launched from the Home Screen
    • ref=vcard - the Application was launched from the contacts 
    • ref=sms
    • ref=email
  • #Route:query:*customParameter*# - custom parameters that could be passed from the external systems. Example: paymentSuccess=1
{
"fullPath": "/?appid=57&screenid=131&os=ios&objid=256870&ref=PWA&result=1",
"path": "/",
"query": {
"appid": "57",
"screenid": "131",
"os": "ios",
"objid": "256870",
"ref": "PWA",
"paymentSuccess": "1"
},
"params": {}
}
}


Was it useful?