Relationship Between BPS and ENOVIA Live Collaboration DatesThis graphic shows which settings affect the input and display of date/times in ENOVIA Business Process Services-based applications and the relationship between these settings and ENOVIA Live Collaboration settings. The default settings work and should only need to be changed under specific conditions listed in Platform and Application Date Formats. Most date fields require the user to choose the date using the Calendar chooser and do not require or allow a time entry. If the user's input does not include the time but the date format that eMatrixInputDateFormat matches, either NORMAL or TERSE, does include the time, the ENOVIA Business Process Services enters midday (12:00 noon) for the time. If the matching ENOVIA Live Collaboration date format does not include the time, the date passes to ENOVIA Live Collaboration without a time and ENOVIA Live Collaboration adds it. Typically, only a TERSE format would be defined without a time. Platform and Application Date FormatsThe eMatrixDateFormat and eMatrixInputDateFormat system properties have no affect on how dates are displayed in ENOVIA Business Process Services-based applications. These properties define the Java format to use to send dates to ENOVIA Live Collaboration and to read them from ENOVIA Live Collaboration. Therefore, they must define the same formats that are defined for dates in ENOVIA Live Collaboration. Only change these properties if one of these conditions apply:
Time String FormatTo specify the time format, use a time pattern string. In this pattern, all ASCII letters are reserved as pattern letters, which are defined as the following:
To display a date, the system converts this format to the display format defined by the DisplayFormat and DisplayTime properties and by the browser's language/region setting. This property does not affect the display of dates in ENOVIA Business Process Services-based applications. The count of pattern letters determine the format:
Any characters in the pattern that are not in the ranges of ['a''z'] and ['A'..'Z'] will be treated as quoted text. For instance, characters like ':', '.', ' ', '#' and '@' will appear in the resulting time text even they are not embraced within single quotes. A pattern containing any invalid pattern letter will result in a thrown exception during formatting or parsing. |