In a Nutshell
In the Smartforms and Feedback app, it is possible to export smartforms in XML format, have them translated, and reupload them. When the default language is defined for the smartform instance, the translated smartform template can then be used in the mobile application by using a business rule to create a smartform instance from the translated smartform template.
Before We Begin
Please note the following:
|1||The language is defined when you create a new Smartform Template (i.e. English).|
|2||Additional languages for the same smartform template can be created with external translation services, and are stored / visible under the same smartform template. Any text, e.g. descriptions (labels), dropdown lists can also be translated.|
|3||If an update is done on the smartform (in the default language), the export/import process of the translations will also need to be repeated.|
|4||Smartform instances of translated templates can be automatically created by business rule (see Business Rule section below) .|
|5||Smartform instances can be created by the planner in the Workforce Management application. However, the language of the instance cannot currently be set here. This is where a business rule could be used to match the business partner language to a translated template language.|
|6||Smartform instances can created directly from the mobile application by completing a ‘Create Smartform’ action and selecting the translated smartform template.|
Smartform Translation Workflow
Templates can be exported in XML format by completing the following steps:
- Select the smartform template you want to export for translation.
- Change the status of the smartform to
- Select the export option frorm the ⋮ menu.
- Select the language/s for which you plan on providing translations.
- The templates will then be downloaded in XML format.
Import Translated Templates
|ATTENTION: Please note than when importing a translated template, the zipped file must contain ONLY the translated file and no additional folders.|
After translation has been completed for the additional language/s, you can then import the template/s by completing the following steps:
- Select the smartform for which you have exported the template in additional languages. Please Note that the template must be in
- From the ⋮ menu, select the
- Select or drag and drop the file. Please note that the file must be in .zip format:
- Select the
Importoption. When successful, the application will display a
Translations Importedmessage in the bottom-left corner.
- From the ⋮ menu select the
- Select the translated template you would like to view:
Business Rule to Trigger Translated smartform instance
After successfully importing the translated templates in Smartforms and Feedback > Designer, a business rule can then be created which would use the transalted smartform template associated with the business partner language and create a new smartform instance from it.
Alternatively, you could create a smartform instance from the translated template from the mobile device if the smartform template is available in the business partner language (see following section).
Business Rules can be created in Admin > Company > Business Rules.
Note: You must have
SUPER USERprivileges to access the Admin application and create and manage business rules.
Business Rule Example
To begin, let's take a look at the following example business rule. Note that the default language of the smartform instance has to be defined in Designer in order for the following business rule to work.
|Action||In this example, we’re using
|Execution count||Here, you can enter
|Category Name||Here you can enter the name of the category you wish to associate with the smartform instance created by the business rule. This can then be used to filter smartform instances.|
|Smartform template Name||Required. Here you will enter the name of the smartform template from which the instance will be created.|
|smartform template Tag||This is another optional field. Tags are used to filter smartform instances.|
|Smartform template Version||By leaving blank, the application will use the latest version. If necessary, you can also specify which version of the smartform template you would like to use.|
|Mandatory||Yes or No. For this business rule, we will need to have
|Reference Object ID||Required. This is where we will enter the object for which the business rule will be triggered. In this case, we will enter
|Reference Object Type||Required. As we entered
|Responsible Person ID||Required. Here we will enter the recipient of the business rule. In this case, it will be
|Description||This description will display in the Business Rules view. If you have multiple business rules, this may make it easier to manage them.|
|Language||This is the crux of the business rule example. Here will enter
Use Translated Template to Create Smartform Instance
Finally, we can have a look at how we can create a smartform instance from a translated template in the mobile application.
Note: If a translated smartform instance is created by business rule, it will be attached to the activity.
- From the mobile application, select the ⋮ menu and select the
- Select the translated template you wish to use:
- Select the
- Select the language of the template for which you wish to create a new smartform instance:
- Save the changes:
- You can now view and complete the translated smartform instance:
|1||It is possible for the field service user to change the language on his mobile device. The final saved (closed) instance is only saved in the specific language at the moment the smartform instance is saved.|
|2||The checkout report should only be run in the language of the instance (so the header / footer of the report (e.g. “date & time” is in the same language as the smartform instance – displayed labels & content as added by field service).|