BP language, OS language and region settings

[Walter.Koller]

in current versions following behavior is implemented:
If BP language matches Windows language setting then Windows region settings are used.
If BP language does not match Windows language then BP region settings are used.

Example 1:
Windows language: English (US)
Windows region: German
BP language: English (US)
... BP uses German region settings

Example 2:
Windows language German
Windows region: German
BP language: English (US)
... BP uses English region settings

In example 2, data would be presented differently in eg Excel and in Blue Prism.

This behavior is not limited to German but affects all situations where Windows language and BP language does not match. However, also the opposite is true, eg when Windows and BP are both set to German then Windows region is used.

The idea is to have constant behavior regardless of language and if languages matches or don't match.
Please always consider Windows Region as the ruling formatting

[Stefan__Pappalardo]

The Issue

Until BPAv6.8 there was no German language support for BPA UI. But when region/locale setting of operating system was set to German (Europe/Berlin) the date, time and data (number) formats in BPA UI was set to German. In our environment this leads to the following results.
Windows language: German
Windows region: German
BPA UI language: English (US) <<< Fallback
BPA UI date, time and data (number) formats: German

Since BPAv6.8+ German language support was added to BPA UI. In our environment this leads ot the following results.
Windows language: German
Windows region: German
BPA UI language: German
BPA UI date, time and data (number) formats: German

This wouldn't harm if we were not a team of international developers speaking different lanugages, commited to use English language for our common working language in BPA. We tried to get back our usual working environment from BPAv6.7.1 by selecting English (US) language at sign in to BPA. In our environment this leads to the following results.
Windows language: German
Windows region: German
BPA UI language: English (US)
BPA UI date, time and data (number) formats: English (US)

For short: There is currently no chance to get back the BPA UI language and formats configuration we used in versions before BPAv6.8 (after adding German language support). And clarification purpose: Changing the Windows language and/or region settings is not a viable workaround as it would affect all other involved software with automatic windows language/region detection support.

[Stefan__Pappalardo]

The Solution

Decouple BPA UI language from BPA UI date, time and data (number) formats. Add selection option to installation routine (MSI) and user profile settings (%AppData%\Blue Prism Limited\Automate V3\). This will bring back the possibility to set BPA as usual was the default in previous versions before BPAv6.8 as an .

As we are currently due to the below described issue not able to perform a full release change from BPAv6.7.1 to BPAv6.10.1 we would be very happy about a "hot" fix for BPAv6.10.1(+).
For short: Add backwards compatibility.

[Walter.Koller]

Tobias Arnold, told me a very helpful workaround that we have now implemented in our BP installation routines and is deployed on all of our developers machines and runtime resourcs (~80 in total).

After installing BP, there are several sub-folder for localization in the Blue Prism Automate directory. Delete the folder that fits your Windows local settings and the default language en-EN will be used instead.
In our case we deleted de-DE since our Windows was set to German localization. 
With this hack we now have the same settings for all of our German and non-German speakers 

(I never thought I would ever say this sentence myself ...)
If you find this idea or this hack helpfull, please leave a like or a comment 😉

[Stefan__Pappalardo]

The Workaround

@Walter Koller: Many thanks for the info. To be honest we already knew of this workaround (rename/remove language subfolder). We are in contact with Blue Prism Limited for a while to get a better feeling about any side effects of this option.

[Stefan__Pappalardo]

Please be aware of a first update from BPL...

The Workaround

As an update on the progress of the actions agreed on Friday’s call, our development team have been evaluating the preferred workaround to delete a folder within the Blue Prism install.  Initial observations have been very positive, however, our Q&A team are currently performing more extensive testing to ensure it doesn’t cause other impact to your environment.  I am expecting  an update on the progress of the testing in the next couple of days and should be in a position to pass on that update to you by close of business on Friday.

Long Term Solution committed
In parallel to this work, our Development Team are continuing their efforts to find a permanent resolution which will be included in a future release of the product.

[Walter.Koller]

Many thanks Stefan for sharing your experiences and keeping us updated.
This is much appreciated

[Stefan__Pappalardo]

The Known Issues list was recently updated.
What are the known issues in Blue Prism Version 6.10?
Highlight: The Workaround (renaming language folder) is supported by BPL.