Hashtags

Updated 1 day ago by Mobsted Support V

Mobsted hashtags is the way to access or reference 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, and when sending messages to the Objects.

Hashtags allow you to view and access data on:

Example

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

Detailed Example

In our Objects database we have Object Alex with this phone number and email provided. We want to send Message to Alex.

In the Message Window 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 Variables Accessible though the Hashtags

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: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)
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: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#.

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

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. 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)

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

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

Filter

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

Repeat

#Repeat:backend_ BackendColumnName#

#Repeat:objects_ ObjectColumnName#

Current event (is available after running the Event Trigger)

#CurrentEvent: BackendColumnName#

#CurrentEvent:Value: *DynamicBackendColumnName InTheValueField*#

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.

Variables

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

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:

After running the operation you might get the following data:

{
"Response": {
"Result": [{
"error": "",
"value": "ok"
}, 200, {
"0": "HTTP\/1.1 200 OK",
"Server": "nginx\/1.15.5",
"Date": "Wed, 26 Dec 2018 06:23:36 GMT",
"Content-Type": "application\/json; charset=utf-8",
"Transfer-Encoding": "chunked",
"Connection": "keep-alive",
"Vary": "Accept-Encoding",
"X-Powered-By": "PHP\/7.2.10",
"Set-Cookie": ["XDEBUG_SESSION=PHPSTORM; expires=Wed, 26-Dec-2018 07:23:35 GMT; Max-Age=3600; path=\/", "PHPSESSID=39ed46b7c61aab53a8316460635a317a; path=\/"],
"Expires": "Thu, 19 Nov 1981 08:52:00 GMT",
"Cache-Control": "no-store, no-cache, must-revalidate",
"Pragma": "no-cache",
"Access-Control-Allow-Origin": "*",
"Access-Control-Allow-Methods": "GET, POST, PUT, DELETE, OPTIONS",
"Access-Control-Allow-Headers": "DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range,Authorization",
"Access-Control-Expose-Headers": "Content-Length,Content-Range"
}],
"Code": 200
},
"Error": {
"Result": [],
"Code": 0
}
}

Please Note:

  • an array might me the value of one of the elements, and 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 / use data from the Set-Cookie section (item with index 1), then you need to use the following hashtag #Operation:OperationName: Response:Result[2].Set-Cookie[1]#

If you want to display / use data from the Response section (Code element), then you need to use the following hashtag #Operation:OperationName: Response:Code#

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#

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

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


Was it useful?