We have the Schedules from EMIX Constraints:
availabiltySchedule
unavailabilitySchedule
We also have the EI ConstraintBehavior, which is hints at how to deal with times when there is an incompatibility between the temporal constraints of the schedule and the requirements of the event.
Currently, the availability schedules are in the array of constraints. Should they instead be paired in some other object with the eiConstraintBehavior? This appears to be what the eiConstraintSchedule does. In refactoring [eiEvents] several constraints were eliminated, a couple new ones were added to EMIX constraints, and the event now has an array of constraints, unspecified.
Should it be an Array of eiConstraintSchedule(s) with any single constraint modifiable by the eiConstraintBehavior? Should only some constraints be expressable in eiConstraintSchedule(s)?
Major
I would like a discussion of the ConstraintsBehavior object, as it is not a Constraint, as defined in EMIX, but some responses to some specific constraints when encountered.
It almost sounds as "How to configure the VTN for this customer [VEN]". Can the VEN CHange it? Is it a report about that configuration to the VEN, but its actual setting is out of scope?