Cory has a list of questions and projects to go over as part of our server meeting. We talked about the email server changes, cascading effects (settings and attributes), and how deep some of the settings and data mapping values go. It really becomes a system. You can't change one thing without it having cause and effect or trickle down effects. That is both good and bad and has pros and cons.

On some of the critical places where users can alter or change things, we may need to catch and hold history records of what was done. This is the when, who, and what type of stuff for some of the settings. We already have it in multiple places, both seen and unseen. We are seeing that we may need to continue to keep adding more historical records. This is especially true in those places that have cause and effect relationships both upstream and downstream.

We talked about some of the upcoming server upgrades and maintenance stuff. That is an ongoing process. We are trying to keep our clients informed but not overwhelmed or worried. It's like a car, you have to keep putting gas in it, do oil changes, and even change out the wiper blades. It's the same with code and servers.