Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform
What are the login form, page template and dictionary; what determines how AGS pages look?
Short answer
The pages AGS presents to the user are determined by three profiles. The Login Forms profile defines the fields of the login form and is selected in the Form step in the access flow. The Page Templates profile determines the common appearance of the pages (page title, favicon, logo, brand color, footer, background, dark mode). The Dictionaries (Multilingual) profile holds the languages of the pages and the translation texts. The template and the dictionary are selected in the Page Template and Dictionary fields in the AGS settings of the vService; each vService uses one template and one dictionary. A new AGS-enabled vService comes with Default Page Template and Default Dictionary, and its flow starts with the built-in Basic Login form.
How Does It Work?
- When the access flow reaches a Form step, the form selected in the Form Profile field of the step is shown to the user. The entered values are read in the following steps with the AGS User Input variable; the values marked with Assign to User Fields are written to the user fields in the session.
- The page is presented with the logo, color, title, footer and background settings of the template selected for the vService; the login form, MFA, error and information pages carry the same appearance.
- In every text field in the form and the template, where the text comes from is selected:
| Text type | Where the text comes from |
|---|---|
| Static | The fixed text written in the field; it can contain a Smart Variable |
| Dictionary | The translation defined with the same Translation Key in the dictionary selected for the vService |
| Default | TR7's built-in ten-language text |
| No Text | No text is shown |
Comparison
| Login Forms | Page Templates | Dictionaries (Multilingual) | |
|---|---|---|---|
| What it determines | The fields, buttons, validation rules and conditional visibility in the form | The frame of the pages: title, favicon, logo, brand color, footer, background, dark mode | The page languages and the translations per key |
| Where it is defined | AGS → Pages & Language → Login Forms | AGS → Pages & Language → Page Templates | AGS → Pages & Language → Dictionaries (Multilingual) |
| Where it is selected | Every Form step in the Flowchart | The Page Template field of the vService | The Dictionary field of the vService |
| Built-in records | Basic Login, Email Login | Default Page Template, Minimal Page Template | Default Dictionary (ten languages), English Only |
AGS Pages in TR7
- The profiles are defined device-wide and are shared by multiple vServices; the corporate appearance is updated in a single template.
- The template and the dictionary are selected in the Appearance section of the General Settings window on the Flowchart tab of the AGS-enabled vService, or in the Presentation & language row of the AGS Management tab.
- The built-in forms, templates and dictionaries do not appear in the lists of their own screens and are not edited or deleted; they are selected directly in the selectors. The new template form opens filled in with the Default Page Template settings.
- Language details: How does multilingual support work on AGS pages?
Common Misconceptions
- "The fields of the login form are edited in the template." The template determines only the frame of the page; the fields are defined in the Login Forms profile.
- "Selecting a dictionary translates the texts on the page automatically." The dictionary resolves keys only for texts of the Dictionary type; Static text stays the same in every language.
- "I can change the built-in Basic Login form or the Default Page Template." Built-in records are not edited; a new profile is created on the same screen and selected in the flow or in the vService setting.
- "Each form step can use a different template." The template is selected at the vService level; all the AGS pages of the vService use the same template.
How it is done in the documentation
