I have been facing an issue since I started working with Appian related to the behavior of Process Model labels when using multiple languages. Currently, Appian requires me to manually replicate the same labels across different languages, which is not efficient nor logical in my development environment. Although I understand that a large portion of the community primarily uses one language (English), my team operates in a multilingual setting, where developers have different language preferences.
Given this context, it becomes necessary for me to enter the same label in another language to maintain clarity and understanding among my team members. However, this redundancy could easily be avoided if Appian implemented a feature allowing us to persist labels across multiple languages. A simple checkbox option like "use same labels for multiple languages" when creating a process model would greatly enhance our workflow by ensuring consistency and saving time.
Moreover, the current differentiation of labels based on language within the nodes seems unnecessary, as these nodes are typically only seen by developers (who should at least comprehend a basic level of English). Ideally, Appian should provide an option to maintain uniformity in labeling, regardless of the language preference of individual developers, while allowing those who read English to function efficiently without duplicating effort.
Additionally, I would like to understand the rationale behind Appian's decision to implement this language differentiation. What is the intended benefit of having separate labels for each language? Particularly for node labels where this distinction seems unnecessary.
Thank you all!
Discussion posts and replies are publicly visible
I’ve had similar issues with multilingual teams in Appian. Having to replicate labels across languages slows things down and doesn’t add much value, especially since most developers can read at least some English. It would be really helpful if Appian added a “use same labels for multiple languages” option to cut out the redundancy. Do you know if there’s any workaround for this right now?
There is more to it.
When a developer with language A creates a user input task, a user with language B will not see the assigned interface.
I make my developers all work in the same language, and strictly review language related configuration and translation.