This has been implemented with the following new feature:
Show exactly what parts of a generated schedule don't respect the "Prefer" and "Prefer Not" availability entries
Please note that you still need to use "Prefer Not" (not "Must Not") if you still want non-optimal schedules (with conflicts highlighted). For more info, please see Hard constraints vs. soft constraints.
The part about editing one of the resultant non-ideal schedules can still be done, but needs to be done manually.
Thanks for the suggestion!
It could highlight conflicts while still posting the best schedule possible.
This is a great idea, thanks for posting!
FYI, the engine does this today--kinda. Most folks have trouble finding a workable schedule because they input so many "Must Not" constraints. (I think the record I've seen so far is around 500!)
If SLPs change all of their "Must Not" constraints into "Prefer Not" constraints, the engine will gladly return to you a non-optimal schedule. It will still try its best to respect all of the "Prefer Not" constraints, but will move away from them when mathematically necessary to find a workable schedule in the first place.
Just this morning, I updated the caseload editor with additional recommendations along these lines. Also, I've added a few more pages to the Knowledge Base this weekend that will also help expose issues more quickly, all while increasing the likelihood of finding a starting-point schedule.
Customer support service by UserEcho