AGR Technical Manual

This documentation is intended for AGR consultants and technical users.

What’s New in AGRv6.2?

Staging 2.0 officially released and used in all new implementations going forward. The new staging framework standardizes data mapping, has a defined architecture for customizations and will be maintained and updated in future releases/patches like the prod database. The new framework is a step forward towards greater modularisation of the system.

The Scheduler introduces new ways to manage and interact with tasks , whether it is to schedule them, restart , cancel them, disable them, take a look at their history , or just see the progress for that particular run. There is also the option to run a task partially .
The new Calendar is interactive and flexes a new interface to schedule tasks and countings as well as serving as an overview of upcoming dates. The new and improved scheduling interface is far more flexible than before, including options to add a specific period, the exact time, and intervals. Furthermore, if a schedule is still not perfect, dates may easily be added or removed by simply toggling them in the calendar - without having to alter the schedule itself.
Encapsulates scheduled orders, scheduled counting, and schedules.

Logging in the system standardized and refactored. This new event logging replaces the old logging with a more unified concept with greater flexibility.

Features that have until now been maintained by consultants are standardized and included in the release:

Connected items
Bridge Stockout
Promo Smoothing
Order Analysis Workspace
Archiving of Old Orders
Standard Reports (A portfolio of reports that enable effective exception management for analysing the supply chain)

Performance helping tools for consultants

New zys schema – Toolbox to help consultants analyze performance and database statistics.
Ex Views – Views to flatten out tables so you don’t have to join multiple tables to get information.

Translations now managed globally in the cloud (AGR Pool) and a translation_override table added to each setup for private (customer only) translations.
Translations are retrieved in a background task that is initiated when the client application is loaded.
Translations are only retrieved if the feature is turned on and there exists any new translations.

Migrations i.e the support and conversion of old data structures (JSON objects) in the database moved away from the client project and into an external script that runs along with the installer/update scripts.

As always, you can view the release page at releases.local/