Imperial Calendar Support
The Imperial Date Calendar is supported by extension in the OIPA system so that users can enter a date in a date field using the imperial date calendar. Currently when a Imperial date is entered in the system the date is stored in the database on save as a Gregorian date. In order to support use of the Imperial calendar a configuration setting has been introduced that allows users to enter an Imperial date on the screen, and stores it as a Gregorian date in the database. Upon re-display of that date the Gregorian date from the database is converted to an Imperial date.
Configuration Requirements
There are two steps involved in adding support for the Imperial calendar. First, the configuration must be added to the screen supporting the calendar type. Second, translations must be added to the AsTranslation table. This can be done using the Localization Editor tool in the Rules Palette or by adding the translations manually to the database.
- ClientScreen business rule: Configuration was added to this rule. It can be viewed from Global Explorer | Business Rules | Screen | ClientScreen | ClientScreen (International Holding Company) .
- The DateofBirth and DateofDeath fixed fields use the new FORMAT and CALENDAR attributes.
- The GregorianDate dynamic field uses the Gregorian translation key.
- The JapaneseDate dynamic field uses the Japanese translation key.
- Several translations were added to support the Imperial and Gregorian calendar configuration:
- en-us
- TranslationKey: Gregorian
- TranslationValue: Gregorian
- TranslationKey: Japanese
- TranslationValue: Japanese
- TranslationKey:LocalCalendar
- TranslationValue: Gregorian
- ja-jp
- TranslationKey: Gregorian
- TranslationValue: Gregorian
- TranslationKey: Japanese
- TranslationValue: Japanese
- TranslationKey:LocalCalendar
- TranslationValue: Japanese
- en-us