Planning with Bryan. The topic of the day was brainstorming on the "any" scheduler or any scheduling stuff. We talked about a number of different steps and what we could save and where.

1. We will use JSON page level settings for simple and advanced (shifts) rostering. Thinking about a number of different tabs going across the page for the new settings. Tab 1 would be simple full day rostering, tab 2 would be advanced shift level rostering, tab 3 would be shift settings, and tab 4 would be the web availability stuff listed below (in number 2).
2. The more advanced stuff will be saved in the layers or availability layers. We have already come up with 3 sub steps of that process. Click here for more info about the web availability layers. As a note, the web availability layers would be saved in a database as individual records vs JSON object storage. It will help us look things up and map usage/availability levels better.
3. We will offer a number of different, user defined, saved favorites. These are custom reports with saved search criteria. Some of these may be calendar views, horizontal time views, vertical time views, and other custom reports. Here are a few links with some ideas. See element of time #'s 8004 and 6967 in the shop.

Good brainstorming session and going over ideas. We got pretty technical and did a lot of drawings. It's fun to see how things progress and the progression of things.