Defects

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

Area Description Test Strategy
System Corrected an issue where price updates and messages were not sent over ION during the deployment (a restore or a back-up procedure) of the application. (WFMPE-5540) This issue happened when:
  • Users approved price changes at night, right before the weekly batch process.
  • There was a request to RESEND messages that are more than one week old.
  • Users approved price changes right before deployment.
System Corrected an issue where the application incorrectly sent DELETE messages that referenced expired TPR price changes (with start/end dates in the past). (WFMPE- 5648)
  1. Identify an item with overlapping price changes (for example, an item with both store and higher location level price changes) with dates in the past.
  2. Create multiple provisional price changes for unrelated items and approve the price changes in one transaction. Use the item from Step #1 for at least one of the price changes.
  3. Verify that a DELETE message for the part of the price change for the item with overlapping price changes in the past that was previously effective is not sent.
User Interface Corrected an issue that caused error messages to incorrectly display when price changes were created at a Region or Metro level that included closed store locations. The application now no longer considers closed store locations while processing price change actions and error messages are no longer displayed for stores that are closed. (WFMPE-5640)
  1. Identify a Region or Metro that includes at least one closed or inactive store.
  2. Create and approve a price change at this Region or Metro level.
  3. Verify that the application does not display any warnings or authorization errors for the price change at the closed store location.
User Interface Corrected an issue that prevented the required field indicator (the red dot) from displaying during the creation of a RWD price change. Additionally, updated the error message that displayed when the user attempted to approve the RWD price change missing those required fields to be more clear. (WFMPE-5470)
Test #1
  1. Click Create Price Change and attempt to create a RWD price change.
  2. Verify that the required field indicator (red dot) is displayed for the required fields.
  3. Leave a required field empty.
  4. Attempt to save and approve the RWD price change. Verify that the user interface displays a clear error message indicating that a required field is missing.
Test #2
  1. Identify a RWD price change in the Price Change List.
  2. Edit the RWD price change inline.
  3. Verify that the required field indicator (red dot) is displayed for the required fields in the row for the RWD price change in the Price Change List.
User Interface Corrected an issue where uneditable fields lost their values when the user attempted to edit an emergency price change inline on the Price Change List. (WFMPE-5693)
  1. Create and approve a regular price change with today as the starting date. This becomes an emergency price change.
  2. Log out and then back into the application.
  3. Identify the emergency price change in the Price Change List, and then click the Edit icon to edit the price change inline.
  4. Verify that the fields that are required during the price change creation, such as the Location Level, remain uneditable in the Price Change List. Verify that these fields do not lose their values.
User Interface Corrected an issue that caused a store-level emergency regular price change to become locked during the application authorization/ deauthorization process if the application received the authorization request and initial price change for the item/store on the same day. (WFMPE-5697)
  1. Create and approve a regular price change with today as the starting date. This becomes an emergency price change.
  2. An authorization/deauthorization request is processed and sent downstream throughout the application. This requires the user to then create a new initial price change for the item/store.
  3. Create a new initial price change for the item/store.
  4. Verify that the emergency price change is not locked and can be modified or even deleted.
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.