[CFAMX-1183] Localization - Change source of date format strings - HotSchedules JIRA

Details

Type: Story
Status: Closed (View Workflow)
Resolution: Completed
Affects Version/s: None
Fix Version/s: CFA 2019R1
Component/s: Core
Labels:
- localisation

Sprint:
CFAMX 2019R1 Sprint 6, CFAMX 2019R1 Hardening
SOW (Time Tracking) Project:
44866
Work Type Classification:
Sustaining

Description

This story is to implement a maintainable/scalable solution to determining what date formats to use for a particular user.

Extend tbLocalisation to include Short Date Format and Long Date Format columns
Update /MMS_System_CultureAdmin.aspx to include the two new fields

Stretch - Update the page to support Adding the Date Formats via the UI

Ideally, we would look at this table to figure out the Date Formats (i.e. not need to set them at the Entity / User level.) If a Locale/Culture does not have the Short and Long format specified, it should look at the parent, in the same way that the localization does. Using this method, it is not necessary to maintain the Short and Long Format fields at the Entity and User, instead, once the Localization/Culture is set these values will be derived from that Culture.

Consider removing the current ShortDateFormat and LongDateFormat columns in tbUser and tbEntity, since these should no longer be needed and keeping them around will likely confuse someone down the line. (This might not be possible to do in the time available - at least look into it.)

See branch CFAMX-1161_InheritCultureSettings_Investigation with a bit of UI work and some placeholders for implementation.