This is a summary of all changes deployed to our production environment in the scope of this release.
Release Date
15th January 2022
Release Type
| Category | Feature | Description | Resolution | Impact |
| Improvement |
Notifications > Company Notifications |
Admin users were seeing a constant global message that reads; "You have received new notifications" even after switching between tabs. | The codebase was updated to remove unnecessary global messages. |
Now Admin users will not experience this global message when switching between tabs. |
| Improvement |
Linesheet > Product Detail page |
Users could incidentally remove products that were currently or previously approved by Sourcing team causing them to lose valuable approved costs. |
We added additional validations to disable the Remove button for these products. |
Enterprise products are now safeguarded from being Removed where it has ever been sourcing approved. |
| Improvement | Pricing Service | Our in-memory caching solution did not prevent deadlocks. | We switched from using Apache Ignite to Gridgain community edition. |
You should not notice any impact as a result of this change, other than the continued operation of the system. |
| Improvement | Enterprise API | Subscription errors were causing a single error to produce duplicate error logs. | We improved error handling by wrapping these exceptions according to best practices. |
No impact to users. |
| Improvement | Various Tables across the application | In UI for some tables, we had inconsistencies in content alignments causing poor user experience. | We defined a standard pattern, based on content type across the application. |
Now all users will see:
|
| Fix |
Linesheet > Buying and Sourcing Approval Status |
Due to a race condition issue, if an event is failed to process, the system didn't have the ability to auto retrieve and sync the data causing a discrepancy in Buying Approval and Sourcing Approval Status on the Linesheet table and on Cost Analysis page. |
We implemented a retry logic to try and recover from the point in time when a subscription fails. |
Enterprise retailers will not have inconsistency in data and our system will try to recover for any failed events. |