Which course in Salesforce can guarantee jobs

Considerations for planning dependencies

Keep these considerations in mind when planning dependencies between service appointments.

This is a feature for managed field service plans.

General considerations

When setting up appointments with scheduling dependencies called complex work, keep these points in mind.

  • Except for consecutive work, you can create dependencies between more than two appointments. However, when you schedule a chain of appointments, dependencies are enforced for every two appointments, even if you do Use all-or-none scheduling for related appointments Select (Use all-or-nothing scheduling for related appointments). In the case of a chain of at least three dates, it cannot be guaranteed that all dates in the chain will be taken into account during planning and optimization. For example, in a chain of four appointments, the first two appointments could be planned, but not the third or fourth.
  • To display the associated appointments for a service appointment, right-click the appointment in the Gantt and choose Show connected out.
  • Change the field set of the service appointment list columns to control which fields appear in search results.
  • It is not possible to assign capacity-based resources to appointments that are part of an appointment chain.
  • If a chain of appointments spans multiple service regions, you must select all regions in the optimization request in order for the appointments to be scheduled.
  • If a multi-day service appointment is part of a chain of appointments, the associated planned end date is not calculated during the appointment scheduling. Therefore, no dependencies should be created between appointments lasting several days.
  • In order for service resources to be considered for Same Resource dependencies, they must all have a single service region membership. A chain of appointments for complex work cannot extend to different service region memberships.
  • Experience generator site dispatchers cannot access this feature.

Consistent work considerations

You can create continuous work with the dependency (beta). Note the following considerations and limitations.

  • Prevents type dependencies from being created for dependencies for chains consisting of more than two service appointments.
  • The optimization enforces this dependency for chains consisting of two service appointments. The standard optimizer does not support this type of dependency.
  • When planning and optimizing, neither the route forecast nor the workforce, resource efficiencies, relocation campaigns, fixed intervals or work lasting several days with ongoing work appointments are supported.
  • Breaks are not supported. Planning and optimization overlap with breaks due to successive appointments, which can lead to rule violations.
  • The organization-wide setting for travel speed is used to calculate travel time between consecutive appointments.
  • If you reschedule consecutive appointments, the original time window of the second appointment is not considered as an available time window by the planning logic.
  • If the first appointment is planned successfully but the second is not, the planning and optimization does not cancel the planning of the first appointment.