As a Chorus user, I'd like to be able to specify (independent of locale, browser settings, or system configuration) how dates appear in Chorus. This should include both entry fields and other places (such as history) where dates are presented.
While it is possible for Chorus process developers to control input fields in form design, the options are limited, and this does not change other areas such as history, which results in further user confusion. This also does not address a single process used in different regions with differing standard date formats, where the only current solution is the creation of multiple otherwise identical forms.
One suggestion is to enable an additional user preference, as this would cater for Chorus implementations where a single solution (set of processes) is used across multiple geographies.
... View more