Predefined session variables
Introduction
Each application template has a set of predefined session variables. These variables are visible during the application design stage. The application designer cannot edit or delete these variables. The purpose of these variables is to carry basic information collected while the end user fills out the application. This data is automatically populated by the application displaying the form and saved in the repository.
List of system variables
Below the system variables and their purpose are listed:
_abandonTime- time of abandoning the application_channel- the channel through which the user fills out the application (web, mobile)_channel_Description- channel description (desktop: web, mobile: mobile, native app: APP_Mobile)_currentPageId- number of the currently displayed page_currentPageMid- mid of the displayed page_cvc- parameter displaying the application in another view, allows placing fields additionally next to the application_domain- domain of the running application (only the host name, e.g.form.consdata.com)_finishTime- time the user submitted the application_finishTimeAfterPayment- time the user submitted the application after payment_formId- name of the application_formInstanceNumber- application number_ip- user's IP address_operatingSystem- name of the operating system (according to the documentation https://github.com/lancedikson/bowser/blob/1.7.3/README.md - for GWT a simplified OS detection mechanism is used)_paymentResult- variable indicates whether the payment succeeded (used for payment handling functionality managed by external services)_startTime- time the user started filling out the application_userAgent- name of the client application_visitedPages- sequence of visited pages___userEmail___- value of the email address field of the user specified in the contact section on the application properties page_externalFormContextId- external identifier of the application context (case identifier)_businessFormIdentifier- identifier displayed on the application view, by default the application number_SESSIONKEY- session identifier_browserName- name of the web browser_cmisObjectId- stores the identifier that allows retrieving the application_internalAuthenticationMethod- authentication method used in the given activity_internalAuthenticationPhoneNumber- phone number to which the SMS was sent / phone number with the authentication app (OTP-SMS, OTP-PRINTED, MOBILE-APPLICATION)_seller- identifier of the seller directing to the application in the mobile app
Last updated
Was this helpful?
