all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|||
|
|||
|
|
|
Uploaded Media/Content & Other Files
(1)
|
||||
| Media Name | File Type | Date | Description | |
| AFB Branding Auto Reduct.pdf | Doc/PDF | 3/2/2017 | Doc form Dave Forbis with the project layout and specs. These are the specs for a project for AFB Branding and auto reduct or automating a supply chain for packaging products. | |
|
Notes:
|
|
On a GoToMeeting session with Nick. We covered a couple different projects and such. They are listed below. 1. New custom project that is needed. From Dave Forbis. We spent almost an hour going over this project. Nick took notes while I read and explained the PDF that Dave had created. See attached for the PDF and see below for the sub notes from Nick. 2. We talked about a mini team with Russell. We would like to get a team of 4 players up and rolling. Russell would be the captain of the team, Alan - as the lead developer, Nick - developer, and Shawn - developer. We talked about how this concept is somewhat - wet paint here... just came up with this... Basically, Adilas will authorize hours, projects, and funds. 6 hours per person per week x $25/hour = $450 (we've told Russell that we have a $500/week budget for this pilot program). This equates to around $2,000 per month that we can run through this project team. These projects could be AFB projects or adilas.biz projects or Adilas Shop projects or custom. The whole adilas project and platform is really one giant project. We are taking a small pool of developers and trying to structure them into teams with captains and leads. The developers will be paid from adilas.biz, Adilas Shop, AFB, and from custom projects. We need to get in and see how this works. If we need to, we can tweak it around. Think of water, snow, ice. We are in the water stage. 3. We merged in about 18 new files for elements of time as part of the system-wide black box project. Good session. |
|
Additional Comments/Notes - Subs (2)
|
||||
| Title/Caption | Date | Time | Done By | Comment/Note |
| Working with Nick | 3/22/2017 | 10:25 am | Brandon Moore | Nick came over and we did an hour or so working on the project. |
| overview with Brandon | 3/2/2017 | 4:28 pm | Nick Vaughn |
-Dave Forbis is Point of Contact for the project -auto deduction of inventory every time something "sells" -we'll interject this somewhere in submit_cart- probably down with the other 3rd party pieces on the page -we're assuming that the settings are going to be too large to maintain on the 3rd party solutions page, so we're going to put a button on that page that will take the user to a separate AFB Branding page. -need permission 76 probably (giving permission to a manager, not a bud tender) -we're pulling from inventory WITHOUT selling -type will be a dropdown menu (most likely part categories) -may need to expand the Amount field to include a range AND the uom -bottle type and item name are both dropdowns -item name will likely be dynamic per system- we need to know what we call it, what they call it, and then we need to map that together -look at sub_inventory_templates to see how we can do multiple/ a custom number of rows of fields (compare this to the sample form) -when deducting items from the inventory, we can use spots on an array similar to what we've done on other API projects. this way we can create virtual "tally marks" for every item on an invoice that needs to be tracked from inventory |