Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Cory Warden
Created Date/Time: 4/4/2020 9:33 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 6225
Template/Type: Brandon Time
Title/Caption: Steve, Cory, Brandon-Catch up on projects and updates
Start Date/Time: 4/13/2020 10:00 am
End Date/Time: 4/13/2020 11:00 am
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

Project planning and coordination with Cory and Steve. On a big scale, we are seeing lots of interacting and connected settings starting to popup. That is both good and bad. Good in that people can set what they want. Bad in that they then have to be educated on what choices to make. Growing pains in the world of settings, configuration, and permissions.

- Talking about sub inventory and new package management settings and rules to play by. Auto open new packages, auto close 0 quantity packages, and other open/close type settings or rules.

- We have a client that needs really high numbers for invoices, invoice payments, invoice line items, PO's, and other places in the system. We talked about options to expand our current database tables or maybe go more along the lines of real in-line extensions and what that might do or handle. Imagine if we could flag a certain invoice that it has super high numbers. We could then use a custom table, such as custom_big_numerics, to hold the numbers in. We could set up the system to check for really big numbers and then run accordingly. Lots of talk about flagging and tagging records, and then rolling over to real in-line extensions to help handle the special cases. Think database extensions vs fixing the whole system to handle the random couple that exceed the norm. Some good ideas there.

- Along the lines of huge numbers. We may also want to include huge positive numbers, huge negative numbers, and huge numbers of decimals (details after the decimals).