results#

The output of a scheduling call. ScheduleResult is what Project#solve, Project#preview, Project#analyze and Engine.schedule return. It holds the baseline token, the changed tasks as Mutation records, dependency cycles, Conflict and Note entries, the convergence flag and, when requested, Analytics. Conflicts and cycles are reported as data in the result, not thrown. The overallocation and load profile fields use types from resources.

Reason, Conflict and Note are abstract classes with a closed set of nested subclasses (Reason.Asap, Conflict.ConstraintViolation, Note.DroppedTask, ...). Match them with instanceof or switch patterns. Every type here is in the org.dhtmlx.plen package.

• AnalyticsCritical path and slack of a scheduling result, with a status that says whether they could be computed
• ConflictA scheduling conflict reported in a result, a constraint that overrode a link or a task placed on non-working time
• MutationOne task's new dates, duration or leveling edits in a scheduling result
• NoteA non-fatal note about input that was left out of the schedule or repaired
• ReasonWhy the planner placed a task where it did, as one nested subclass per cause
• ScheduleResultThe result of solve, preview, analyze, level and Engine.schedule - changed tasks, cycles, conflicts, notes, analytics and overallocations