149 views

Description

When a Date/Time or Currency or Decimal field is set to read-only, the database value for that field is passed to the validation script when the form is updated. If the current user has changed the Date, Currency, Decimal format to something other than System, the read-only field value will not match the format set by the user and a field "Invalid Date" or Invalid decimal number" error will be triggered. This differs from a non-read-only field where the display value is passed to the validation script instead of the database value.

 

Steps to Reproduce

  1. Log in to a Jakarta instance as a non-Maint user.

  2. Open the user's profile record and change the Date format value to MM-dd-yyyy.

  3. Navigate to Change > Create New.

  4. Click Normal: Changes without predefined plans that require approval and CAB authorization.

  5. Set the following field values:

    • Configuration item: ApplicationServerHelpdesk
    • Assignment group: CAB Approval
    • Planned start date: 10-27-2017 12:00:00
    • Planned end date: 10-27-2017 13:00:00
    • Enter values for Description, Short description and all Planning fields.
    • Use default values for all other fields.
  6. Save the record.

  7. Click Request Approval.

    The Conflict last run field database value is passed to the validation script where its format is compared to the user's preferred date format, does not match, and fails validation.

Workaround

If you are able to upgrade, review the Fixed In field to determine the versions that has a fix.


Related Problem: PRB1235556

Seen In

Jakarta

Fixed In

Jakarta Patch 9
Kingston

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-08-09 10:50:02
Published:2018-07-26