General: Custom field names
Answer: If the name of a field in TOPdesk does not match with your intended use of the field, you can register a request on the TOPdesk Innovation Platform to make the name of the field adjustable. That way we get a clear overview of which field names are often adjusted, allowing us to prioritize translation requests.
Answer: If the name of a field in TOPdesk does not match with your intended use of the field, you can register a request on the TOPdesk Innovation Platform to make the name of the field adjustable. That way we get a clear overview of which field names are often adjusted, allowing us to prioritize translation requests. SaaS customers: On TOPdesk SaaS it is only possible to change the names of fields that can be found as an Adjustable Names option within the environment. You can find the adjustable names in the settings pages of TOPdesk. Attention: adjustable names for Extra 1 and Extra 2 fields are not editable at once (grayed out) if they have only just been activated. Closing the settings tab and going to the settings again will solve this. On-Premises customers: TOPdesk versions newer than 9.04.023: It is no longer possible to change fields other than those that can be found in the Adjustable Names options within the environment, just like SaaS. TOPdesk versions older than 9.04.023: You can use our DIY manual on Scribd about how to adjust field names by creating a bespoke work to edit installation files, also found in the PDF file attached to this knowledge item. Please note, that we cannot support bespoke work created by anybody other than our own bespoke work department. The following is applicable for the resource files mentioned in the Scribd article for TOPdesk 6: ⒈resource (.properties) files that use special characters need to apply the following rules: ◦The file needs to be UTF-8 encoded (Not UTF-8 with BOM). ◦Special characters will have to be encoded with JavaScript encoding (https://r12a.github.io/apps/conversion/). ⒉The standard recourse files are: ◦UTF-8 with BOM encoding. ◦Special characters are decimal NRC's (https://r12a.github.io/apps/conversion/) encoded. ⒊It is advisable to add no more then the changed resources into the bespoke work. Note: we strongly advise to not add a period (.) to custom names. These can lead to broken links ([UNRESOLVED_FIELD_PATH]) with the field when used in email actions. When saving the file in an application, the encoding can be changed. Check if the file has the right encoding according to the explanation above, before uploading.