Date fields in business rules or record producer scripts fail to populate with a correct date value because the internal code does not take the date format MM-DD-YYYY into account.

Steps to Reproduce

1. Create two fields in the Incident table or any other Task extended table:

Type: Date
Name: Current Date
Type: Date
Name: Copy Date

2. Create a Business Rule on the table selected in step 1:

Set field values: "Copy Date same as Current Date"
Rule: before
3. Login as a user with the date format set as system format YYYY-MM-DD.
4. Create a new Incident and set the Current Date in it.
Observe the BR created in step 2 has run and the Current Date was copied into Copy Date.
5. Change the user date preference to MM-DD-YYYY or DD-MM-YYYY. 

6. Repeat step 4.
Observe the copy date action fails, populating an invalid value into Copy Date.


This issue was fixed in Madrid. There is no workaround applicable. Please review the Fixed In section to determine the latest available patch your instance can be upgraded to.

Related Problem: PRB1290308

Seen In


Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-06-27 04:44:54