Product enhancements
This section presents solution improvements and product enhancements to the existing functionality of Price Management included in this release.
Reason code cache (WFMPE-6070)
Updated the application so that the reason code cache is cleared when a new reason code is created or an existing reason code is modified/deleted.
Valid encoding characters in the location data file (WFMPE-6352)
Completed updates so that pipe characters (|) can be used in the XML and CSV files, such as the location data file, to avoid character escaping issues that occurred in the XML/CSV files..
Search and Clear All buttons in Search Criteria fields (WFMPE-6397)
Updated the Search Criteria fields so that the and buttons are disabled when search criteria is not specified or selected (correcting an issue where the and buttons were enabled, allowing users to search the application, even though no search criteria was applied).
Money type values in configurable attributes (WFMPE-6409)
Migrated current decimal data types for configurable price attributes to be money type with two decimal places.
Sort and filter by alert type (WFMPE-6458)
Updated the Alert column in the Price Change List and Conflict Resolution page so that users can now sort and filter the table by the alert message type. Previously, the Alert column could be sorted by whether an alert existed, but the column could not be sorted/filtered by the alert message type. This allows users to group together price changes with like error messages or filter to a specific set of records with an alert.
List filter options alphabetically (WFMPE-6488)
Updated the user interface so that filter options that display when you filter a column in a table are listed in alphabetical order (correcting an issue where column filter options with check boxes were not listed in alphabetical order).
Date validation for configurable attributes (WFMPE-6493)
Updated the system validation check and rules for configurable attribute Date fields in the user interface to be more consistent. Now, when a user changes a date on a configurable attribute, the system handles the validation check the same way across all Date fields.