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 | |
| intro_to_process_and_documentation.docx | Doc/Text | 4/18/2016 | Awesome article called "Get Control! An Introduction to Process and Documentation" by Dave Hecker – April 12, 2004. I've read this article a number of times. A good one on project management. The original article was posted up on a website called: sitepoint. | |
|
Notes:
|
|
Shawn came over to my house to work on the Hypur project. We worked upstairs in the front room (better natural light). We used a small whiteboard and pen and paper to take notes and do some planning. See photo gallery for some of the notes. Page 1 - We worked on a small flow chart of when and how the Hypur API socket connection would work and how they play into existing flow and processes. Page 2 - We talked a lot about options for locking down full invoices. We thought that it would be cool to add a couple new columns such as is_locked (1 or a 0) and locked_reason (why it is locked - Hypur, 3rd Party, Audit, Admin lock, ice-down date, etc.) - Shawn also had the idea to put an extra where clause on the updates that only allowed updates on non locked items. That would create a great fall back on the root or update level. - The other main topic was flagging and tagging data. The more we look at things, the more we are seeing more needs to be able to flag and tag items within the system. We need easy ways to flag things and then easy ways to search and pull reports based off of the flags. Page 3 - This page of notes dealt more with a task queue of sorts. We need a queue for the Hypur project but we could also use a queue for other internal adilas projects such as watchers, feeders, auto summing, stats, and gathering and collecting other information. We thought that it could be really cool if we had a web interface (load and unload the queue) and then have a full on software backend that could run longer or more processing intense pieces. Kind of a hybrid of sorts. See scan for some database ideas for the queue table. - Quote from Shawn - "Please help us as we are working to help other people have work to do." - a line from Shawn's lunch prayer. I liked it. - Part of the page has some notes about ways to organize and break things into smaller pieces. Think of Legos and building blocks. For example: basic pages (shells), black box access points for custom code, themes, skins, smaller component parts, world building levels, permissions (different levels), settings (different levels), cfc database and logic libraries, special page functions and player functions, watchers and feeders, documentation (help files or videos), histories and logs, real in-line database extensions, flags, tags, and subs. Also different data views and report types (calendar, time slot, horizontal, grouped, details, advanced - build & save your own reports), options for saving and exporting any data from any page. Page 4 - More looking into special flags and tags. Added some notes about special cases such as returns, vendor credits, customer credits, back orders, and general PO ordering processes. - We also talked about the task queue and being able to drill-down and see what is going on and what is queued up. We talked about a one-to-many between the queue and the action logs. We listed out a few of the possible queue action statuses - See scan for more info. Page 5 - Shawn and I took some time to talk about our process and how we want to treat and track our projects. Lots of funnels and sub funnels. There is a lot going on and lots of things to make sure and check. See the attached scan for a small visual of the brainstorming session. |