Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 7/17/2018 5:45 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 3935
Template/Type: Brandon Time
Title/Caption: Adilas Time
Start Date/Time: 8/30/2018 9:00 am
End Date/Time: 8/30/2018 1:00 pm
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

Small pow-wow on what happened with the server hack, light debriefing and recap, where we are going, and how to push usernames and passwords to other developers. Making a small plan to push out resources to the different developers.

Calvin came in and we were chatting about the upcoming adilas training in Denver as well as bulk texting (GMext program) and text alerting (more strategic but smaller text messages). Lots of needs and options coming down the pipeline. One of Calvin's comments was the cost in multi texts is in the texts. The cost in alerting is in the code and how to make those triggers and where to place those pieces of code.

We also spent some time talking about the adilas label builder and how that will all play out. Calvin and I were documenting steps and processes to get it all rolled out. We spent a lot of time talking about the order process (what do you want), how we can assign it, how we then request it, and how to actually process and print that label. We also lightly talked about how to communicate back and forth between the different servers. Lots of moving pieces and lots of data going back and forth.

The end goal is to get a custom label solution that is owned and used by adilas for the adilas clients. We want to keep building onto the overall solution and/or platform. Sometimes, we have to build stepping stones and then try to link them together to make up the bigger picture. Lots of mixing and blending of pieces and concepts. Another interesting piece of the puzzle is the question, how are things being used? Sometimes the feedback that we get and when we can see the usage patterns, that is like gold to a developer. If we let our users, they will help tell and show us where we need to go and how to get there. They, our users, are a huge resource.

Spent some time helping Dustin get his settings page dialed in. He is making one of his first, both add and edit, pages that uses the same page. Lots of his logic is modern div tags and JavaScript vs normal page modes and physical page refreshes. He was on it and will do fine.