Recording some more ideas for time settings. got into database field settings and custom verbage (names and aliases and instructions) planning.

These notes were added as of 9/3/21 - Original date was 7/24/21. All of them are dealing with elements of time and new time settings

- We need validation on the add/edit time action page to reflect the new template settings and verbage settings

- If a frequency is selected, help it automatically show in the add/edit page for adding time (all settings and verbage settings). It may also be nice to do the same thing for the sub dates and times and sub flags and tags. For example: Say I mostly deal in hours, if that is selected, i'd like to see hours preselected in the frequency drop-down. As a side note, we will use a new setting to take care of this.

- Some pieces of elements of time get pulled into the shopping cart. We may need to check settings and template values there as well.

- With all of these changes to names and defaults, we will need to update a number of help files.

- List of subs
Action Status Logs & Changes
Additional Date/Times
Additional Categories and Special Flags
Additional Comments/Notes
Additional Sign-Off's
Additional GPS or RFID Tag Tracking
Additional Payroll/Time Sheets
Additional Notification/Reminders
Additional Tie-In's/Assignments/Pools ("any" person, place, or thing)

- On sub sign-off's - Take off the under construction note on the template page.

- Add a date/time frequency id for general dates - this will be a new template setting - use it for start dates, end dates, and target dates - make sure it replaces the total time frequency id and also populate things in the edit mode for flipping dates quickly.

- On the time templates, add a budget frequency preselect, including a custom one. Currently, you can just turn on budget stuff but can't set anything.

- There is an awesome function called buildCustomFieldSettings in cfc/basics_3.cfc - We may need to add an alternate table name to allow for time templates to be pulled, as they are different then the main defaults. Once done, make sure and search other usages and update them with an alternate table name as well (for customers and such).

- Took a small break and went outside and walked around my house. Came up with a couple of things for me... 7/24/21

- Create a whole excel spreadsheet with the new verbage changes that are needed. Include a usage column to remind me or whoever where these changes need to go or show up. Very important, so that we don't miss anything.

- On horizontal time views (and vertical time views) make sure and show conflicts or double, triple bookings - expand as needed.

- Keep planning it out... it may be faster in the long run, including options to delegate parts and pieces.

- Figure out the dynamics - say $$custName$$ or $$locName$$ for the corp-wide settings for customers and locations. just an idea.

- Not worried about time or money to do and finish this. Do it right and build as if for years. Part of this is showing that fracture (future project) is possible. Small exercise and experiment. I know that it is possible.

- My current job is focusing on project management and planning

- Sell and pitch the vision

- It doesn't have to be done to pitch it

- Keep prepping things and be your own style

- On the db_field_settings (custom field names and aliases), we may need to update the db_field_rules_min from unsigned to signed (allow negatives).

- On the new db_field_settings... do a check to make sure that _display and _short_display values all match up. Check excel before doing a final commit. Maybe add some temp columns to the spreadsheet to see what is where.

- We had the idea to make the advanced search be template specific. What about being able to make the main time homepage be template specific. That would be really cool!

- Speak their language. Everywhere that is possible. Make it easy. Less training will be needed later on, that way.