However if the Date/Time field format is 'dd.mm.yyyy' the above error message will not be thrown in such a case and instead the field will regardless of the locale be filled with the inaccurate value of '30.01.1900'
In an article in the Knowledge Management in Serena Request Center the date format from SBM is ignored and it is always shown is US format . To reproduce: (1) Set date format in SBM to dd/mm/yyyy
Dates within email notifications to users that have a datetime display setting of 'use date/time format from locale' set are incorrectly displayed e.g. submit date. The notification server cannot know what the locale of the users machine is and therefore would understandably revert to a setting on the server. However, the locale of the server is set to a non-US locale e.g.UK the date is still displayed in US format - mm/dd/yyyy.
In certain scenarios the getFieldValue Javascript function returns dates in the default format instead of the date format selected by the user. For example the regional settings are set to use a date formatting of dd/mm/yyyy so a date of 07/10/2015 should be returned as 07 October 2015, however for this particular field only the returned date is Fri Jul 10 2015 00:00:00.
For many non-English locales, it is possible to get accented characters with keyboard shortcuts, such as AltGr-a, AltGr-c etc. When using the Rich Text Editor in a system from 10.1.5 onwards, these keystrokes are taken instead as formatting shortcuts for the editor. The only workaround at the moment is to compose your strings in an external editor and copy them in to the field.
This defect revolves around the Date/Time setting a user has selected in their user profile. When the user has the setting set to "Use the Date/Time Format from Locale " in their profile and they run a transition that calls an appscript that creates an aux item and sets the date in the aux item, the date gets stored in the database with a year of 1899.
The only workaround is to ensure that only periods are used as decimal points and that the locale of the user submitting also has a period as the decimal point. As such emails are usually coming from special userids, this affects the locale setting only for that user. Any other user will see the number displayed in his chosen format : 10.22 or 10,22
▪ $TRIGGEREDDATETIME() Returns the date and time the notification rule became "true" for an item. Date and time are formatted for the locale set in each user's profile.
