Eric and I were working on cross corp and multi corp loyalty points settings. Eric has that project almost done. We also spent some time talking about virtual live or quasi-live testing environments. Eric and Wayne will work out some of those details.

As a fun side note, on one of Eric's project, he did a creative try/catch to let a page try a process and then softly respond if something didn't work. We had done the same thing by checking counts and settings but it ended up being easier to let the try/catch either do the correct action or softly report that it was unable to do it. We ended up stripping off quite a bit of code by handling it that way. Otherwise, it was a constant battle to either show errors or wrap logic with variables and indicators. Rough lesson.

Eric showed me some samples of what the cross corp customer loyalty points stuff looked like. We went through the different pages and made a few notes. All in all, it was looking good. I would imagine that by the end of the week or first part of next week, we should be able to deploy the cross corp customer loyalty points stuff.

Toward the end, Wayne and Eric were chatting about testing environments and when to update those pieces. They talked about maybe even setting up two different environments per server. One would be a testing account (data and code changes daily - simulate the live environment) and another one called dev or a development environment where we could still access a copy of live data, but it wouldn't auto update itself so that we could have longer windows to configure and play with things without hurting anybody else's code or projects. Basically, an auto updated version for testing and a longer term version for testing where needed.