Your users can only change the language of the application if you use edoc workplace in your organization. If you use the d.3 mailbox functionality or the Tasks feature in d.velop documents (d.3one), the language settings cannot be changed.
With edoc language service, you and your users can use the edoc applications in different languages.
You can select your preferred language in the personal settings. You can also translate e.g. organization-specific fields and columns in the languages provided in edoc language service.
All standard fields are automatically displayed in the respective language. As you can also change the texts of standard fields, these fields are treated as organization-specific fields in edoc language service and you can also translate the updated entries.
Each newly created or changed field in your application is assigned an ID (unique translation key). The ID is used to assign the translations to the corresponding field in the application.
Structure of the ID for translations (translation key)
Newly added or changed fields and columns are assigned an ID (unique translation key). The ID is company-specific and is displayed in edoc language service. The ID can be used to assign translations to the correct field or column in the application.
For example, the ID has the following pattern for a field in edoc invoice:
invoice-service.invoice_headers.invoiceType_edoc_custom
-
invoice-service: The sample <product>-<service> identifies the product. In this case it is edoc invoice.
-
invoice_headers: The sample <product>_<detail functionality> identifies where the text is located within the product. In this example, this is the function around the header fields.
-
invoiceType_edoc_custom: In this example, the sample <detail1>_<company>_custom contains the column ID (invoiceType) from the capture form for the header fields, the company (edoc) and the suffix custom, which identifies the entry as an individual field or individual column (organization-specific).
Find out more