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
The user creates an annotation on a workflow. He then edits copy in Notepad++ to allow for formatting , and then copies the text from Notepad++ and pastes into the Composer annotation. Depending on how the text was entered and copied, it may paste an invalid control character.
