The 1.2.6 release is an update of the July 1.2 release and has some important bug fixes and new features. A summary of the key updates in this release -
- Demand Components in the workbench can now be adjusted by planners
- Outlier Exceptions are now suppressed by default when there are events
- Performance improvements in UI and engine runs
- Adjustment bug fixes
- Workbench table disaggregation logic and Lifecycle profile application bug fixes
1. Demand Components in the workbench can now be adjusted by planners
All forecast components except baseline can now be directly edited in the workbench UI. This allows users such as sales for example to directly adjust promo or event components. The components add up to make up the total forecast on a given date.
Note - Baseline is not editable as it is flat and determined by the last point of history. Baseline changes should be reflected in the trend component instead.
2. Outlier Exceptions are now suppressed by default when there are events
When there are already events defined for a particular item/loc/customer scope for a particular date, the Garvis engine already has the intelligence about that peak or dip. Hence outlier exceptions are not by default treated as exceptions anymore if there are already events that “explain” it and can be used by Garvis engine