| Note | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
When adding display names for a new language, a new entry (record) must be added for that language with the correct language ID (LANG_ID column) in the LANGUAGEMASTER table in the Canvas schema. For the changes to get applied, users must choose their primary language as the preferred language in the functional application, Modelhouse. A sample entry in the LANGUAGEMASTER table for the Arabic language is shown for reference:
Adding an entry for the new language in the LANGUAGEMASTER table is mandatory, without which that language will not appear in the functional application (e.g. Preferences tab in Modelhouse). |
To manage the display names of forms, perform the following steps.
Let's assume that the form with the Form Id, FORM_ACCOUNT_TYPE has CUSTOMER_INFORMATION has been created using Canvas Studio.
- Open the form in the Form Designer in Canvas Studio.
.png?version=1&modificationDate=1587638886806&cacheVersion=1&api=v2&height=400)
- Click a field on the form. For instance, click the Title
Text Field 
form item. Click the Plain label
icon.
.png?version=1&modificationDate=1587638984606&cacheVersion=1&api=v2&height=400)
By default, the name of the form item appears in the Plain label field.
In the following screen shot, the word, 'NAME' has been assigned as the text of Plain Label. .png?version=1&modificationDate=1587639072468&cacheVersion=1&api=v2&height=400)
Info If language specific labels have to be rendered, then the Display Name Key has to be used instead of the Plain label. If Plain label is present for a form item, it takes more precedence. To enable Add labels, remove the default or assigned text from the Plain label field.
.png?version=1&modificationDate=1587639167416&cacheVersion=1&api=v2&height=400)
- After removing the name from the field of Plain label, click Display Name Key
icon.
.png?version=1&modificationDate=1587639248173&cacheVersion=1&api=v2&height=400)
A text field appears. Enter the display name key in the text field and press Enter. For instance, the word TITLE can NAME can be used.
Info In the text field of Display Name Key, blank spaces should not be used. Symbols like hyphen (-) and underscore (_) can be used.
.png?version=1&modificationDate=1587639301788&cacheVersion=1&api=v2&height=400)
Once you have applied changes with Display Name Key to all the form items that you have used in your form, proceed to click Add Labels
.png?version=1&modificationDate=1580799415645&cacheVersion=1&api=v2)
icon.Note The Add labels screen will get enabled, if there is at least one form item with a display name key.
.png?version=1&modificationDate=1587639373352&cacheVersion=1&api=v2&height=400)
The Resource Bundle Entries Page appears.
.png?version=1&modificationDate=1587639415972&cacheVersion=1&api=v2&height=400)
Info The Bundle Name is taken from the form’s default bundle name. You can change the default bundle name by using the Form ribbon in the Form Designer.
The Language drop-down box allows you to choose your preferred language. For new languages, refer the Prerequisites mentioned above in the procedure.- Select your desired Language from the Language drop-down box.
%20-%203.png?version=1&modificationDate=1587640259880&cacheVersion=1&api=v2&height=400)
- In the Form Item Labels tab, click the Phrase for fields and enter the display names. You can choose any of the fields, for which you wish to modify the display names. The following screen shot showcases the new display names.
.png?version=1&modificationDate=1587639471026&cacheVersion=1&api=v2&height=400)
- After changing the display names for the form fields, click Save.
%20-%202.png?version=1&modificationDate=1587639602916&cacheVersion=1&api=v2&height=400)
The Resource Bundle data gets saved successfully.
- Click OK.
- Click Save
icon to save the form.
%20-%202.png?version=1&modificationDate=1587639664006&cacheVersion=1&api=v2&height=400)
After you save the form, a successful confirmation message appears, with a reference number.
.png?version=1&modificationDate=1587639693706&cacheVersion=1&api=v2)
Let's assume that the form is already mapped to the CUSTOMER DASHBOARD workspace widget, Account Holders' Information, which, in turn, is mapped to the workspace, titled as Form in the functional application (e.g. Modelhouse). The following screen shot serves as a good illustration of the output in the functional application, Modelhouse.
.png?version=1&modificationDate=1587639855868&cacheVersion=1&api=v2&width=787)
The following table illustrates the different form types, which possess the Plain label configuration. Certain form types listed in the table do not possess the Plain label functionality.
...