SUMMARY
Use this guide to add translations for stop causes so operators see stop categories and stop reasons in their preferred language. Customer-specific translations can be managed directly within the stop cause configuration.
WHEN TO USE THIS
Use this guide if:
- You have operators who use Factbird in different languages.
- You want stop causes to appear in each operator's local language.
- You are configuring multilingual production lines.
PREREQUISITES
Before starting:
- You have permission to manage stop causes.
- Stop categories and stop causes have already been created.
- The required language is enabled in your Factbird environment.
STEPS
- Open the production line you want to configure.
- Navigate to the Stop Causes configuration.
- Select the stop cause you want to translate.
- Open the Translations section for the stop cause.
- Add the translated name for each required language.
- Repeat the process for any additional stop causes.
- Save your changes.
EXPECTED RESULT
After completing these steps:
- Stop causes are displayed in the translated language for users working in that language.
- Operators continue to register downtime using the same stop causes, regardless of the language displayed.
TROUBLESHOOTING
Issue: A translation is not displayed.
Try: Verify that a translation has been added for the selected language.
Try: Confirm that the user's language matches the translated language.
Issue: A system label is translated incorrectly.
Try: Customer-specific stop cause translations can be edited directly.
Try: For incorrect system translations, submit a support request with the language, a screenshot, and your suggested wording.
STILL NEED HELP?
Contact Support and include:
- The language you are using.
- The name of the stop cause.
- A screenshot of the stop cause configuration.
- A screenshot showing the incorrect translation, if applicable.
RELATED ARTICLES