Net-change report

This section provides a table of resolved customer-reported defects and fixed issues included in this release.

Note: This release includes defects found in previously released hot-fixes from 20.3.x and may be found in that section of the release note documentation.
Area Description Test Steps
Search Corrected an issue that prevented the application from displaying search results when a user specified partial text values in the Item Description and Price Change Description even though items with that partial text value exist in the application. (WFMPE-6685)
  1. Navigate to the Price Change List.
  2. Specify an incomplete description of an existing item in either the Item Description or Price Change Description fields in the Search Criteria fields.
  3. Click Search.
  4. Verify that results are displayed.
Search Corrected an issue that occurred when a user searched for a brand within the Select Brands list field in the Search Criteria fields where the application did not return any results even though the specified brand existed in the application. (WFMPE- 6692)
  1. Navigate to the Price Change List.
  2. Specify an existing brand in the Search field within the Select Brands list field in the Search Criteria fields.
  3. Click Search.
  4. Verify that the application returns results for the specified brand.
User interface Corrected an issue where the Actions column was not aligned and did not display correctly in the tables in the user interface. (WFMPE-6675)
  1. Navigate to the Price Change List.
  2. Specify a search in the Search Criteria fields to populate the table with price changes.
  3. Click Search.
  4. Verify that the Actions column is displayed and aligned correctly.
Location override Corrected an issue where a store-level TPR price change with Location Override set to Yes caused the actual in-effect price for all other TPR price changes with the same item and any overlapping days for all other stores in the same region to become ineffective. This resulted in the Advanced Price Lookup page to incorrectly display the last prioritized price for any other stores in that region. (WFMPE-6725)
  1. Identify a region with at least three stores authorized to sell the same item. Note these stores and the item.
    Note: For this test, the stores are listed as 1, 2, and 3.
  2. Navigate to the Price Change List, then click Create Price Change.
  3. Create a TPR price change using the identified item for store 3 with Location Override set to No. Note the Start Date/End Date used.
  4. Create a TPR price change for the item at the whole region level with Location Override set to Yes. Verify that this region-level TPR price change overrides the price used in Step #2.
  5. Create a TPR price change for store 1 with Location Override set to Yes for the item with overlapping dates.
  6. Navigate to the Advanced Price Lookup page.
  7. Verify that the price from the TPR created in Step #4 is used for store 3 and store 2. Verify that the TPR from Step #5 overrides the price from the TPR in Step #4 but does not cause the region-level TPR to become ineffective.
Location override Corrected an issue where a TPR price change for a region with Location Override set to Yes caused the in-effect price for all other region-level TPR price changes with the same item and any overlapping days to become ineffective. This resulted in the Advanced Price Lookup to incorrectly display the last prioritized price for those regions (instead of any existing region-level TPR price changes). (WFMPE-6727)
  1. Identify two regions with at least two stores authorized to sell the same item. Note the regions and the item.
    Note: For this test, the regions are listed as 1 and 2.
  2. Navigate to the Price Change List, then click Create Price Change.
  3. Create a TPR price change using the identified item for region 1 with Location Override set to No. Note the Start Date/End Date used.
  4. Create a TPR price change for the item at a store in region 2.
  5. Create a TPR price change for region 2 with Location Override set to Yes for the item with overlapping dates.
  6. Navigate to the Advanced Price Lookup page.
  7. Verify that the price from the TPR created in Step #5 overrides the store TPR price change from Step #4. Verify that the region TPR price change from Step #3 is still in-effect.
Bulk editing price changes Corrected an issue that occurred when a user modified the Multiple Price value using bulk edit causing the Price value to be recalculated by the system where the application incorrectly validated the system's new Price value against the old Multiple/Multiple Price values instead of the new Multiple Price the user just specified. The application then incorrectly displayed a validation error on the Price field, preventing the user from saving any changes, and caused the user to become stuck in a loop unless the original Price value was used, resulting in the Price and Multiple Price data to become mismatched and out of sync. This also caused incorrect price data to be exported downstream for price changes where there was a mismatch. (WFMPE-6780)
Note: This issue only occurred if the bulk edit functionality was used to change either the Multiple Price or Price.
The test steps used are based around an example.
  1. Create a simple price change with a Price of $3.33 and a Multiple/Multiple Price of 3 for $10.00.
  2. Select the price change from the Price Change List. The Action Bar is displayed.
  3. Click Edit from the Action Bar. The Edit Price Change Values page is displayed with the editable fields.
  4. Edit Price to $5.00. Verify that the application displays a validation error because the new Price does not match the Multiple Price deal. Change Price back to $3.33.
  5. Edit Multiple/Multiple Price to 3/ $15.00. Verify that the application recalculates the Price to $5.00. Verify that the price change can be saved without any validation errors.
  6. Edit Price back to $3.33. Verify that the application displays a validation error and the price change cannot be saved.