Meeting with Cory and Shari O. over a Zoom session. We were looking into an issue with one of our client's balance sheet and some gift card transactions. We had to update the created date/time on the corp special account transactions for some gift cards that were partially done in the old way and then converted to the new way. As a side note, we may need to allow that date/time field to be editable. I had to do it from the background. That might be nice to have that as a standard feature.

We talked about the discount engine project and came up with a small plan for going forward. The new plan involves a database change, retrofitting the old discount engine code to use the new database changes, then working on the new discount engine code. Ideally, we get the database piece done and then allow our users to pick if they want to use the old or the new (for a while). When ready, we fully transition to the new code base. We also covered some other questions and what not.

Two different sessions with Eric, going over tips, payments, and use cases and scenarios. Our first session was in the morning from 9:30-10 am. I had to bail out to meet with Cory and Shari O. We met up again at 11 and did some more talking and discussing. The main goal was tips, flow, and keeping financials in balance and in good shape. We also talked about either creating and/or using some mappings for new expense types and/or deposit types. We talked alot about EMV/chip readers, tips, and how to handle those credit card type transactions. We also talked about cash/check scenarios and how that is sometimes treated differently for tips and repayment.

Each corporation does their own stuff and handles tips in their own way. Some treat it as cash and cash out every night. Others hold it, track it, and pay it back out with payroll, taxes, and a rolling payment method. Lots of companies in between, including some companies that don't allow or don't even deal with tips. Lots of possible scenarios.

Some of our discussions got off into the weeds a bit. Adilas is so flexible, we allow our clients to sort of make up their own rules. That is great, but we may also need a way to help steer them in a good direction and/or help them enforce their own rules. If we create something, we can't just take that away. We have to leave it alone so that it can play through any past transactions or user history actions. That complicates things a bit.

We talked about a dedicated tip screen on the checkout process. That would help us gather the correct information and even provide us with enough information to process things how we need to, to keep everything inline.

Looking into the discount engine code. Created a new branch and stashed some of the older code pieces. I'll grab and pull things out as I need them (stashed resources). Started to make a new database update page. Slowly working through the different pages. First task is to map things out and match up database changes between old and new. We can't launch the new without the changes but the new changes will break the old discount engine. We have to meet in the middle. This project has been being worked on for a couple of years now with multiple developers. I'm kinda doing a salvage and clean-up type project.

Spent an hour doing some training on W3schools. Reviewing some HTML and CSS stuff.

Working with Shannon. Reviewing some of our work from last week. Then jumping into the next section. Copied over the jellyfish overview from an internal questionnaire from a couple of years ago. Spent the rest of the time working on the SWOT analysis. John and I roughed out some stuff back in July. Shannon and I were going in and harnessing some of that work. Trying to make that document more usable. See attached for some uploaded pieces that we are working on.

Meeting with Bryan. Looking over his bigger CSV file maker code with a progress bar. Looked pretty good locally. Pushed it up live and did some bigger tests with it and it had some issues. We talked about ways to make the bite sizes smaller and smaller. It's still trying to process too much at a time without any information back to the users. Slowly making progress.