Advanced tokens
The following tokens provide advanced functionality that you can use in templates and formulas. Platform replaces the token with the content described below:
| Token | Will be replaced with ... |
|---|---|
{!#TODAY}
|
Today's date in the user-selected format |
{#SESSION_ID}
|
User's session ID |
{#PAGE_ID}
|
ID of current page |
{!#HOST_NAME}
|
Host name of the server running the Platform instance |
{!#LINK.objName}
|
Link to the object's view page assigned to current user |
{!#LINK.objName#id}
|
ID of the object's view page assigned to current user |
{!#LINK.objName#12345}
|
URL to the object's page specified by the original ID (only available for view, new record, and edit pages and only if more than one page of each type exists (e.g. at least two view pages)) |
{!#LINK.objName#generic}
|
URL to the object's generic page assigned to current user |
{!#LINK.objName#template}
|
URL to the templates page |
{!#LINK.objName#import}
|
URL to the object's import page |
{!#LINK.objName#search}
|
URL to the object's search page |
{!#LINK.123456#tab}
|
URL to the generic or web tab specified by the original ID |
{!#OBJ_ID.objName}
|
Object definition ID for the specified object |
{!#CURR_USER.fieldName}
|
Value of the specified fieldName for the currently logged in user |
{!#CURR_CUSTM.fieldName}
|
Value of the specified fieldName for the current customer |
{!#SETTINGS.fieldName}
|
Value of the specified fieldName for Company-wide Settings |
{!#ISV_VALUE.fieldName}
|
ISV customers only: Value of the specified fieldName for an ISV account. The fields must be marked as Make this field available for related ISV customers, see Using the ISV Partner application |
{!#PORTAL. 688851.#id}
|
ID of the portal with the specified original ID |
{!#PORTAL.688851.705908#id}
|
ID of the portal page with the specified original ID |
{!#PORTAL.688851.705908#url}
|
URL of the portal page with the specified original ID. This token can be used in the user interface. |
{!#PORTAL.688851.705908#link}
|
Link to the portal page with the specified original ID |
{!#PORTAL.688851.705908#emailUrl
}
|
URL of the portal page with the specified original ID. This token can be used in emails. |
{!#PORTAL.688851.logout#url}
|
URL to the logout page for the portal with the specified original ID |
{!#PORTAL.688851.logout#link}
|
Link to the logout page for the portal with specified original ID |
{!#PORTAL.688851.emailUrl}
|
URL to Portal's main page which is safe to use in emails |
{!#REPORT.123456#body}
|
The HTML body of a text-based report with the specified original ID |
{!#REPORT.123456#url}
|
The resource URL that generates the report with the specified
original ID. Note: This is not available for tabular
reports. |
{!#REPORT.123456#body? fieldName=fieldValue}
|
The HTML body of a text-based report filtered by a field value. The
fieldName parameter specifies the integration name of a field
by which to filter, fieldValue specifies the value on which to
filter, such as country=USA. |
{!#FILTER}
|
HTML with content of current report filters. For template-based reports only. |
{!#CURR_VISIT.name}
|
Display name of the current portal user |
{!#CURR_VISIT.id}
|
ID of the current portal user |
{!#CURR_VISIT.loginName}
|
Login name of the current portal user |
{!#UID}
|
Unique string ID of objects imported from an external database or an OpenEdge Service. |
{!#CP_TOKEN}
|
A client principal token used to access a JSDO Invoke method
on an OpenEdge Data Object from Platform Object script. This token can be used in an
HTTP header under the header name X-OE-CLIENT-CONTEXT-ID. |
{! #CSRF_TOKEN}
|
Platform servlets are now guarded with CSRF tokens and thus making the platform more secure. Any custom code that directly hits a Platform servlet with POST call requires CSRF token to be passed in the call. For details about CSRF, please refer https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF) |
{!name#ssolink#Okta_Saml}
|
This token generates the record view link for any SAML authenticated users. In this token, Note: Separate tokens are available for every SAML profile in the tenant.
|
Tokens for Job History Template Helper
The following tokens are available under Job History template helper. The application developer can use these tokens as preferred.
| Token | Will be replaced with ... |
|---|---|
|
|
The type of the background job. For example: Import job, Generate Report, List View Export, Mass-Update etc. |
|
|
The name of the object on which the job is initiated. For example: Users |
|
|
The details of the job. For example: Export List View : "All Users" [xls] on USER |
|
|
The status of the job. For example: Complete or Error |
|
|
The URL of the generated job file available for download. |
|
|
The URL of the error file for failed jobs. |
|
|
The name of the user who initiated the job. |
|
|
The time of job when started. |
|
{ |
The time of job when started in ISO format. |
|
|
The time of job when finished. |
|
|
The time of job when finished in ISO format. |
|
|
The duration of the completed/failed job. |
|
|
The record level details of the job performed. For example: Exported 10000 of 10000 total records |
