Talking about delayed counters and working on phase 2 of that project. Molly, Cory, and Brandon were on the call.

Known needs:
- we need to be able to include subs
- we need to be able to scan subs - currently only scans parent subs
- we also need to be able scan and hold (scan every unit in a bin) and then have that count for you
- multiple locations and being able to scan and hold - not really real adilas locations - kinda like sub locations within the same location
- be able to ultimate review before submitting for processing
- on the review, you could see who scanned what

// ideas

- Maybe a new button that allows for multiple scans (scan to count) - Once it comes up, maybe a spreadsheet like column with multiple lines

- On the review and commit page, be able to search and filter by item and by person and by notes.

- You also need a way to remove and/or combine certain pieces. Kind of a fully functional master overview.

- They would like to see some new quantities such as total amount scanned, system count (on hand), and an open field for the real quantity. Maybe even show them the math before we actually do it, meaning another quantity called math adjustment quantity (non adjustable >> just a math calc).

- On the review page, they wanted a little bit more info without over doing it.

- We may need to change the database model and move from JSON text to real database entries. This would help with searches, show/hide stuff, and better ways to clear and/or delete things out of the process.

- Molly was talking about the importance of date filters and date/time stamps

- They don't want to see all of the sub information (too much). They would like to rework the normal update PO process. (update_inventory_count.cfm page). They would like to have all of the subs open by default, take off all of the extra sub info and sub inventory attributes. Keep it simple and easy. They like how simple the delayed inventory counter looks but even that one needs some new fields.

- Some of the people use this process every day. Many of them use it at least monthly. They really want it work on a Wearhouse type model. Lots of scans and less clicks. They want more of a barcode based model.

- There was some discussion on how to display the review and submit page. Some of the comments were grouped by parent item and then broken down by person who did the scans. They were talking about having a total summary line per item and then some sub details that could be showed if needed (collapsible like the show subs option for sub inventory).

- There was some talk about storing multiple steps in the session scope. Basically another way of delaying the inventory counting. Currently we submit each page... the question was raised about submitting multiple pages and then having a final review to do the real submit process.

- As a side note, the action page for the delayed count process aborts and shows a dump. We need to help and clean that up.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=22&id=1485 - community funded project for this piece.

See attached for a link to the video recording of the GoToMeeting session.