...
Hashtags can be created manually or automatically via Hashtag generator function in Constructor.
...
1. How and Where its Engaged
Every where you see the sign # - you can call the generator and find a piece of data you need.
2. Which Data Points are Available
Hashtag generator works for the below parts and functions of the platform:
Application
Backendname
Event
LastEvent (last event created on app user action)
Filter
Object
API Operation
Screen
System
Tenant
Variable
- Lists of Tables (Custom Data Tables)
Info |
---|
When entering Hashtags manually make sure the text contains no spaces otherwise they won't work. |
...
Info |
---|
Some hashtags work for app users or for platform users (admin part) only. Please, pay attention to relevant notes to the sections below. |
3. Hashtags Usage Examples
...
User Interface
Hashtags are used to display, or execute upon, Object data from a needed column. Here is a sample of simply displaying data:
Constructor View - #Object:Name# | Application User View - resulting data pulled from Object's column "Name" |
API Providers
...
Hashtags are used to pass data into API call parameters, for example, #Backendname:city# in the sample below:
...
This is a sample of messaging block of the platform.
Custom JS
...
Hashtags are used to pass data into Custom JS code, for example to call a native Share link function, and track which objectID does most sharing you can add a hashtag into Custom JS, like in the sample below:
...
Anchor | ||||
---|---|---|---|---|
|
|
---|
...
|
---|
...
|
---|
...
|
---|
...
|
---|
...
|
---|
...
|
---|
...
|
---|
...
|
---|
...
|
---|
...
|
---|
...
|
---|
...
|
---|
...
|
---|
In this case the #Object:objid# will be pulled in by the JS function.
...
4. Available System
...
Wide Hashtags
We try to have this list up to date, however there is good chance there are more hashtag references available on the platform, as new ones are added often.
...
#Object:id# - object unique ID
#Object:PIN# - login PIN if PIN is set in user access settings
#Object:Phone# - object phone number
#Object:Email# - object email
#Object:CreateDate# - object creation date
#Object:LoginUrl# and #Object:InviteUrl# - personal short link to enter the app on behalf of the object. #Object:InviteUrl# is used for app distribution to new users
#Object:Enabled# - object Status, if 0 - the object will not be able to access the app (requires to make settings in Enabled column in Objects)
#Object:LastLogin# - last date the app was accessed by the object
#Object:InviteStatus# - status of an invite sent to the object
#Object:Timezone# - current time zone
#Object:AutomaticalTimezone# - set automatic time zone, can be ON=1 or OFF=0
#Object:LastModified# - last date when object's data was changed
#Object:*anyColumnName*#anyColumnName# - reference to any custom column created in Objects
#Object:FacebookChannel# - FB bot enabled=1, not enabeld=0
#Object:TelegramChannel# - Telegram bot enabled=1, not enabled=0
#Object:ViberChannel# - Viber bot enabled=1, not enabled=0
#Object:VKChannel# - VKbot enabled=1, not enabled=0
#Object:NotifyPush# - Chrome push enabled =1, not enabled =0
#Object:NotifyEmail# - Email push enabled =1, not enabled =0
#Object:NotifySMS# - SMS push enabled =1, not enabled =0
#Object:*anyColumnName123*#anyColumnName123# - reference to any custom column created in Objects.
...
Resulting in the following looped data:
EVENT
Event hashtags are available in Triggers' operations only.
#Event: id# - Event id
#Event:Value:*EventFiledName*# EventFiledName# -data from the specified field name in Event Value column
#Event:ActionName# - event action name.
LAST EVENT
LastEvent hashtag returns data from last event created on app user action.
...
#LastEvent:id# - Last Event id
#LastEvent:Value:*EventFiledName*#EventFiledName# - data from specified field in Event Value column
#LastEvent:ActionName# - Last Event action name.
API OPERATIONS
#Operation:OperationName: Response:Code# - HTTP status code after executing the operation
#Operation:OperationName: Response:Result[0].value# - data received as 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 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.
...
Example: you can ran an operation to check weather in London and recieve the following data:
...
|
---|
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.
...
This check requires having the API method as already set in your INTEGRATION section of Mobsted. The Weather example API method is available by default.
CURRENT PAGE ROUTE
Current page route (URL)
...
#Route:fullPath# - absolute path
...
LISTS OF TABLES (CUSTOM DATA TABLES)
The FULL general form of the hashtag to call on custom tables is the following:
#List:list_name:table_name:N:column_name#
Where: "List" is the initiation line telling the system to look into lists of tables data. "list_name" is the custom name you give to your custom list of tables "table_name" is your custom name of the needed table within the list "N" is the ID of the ROW within the table "column_name" is the custom name of a column |
---|
The full form returns to the exact data cell.
The List's hashtags can be used in it's partial form to pull in arrays of data from the table:
- #List:list_name:table_name# - returns the table in full, and is often used with ONE column tables
- #List:list_name:table_name:N# - returns the specified ROW from the table, with all the columns
You can also use a hashtag WITHIN a hashtag to make more dynamic data calls, as shown in the example below, taken from the Task Manager sample app (located in your account):
You can see that the hashtag used in the Constructor (marked Red) of the app, has this form (marked Green) -
Now, look into this hashtag - #List:languages:translation:3:#Backendname:Language##, open the Lists of Tables (marked Red), click down to Languages > Translations. You can see that the first part (in bold) of the hashtag fully repeats the route to the table.
Now - look at the second part of the hashtag #List:languages:translation:3:#Backendname:Language## ( in bold again). Each row stores how each piece of text in app is in every language. Then a column is requested using another hashtag, from a backend element's name, where use sets his own language. Note that in this case you user a double ## at the end to "close" both hashtags, just as with spreadsheet formulas.
CURRENT URL - ROUTE
Current page route (URL) will pull into the application any information located in the incoming/open/current URL. This is often used to pass data between applications without any complex integration.
#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). Will be detected automatically if not specified
#Route:query:objid# - current Object ID
#Route:query:ref# - referrer. Possible options:
ref=PWA - application was launched from Home Screen
ref=vcard - application was launched from Contacts
ref=sms
ref=email
#Route:query:*customParameter*# Custom_Parameter# - custom parameters that can be passed from external systems. Example: #Route:query:paymentSuccess=1.1#, or #Route:query:utm_referer# to read off the "objectid" info sent from the Custom JS example in Section 3 above.
Related articles
Related articles
...