Release 12.3.11

12.3.11.19

Individual Tasks in Task Manager for Multistore Cook

IGCM has been enhanced to create individual tasks for each store in the Task Manager when a cook is performed for multiple stores simultaneously. This enables users to monitor the cook status for each store independently.

Previously, a single task was created for all stores during a multistore cook, limiting visibility into individual store progress.

Each cook task now includes enterprise ID, division ID, and store ID next to the task name in the Task Manager for easier identification. Additionally, the task ID and the date and time when each task was initiated are now displayed.

A screenshot of a computer AI-generated content may be incorrect.

If a cook is already in progress for a store and another is initiated, a prompt indicating the cook status as Queued is displayed.

A close-up of a screen AI-generated content may be incorrect.

Important Points

  • Context (Enterprise ID, Division ID, Store ID) is displayed for cooks initiated with the parent base group in CCM2 only. It is not displayed for other parent groups and child in CCM2. 

  • Individual tasks for each store are not created for cooks initiated through the following tasks in the Task Setup menu (Reports ➜ Scheduling ➜ Task Setup):

    • Prepare Terminal Data for All Stores

    • Prepare Terminal Data

Changes Made in IGCM

The following changes have been made to support this enhancement:

  • A new checkbox, is_split_multistore_req, has been added to the General section under System Configuration utility (Utilities ➜ Utilities ➜ System Configuration). 

    • When enabled, individual cook tasks are created for each store. It is enabled by default.

    • When disabled, a single task is created for all stores.

  • Two new fields, Task ID and Started On, have been added to the Task Manager (Utilities ➜ Utilities ➜ Task Manager).

    • Task ID: Displays the unique identifier for each task.

    • Started On: Shows the date and time the task was initiated.