Introduction
In XTM Cloud, you can create custom fields for projects. These fields can be completed during project creation. The fields are available for use in the advanced search screen. Custom fields in XTM Cloud are useful if you would like to pass data, for example, during project creation, but there is no appropriate default field available in XTM Cloud.
Guidelines on custom fields for internal use
As a user with the Administrator role, go to Configuration → Data → Custom fields → Project custom fields, and Add a new custom field.
Complete the custom field creation form by specifying:
Field name,
Field type:
Checkbox,
Date,
Dropdown → enter the list of values that that you want to be selectable for that field,
Multiple selection → enter the list of values that that you want to be selectable for that field,
Number,
Text field.
Select Active,
Decide whether or not the custom field’s presence should be Obligatory for projects,
Optional: select Custom MT if the custom field is to be available in your customized machine translation engine,
If you selected either Dropdown or Multiple selection as Field type, enter Field values.
Finally, click the Save button.
Your custom field is now added to the list and is active under the Custom fields table.
Next time you create a project, a new section will be available and you will be able to use your defined project custom fields in the Custom fields section.
Once the project has been created, the selected custom fields are visible in the project editor (General info → Custom fields).
Project columns
In Projects → Project list, expand the Columns dropdown. You can select particular custom fields so that they are displayed as columns, and then sort by them.
Guidelines on custom fields for subcontractors (LSPs)
You can freely modify visibility rights for your custom fields for both your internal linguists and subcontractors (LSP) (again, administrative privileges required!) in Configuration → Settings → Translation → Workflow and access → Linguist metadata access → Access to custom fields.
Define Linguist custom fields access → In this field, select custom fields which your internal linguists will be able see in a project.
Define LSP custom fields access → In this field, select custom fields from which you will be able to set up custom fields for individual subcontractors (LSPs), who will be able see them in a project.
Once you set up the Define LSP custom fields access field, you might want to set up the selected custom fields for individual subcontractors (LSPs), who will be able to see them in a project. To do this, go to Users → LSPs → (select a relevant LSP) → Access rights → Custom fields.
In the Access to custom fields field, you have three options:
Yes, LSP specific → It allows for specifying custom fields that this LSP will be able to see in a project.
System default → The LSP will be able to see custom fields which are specified in Configuration → Settings → Translation → Workflow and access → Linguist metadata access → Define LSP custom fields access.
No → It disables custom fields for that LSP.
In the Custom fields field (if Yes, LSP specific option was selected, in the Access to custom fields field), select custom fields that the LSP will be able to see in a project.
Next time you create a subcontracted project, use your defined project custom fields in the Custom fields section. On the LSP side, the custom fields are visible in the project editor (General info → Custom fields).
As you can see, there is a suffix with the client name of the contractor, that is attached to the custom field name, indicating its origin.
Show contractors custom fields
Subcontractors have the possibility to see all the custom fields coming from the contractor, that have been passed over to a subcontractor, within the framework of a subcontracted project, at least once and which the LSP is able to see in that project. To do so, the LSP must enable the Show contractors custom fields option in Configuration → Data → Custom fields → Project custom fields → Show contractors custom fields. The contractor’s custom fields are greyed out and uneditable.
