NEW CONTENT/IMPROVEMENTS

Reservations

Finished validation for reservations. The validation checks:

• Whether the reservation instances fit the resource availability constraints.
• A check to see if the reservation instances are located in the past.
• Whether the reservation instances intersect each other (would not want to conflict with your own reservation, would you?)
• IMPORTANT NOTE: NO checks are in place for Phone/Extension and Description fields. These seem to have been intended as optional free-form fields, so the base functionality does not check them at all, as far as I know.

Improved time line usability

• Now all items on the time line are color-coded. All background areas are colored based on the time range type (e.g. resource unavailable, resource reserved, etc.). All current reservation instances also change color based on validity checks (yellow/green = no problem, orange/red = the instance is in conflict with something).
• Added a legend to the time line.
• The offtimes for resources now “leapfrog” along the time line. In the previous version the offtimes were generated only for the first 27 weeks starting from the current moment. All offtimes beyond that were not shown in the interface (for performance considerations). Now if the user scrolls to a moment that is at least 2-3 months into the future, the offtimes “leapfrog” into the future to show the offtimes of future periods, so that the user gets a consistent picture of offtimes up to any moment in the future he/she choses to look. If the time line is scrolled into the past, the offtimes “leapfrog” back and “dock” to the current timestamp as needed.
• PLEASE NOTE: If you're scrolling to a reservation instance that is far away into the future, it may sometimes appear as if the resource is available, although it really is not. If you release the mouse button, the reservation instance is updated and is then shown as unavailable. This is because of the “leapfrogging” mechanism described above: the color-coding happens based on intersections on the time line, not real back-end checks.

Other

• OpenLog integration now available!!! Sincere thanks go out to Paul S. Withers, who offered to help and went through the trouble to implement it. If you want to use OpenLog to capture your errors, just change the xsp.properties variable xsp.openlog.filepath to the location of your OpenLog.nsf database relative to the server Data folder. Please see the OpenLog Logger project (https://openntf.org/main.nsf/project.xsp?r=project/XPages%20OpenLog%20Logger) for additional options at your disposal.
• Custom error page now in place, courtesy of Paul S. Withers.
• Introduced My Reservations view. Now a user can look up their own reservations. Still thinking on how to best implement the Calendar view…

FIXES

Reservations

• Fixed loads of data-induced bugs when submitting New and Quick Reservations.

Resources

• Fixed the “Delete Resource” button. It now works as intended. I seem to have skipped it previously. Sorry! :)
• Fixed an issue when a resource being marked as unavailable on some day would lead to the time ranges for these days to become corrupted (the timestamps would multiply uncontrollably).

MISC

• Cleaned up the code a bit. Redundant and obsolete parts removed, missing Javadoc added, some code refactored.