remove localization on DB level

[Walter.Koller]

I understand it may improve user experience when they can chose their own language and see Blue Prism UI and log entries in their native language.

However, in an international environment with more than one language, this seems to be contra productive as each user creates log entries in their own language with the result of some people see texts in non-native language nonetheless. 

I assume most people use English to avoid exactly this situation. Other users do just ignore texts they cannot read. 

It becomes more tricky when trying to report on DB level when date format may differ from row to row and instead of one keyword to search for, all possible keywords might have to be considered. Normally only 2-3 language are needed to be considered. Although some users may 'practice their Spanish/French/Chinese...' and may be missed in Audit log analysis.

Example: I was querying Audit logs for event 'A%' to get changes to credentials. Additionally I wanted to extract the credential names by taking everything after the keyword 'credentials'. Then I noticed some logs are in another language and I have to search for another keyword as well.  I immediately noticed this issues but I could have easily missed it. 

I guess when using the built in Audit report feature it would be quite hard to notice some records are missing in the result.

Even more tricky is the situation when sub cultures are used, eg en-UK vs en-US. The text would be the same in both cases but (according to Wiki) UK uses dd/mm/yyyy and US uses mm/dd/yyyy. 

It would be great to have one consistent way of representing data in the DB and then only change how this data is represented in UI; not the other way round.