# Localization functionality

**URL:** <https://forum.flowable.org/t/localization-functionality/1639>\
**Category:** Flowable Engine\
**Created:** [February 13, 2018, 3:07pm UTC](https://forum.flowable.org/t/localization-functionality/1639 "2018-02-13T15:07:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmitryfar](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/dmitryfar/32/477_2.png) [@dmitryfar](https://forum.flowable.org/u/dmitryfar)\
**Post date:** [February 13, 2018, 3:07pm UTC](https://forum.flowable.org/t/localization-functionality/1639/1 "2018-02-13T15:07:17Z")

</div>

Hi Core guys.

As I saw in code there is a localization functionality in the Engine via activiti extensions in BPMN.  
First thing: there is no any mention about it in docs. Sad 🙂  
Second: I think it is too hard to view, modify and mantain it in consistent state. If some day we (as organization) want to extend localizations and add one Lang more… we have to search all extensions for all elements and add localization.  
It is not humane 🙂  
For this reason I suppose I want to be able place in the deployment additional \*.properties resources. This resources may be used to translate all form properties names, task/process titles, and used in expressions like “${labels.usertasks.request-task-name}”.  
In this way is easy to copy one property file and replace translations.  
What do you think?

Thanks.

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [February 16, 2018, 12:24pm UTC](https://forum.flowable.org/t/localization-functionality/1639/2 "2018-02-16T12:24:43Z")

</div>

That sounds like a nice idea and easier to get an overview for sure. However do note that it does mean that new translations are tightly coupled to the deployment. So if you want to change something or simple fix a typo, it means a redeployment.

---

<div class="post-metadata">

**Author:** ![dmitryfar](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/dmitryfar/32/477_2.png) [@dmitryfar](https://forum.flowable.org/u/dmitryfar)\
**Post date:** [February 16, 2018, 1:27pm UTC](https://forum.flowable.org/t/localization-functionality/1639/3 "2018-02-16T13:27:32Z")

</div>

Joram, thanks for reply!

Yes, it is clean: if I want to change something, it needs to be a redeployed, of course.

And technicaly everyone can add custom functionality to own UI (if needs) to update/delete/add new \*.properties resources for the _deploymentId_ using _ResourceEntityManager_. Because (I suppose) it is not really critical to change theese resources in deployment even while the processes are actualy executed at the moment. Is that right?

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [February 16, 2018, 3:29pm UTC](https://forum.flowable.org/t/localization-functionality/1639/4 "2018-02-16T15:29:20Z")

</div>

yes, however that would mean these resources can’t be cached. Or they can be cached with a timeout, as fetching these every time would be expensive.