Organize store task dependencies with subtasks
Important
This content is archived and is not being updated. For the latest documentation, go to What's new in Microsoft Cloud for Retail. For the latest release plans, go to Dynamics 365, Power Platform, and Cloud for Industry release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users by admins, makers, or analysts | 
Dec 1, 2023 |
Dec 1, 2023 |
Business value
Store Operations Assist introduces a modular approach to task management, empowering managers to streamline operations efficiently. Each task in Store Operations Assist acts like a standalone task with individual or team ownership. A distinctive capability of this feature is the ability to establish dependencies among tasks. For instance, Task A can be the main task and can be designated with dependencies on sub tasks - Task B, Task C, and Task D. Each of these sub tasks can be assigned its own unique or shared task template. Subtasks seamlessly inherit the schedule defined for the main task. Dependencies, whether mandatory or nonmandatory, can be specified at the subtask level, ensuring that the main task (for example, Task A) is only considered complete when essential subtasks (for example, Task B and Task C) are finished.
Feature details
Streamlining and managing store operations require store managers and district managers to create intricate task structures that promote an organized workflow. Given the constant changes stores must comply with, there are dependencies that must be handled between tasks. This new capability allows managers to create sub-tasks tagged to main tasks and define the main task dependency as mandatory or non-mandatory. This ensures that associates have a clear view of which tasks must be completed first so that it satisfies the criteria for main task completion. For instance, the next time you want to set up a promotion in a store that requires handling of multiple sub tasks, simply enable it using Store Operations Assist.