Any 'Date' field value set through UI Policy script gets corrupted if the users date format is differentIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Any 'Date' field value set through UI policy script gets corrupted if the users date format is different. Release Any Supported release Cause Value passed through the script and the users date format are different. Resolution In the UI policy script, if the value passed on to the 'Date' field is in the format "yyyy-mm-dd" and the users date format is "MM-dd-yyyy": The value in the date field gets corrupted after saving the record. Ex: It may be displayed as '0190-03-05' if it was entered as '2019-03-05'. If the users date format varies across the system, make sure to get the users format and then pass the value on to the Date field. or make sure all the users have the same date format and use the same in UI policy script.