Requirement dependency for efficient workflow
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
|Enabled for||Public preview||Early access||General availability|
|End users, automatically||-||Feb 3, 2020||Apr 1, 2020|
Sometimes it's necessary to sequence work in order to make sure that it's done in the correct order. For example, a physical installation must occur before electrical connection. Businesses can optimize operations workflows by ensuring dependent tasks are done in order. This feature allows organizations to complete work in a specific order.
This feature enables the configuration of requirement dependencies to ensure technicians follow the optimal workflow and achieve the most efficient service operation. Requirement dependencies allow customers to schedule requirements in a specific order by relating them through a predecessor and successor dependency relationship. For example, a technician might need to pick up a unique part from the warehouse and then perform work at the customer's site. Critical jobs that rely on a series of tasks dependent on one another can now be linked together as predecessors and successors and booked through the resource scheduling optimizer.
In 2020 release wave 1, this feature will only be supported by resource scheduling optimization with the ability to view these bookings on the schedule board. Also these dependencies will work only for single-resource, single-day scenarios.
This feature is available in Unified Interface only.