This is a summary of all changes deployed to our production environment in the scope of this release.
Release Date
19th February 2022
Release Type
| Category | Feature | Description | Resolution | Impact |
| New Feature | Settings > Order Settings |
Order Settings will enable Customers companies to set the configuration required for processing orders. These are settings required to create every new purchase order hence allowing them to configure removes the manual input at an individual order level. This is in preparation for the upcoming Order system launch. |
N/A |
Administrator and Merchandising Managers will be able to configure the Internal and external Order setting required for Purchase Orders. |
| Improvement | Linesheet > Maintain Sales Price |
Currently, Integration users could set Retail Price as a dependent field, even when Maintain Sales price = Off for any product, causing incorrect data overwriting. |
We made changes so Retail Price can only be set to a dependent if maintain sales price is switched ON for all rows in Linesheet. |
Users are protected from erroneously changing setting for Maintain Sale Price toggle when the Retail Price field is set as a dependent field by Integration users. |
| Fix |
Linesheet |
If a memo set is created using individual products for which cost submission is not approved, set row approval status would not update even after the contained product gets approved. Users were forced to approved individual products approved before creating a memo set. |
We updated the function logic so the approval status of the Memo Set row gets updated based on its contained product status. |
Memo sets will now show the correct approval status. |
| Fix | Enterprise API | Some vendors had found that their Sales Team members were unassigned from customer companies and were no longer able to access Cost Submissions. | We redeployed our internal services and updated the function logic to prevent this issue. | Affected Sales Team members now have access to Cost Submissions. |
|
Fix |
Customer Settings | Suppliers would lose their saved Discount and Coop for a specific customer anytime that customer's Sales Team was updated. This resulted in wrong prices being displayed for the affected customer. | We updated the function logic such that updating Sales Team members no longer impacts the Discount or Coop for that particular customer. | Discount and Coop values set for the customers will remain unimpacted when changes are made in sales team members. |
| Fix | Linesheet > Batch actions |
Linesheet has multiple batch actions where a user can change values for integrated fields via Atelier even if they are defined as dependents and should only receive values from their system. | We updated the function logic so users can not make changes via Atelier for fields that are set as Dependent using batch actions. | Now clients using the Retail Data Management in Atelier will be protected from erroneous overwriting for their system's critical data. |
| Fix | Samples > Sample Upload |
If the vendor initiate editing sample data but click save without making any changes, Cost submission was getting withdrawn. This is confounding because if there is no change in data, resaving should not trigger the withdrawal of cost submission. | We greyed out the Save button in the sample edit flow when there is no change in the sample data, stopping incorrect Withdrawal of cost Submission | Now if vendors don't make any changes to sample data, Cost Submission won't be withdrawn for their customers. |
| Fix | General UI > Performance |
If users spend more than 45-60 minutes in the application, some users were experiencing slow page load. | We resolved the issue by resolving memory leaks on certain elements. | Now performance would remain stable - regardless of the length of time spent in the application. |