Smarter by Design.Simpler for Business
ags profiles
ags profiles is the command group that collects the records that determine the appearance and the language of the access pages. It does not have its own action; it consists of two subcommands.
| Subcommand | What it manages | The panel screen |
|---|---|---|
ags profiles page-templates | The appearance of the access pages: the title, the logo, the color, the background, the footer | Page Templates |
ags profiles dictionaries | The multilingual dictionaries: the languages supported and the translation entries | Dictionaries (Multilingual) |
Both records are used by being bound to the gateway:
admin@TR7LBWAF01> ags gateway update id <vService> --pageTemplate <template> --dictionary <dictionary>
admin@TR7LBWAF01>
ags profiles page-templates
It defines the appearance of the access pages. Its only required field is the name of the template; all of the appearance settings come with their default values.
admin@TR7LBWAF01> ags profiles page-templates list # list all of them
admin@TR7LBWAF01> ags profiles page-templates show <id> # show one
admin@TR7LBWAF01> ags profiles page-templates add name <name> … # new template
admin@TR7LBWAF01> ags profiles page-templates update id <id> … # change
admin@TR7LBWAF01> ags profiles page-templates delete <id> # delete
admin@TR7LBWAF01>
The required field
| Order | Field | Status | Value |
|---|---|---|---|
| 1 | name | Required | The name of the template |
The appearance settings
| Field | Default | Value |
|---|---|---|
--pageTitle.type · --pageTitle.text | The type universal | The page title that appears on the browser tab |
--pageFavicon | — | The tab icon |
--darkModeSupport | false | The dark mode support |
--brandColor | — | The corporate color |
--headerLogo | — | The logo in the upper section |
--headerContent.type · --headerContent.text | The type universal | The upper section text |
--footerEnabled | true | The showing of the footer section |
--footerLogo | — | Only while the footer is on; the logo in the lower section |
--footerContent.type · --footerContent.text | The type universal | The footer text |
--backgroundImage | — | The background image |
--backgroundOpacity | 0.3 | Only when a background image is given; the transparency of the image |
The title and text fields use the same multilingual pattern as the form texts: first .type, then for universal .text, or for localized .key.
admin@TR7LBWAF01> ags profiles page-templates add name corporate-template \
--pageTitle.type universal --pageTitle.text "Corporate Access" \
--brandColor "#2563eb" --darkModeSupport true \
--footerContent.type universal --footerContent.text "The Information Technology Department"
admin@TR7LBWAF01>
ags profiles dictionaries
It keeps the translations of the texts on the access pages. When the texts are written with the localized type on a page bound to the dictionary, their correspondences are resolved from here.
admin@TR7LBWAF01> ags profiles dictionaries list # list all of them
admin@TR7LBWAF01> ags profiles dictionaries show <id> # show one
admin@TR7LBWAF01> ags profiles dictionaries add name <name> … # new dictionary
admin@TR7LBWAF01> ags profiles dictionaries update id <id> … # change
admin@TR7LBWAF01> ags profiles dictionaries delete <id> # delete
admin@TR7LBWAF01>
The required field
| Order | Field | Status | Value |
|---|---|---|---|
| 1 | name | Required | The name of the dictionary |
The languages and the translations
| Field | Default | Value |
|---|---|---|
--supportedLanguages.0 | en | The languages that the dictionary supports; every language is written with its own index, as a language code |
--translations.0.key | — | The translation key; this key is used with the localized type on the pages |
--translations.0.language | — | The language of the entry |
--translations.0.value | — | The text of the entry |
Every translation row consists of a key, a language and a text. The correspondences of the same key in different languages are written as separate rows.
admin@TR7LBWAF01> ags profiles dictionaries add name corporate-dictionary \
--supportedLanguages.0 tr --supportedLanguages.1 en \
--translations.0.key login_title --translations.0.language tr --translations.0.value "Kurumsal Giriş" \
--translations.1.key login_title --translations.1.language en --translations.1.value "Corporate Sign In"
admin@TR7LBWAF01>
admin@TR7LBWAF01> ags profiles dictionaries update id <kimlik> \
--translations.2.key login_button --translations.2.language tr --translations.2.value "Giriş yap"
admin@TR7LBWAF01> ags profiles dictionaries update id <id> --translations.delete # remove all the translations
admin@TR7LBWAF01>
Things to Know
- Both records are bound to the gateway. The template is bound with the
--pageTemplatefield and the dictionary with the--dictionaryfield; as long as they are not bound, they have no effect on the appearance. - The keys must match the page texts. The key in the dictionary must be exactly the same as the key written with the
localizedtype in the form or template text. - The languages are written as codes. The languages supported are given with language codes such as
tranden; if no language is written, the dictionary opens withen. - The color and the values with spaces require quotation marks. The corporate color and the texts with more than one word are written with double quotation marks.
