Localization of Messages
Is there any reason the action messages are not localized?
The only way to accomplish localized messages is to make all your action methods 'ProcessContext.StageCaption' and then localize your stage captions. That limits us to naming our messages and stages the same.
Perhaps I'm looking at it the wrong way and there is a method to accomplish what I'm trying to do.
Otherwise I'll be requesting a feature change.
Comments
-
Action messages are defined as expressions, have you tried localising them at this point?
0 -
But surely the message cannot be localised to the user's Locale in this way? That can only ever be done by an internal mechanism. All you could ever do is present a message tailored to the previous user's Locale, as that is all you can know when the Action occurs.
Stu White wrote:
Action messages are defined as expressions, have you tried localising them at this point?
0 -
Correct, once the action message has been set, then this is how it will be displayed to the user regardless of locale of their browser.
0 -
Yea, I considered creaeting a class library that switched on ProcessContext.UserLocale then set the language specific message. It's just extra work that I figured the localization feature of Metastorm would handle. As Jerome has said though, this only guarantees that the user who took the action has a localized message. Not the user who eventually opens the todo task. For the most part this shouldn't affect us, but something to be weary of.
I'm doing a lot of out of the box things with Metastorm so perhaps I'll post some solutions for those that find my various questions.
0
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 152 General Questions
- 148 Thrust Services
- 57 Developer Hackathon
- 37 Thrust Studio
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 32 eDOCS
- 190 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 9 XM Fax
- Follow Categories