This is related to issue #39. Services are scheduled by assigning them to a TimeSlot. This is implemented via a Lookup relationship between the two custom objects. The Lookup dialog is a clumsy interface as it doesn't do the following:
Filter out past TimeSlots.
Filter out full TimeSlots.
Display future TimeSlots by default. The user must enter a search criteria: "2014", etc.
The current implementation might be usable for initial rollout, but I'm sure that the users will prefer a better user interface.
rmsu
commented
9 years ago
This is related to issue #39. Services are scheduled by assigning them to a TimeSlot. This is implemented via a Lookup relationship between the two custom objects. The Lookup dialog is a clumsy interface as it doesn't do the following:
The current implementation might be usable for initial rollout, but I'm sure that the users will prefer a better user interface.