Defects

This table shows a summary of the defect fixes included in the release.

Area Description Test Strategy
Price changes Corrected an issue that allowed a TPR price change to be created for an item with a higher price than the REG or initial price of that item. This issue occurred when a TPR was created for a location level higher than store, and then a new store was added within that location level with an approved initial price for the new store. (WFMPE-6032)
  1. Create and approve a TPR price change for an item at a location level higher than store. Note the TPR price. Let the system process the TPR.
  2. Add a new store within the same location level used in Step #1 (within the same metro or region) to the system.
  3. Create an initial REG price change for the item at the new store location with a lower price than the TPR price.
  4. Attempt to approve the initial REG price change.
  5. Verify that the system displays an error indicating that the REG price must be higher than the TPR price.
User interface Corrected an issue where the cursor incorrectly moved to the end of a string of text in a field when the user clicked the start of the string and entered a space ( ). For example, when the user clicks the start of the User ID field for an existing user in User Management, the cursor is moved to the end of the text. (WFMPE-5740)
  1. Navigate to User Management.
  2. Identify an existing user and click the Edit icon to edit the user inline. The editable column fields are enabled.
  3. Click the start of the text in the User ID field. Specify a space at the start of the string ( ).
  4. Verify that the cursor does not move to the end string of text. Verify that the cursor is displayed correctly.
User Interface Corrected an issue that caused "Delete" error messages to incorrectly display for a TPR item/price change at a Region Location Level if that region included a closed store location, locking the price changes. (WFMPE-5768)
  1. Create and approve a TPR price change at the store level. The TPR price change should run for one week. Note the store ID/number and the End Date.
  2. Create and approve a second TPR price change for the same item at a different store in the same metro as the store from Step #1. This TPR price change should run for only a few days, with an End Date before the End Date used in Step #1. Note the store ID/number and the End Date.
  3. Close the store from Step #2 after that TPR price change ends.
  4. Wait ~30 minutes for the application to process these changes.
  5. Create and approve a TPR price change for the same item at the regional level for the region that includes the metro and stores from Step #1 and #2.
  6. Verify that the application does not display a "Delete" error message from Mammoth. Verify that the regional price change is created successfully and that the price change does not become locked.
User Interface Corrected an issue that prevented items from being loaded into the database from Infor Retail Information Management (or a third-party item repository) if an item attribute was left blank (or with a leading space or a line break) even though the attribute was not required. Now, the application accepts all attribute values, even if they are empty, during the import process. (WFMPE-5785)
  1. Import items from Information Management. Leave several non-required attributes empty.
  2. Verify that the application does not display an error message indicating that a non-required attribute field is missing a value. Verify that the items are imported correctly.