...
| Info |
|---|
Some hashtags work for app users or for platform users (admin part) only. Please, pay attention to relevant notes to the sections below. |
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:
...
Resulting in the following looped data:
EVENT
Event hashtags are available in Triggers' operations only.
#Event: id# - Event id
#Event:Value:*EventFiledName*# -data from specified field 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*# - 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.
...
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 URL - 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). 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 parameters that can be passed from external systems. Example: paymentSuccess=1.
...