Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Pink
Assigned To: Charles Swann
Created By: Cory Warden
Created Date/Time: 10/5/2020 11:08 am
 
Action Status: Completed
Show On The Web: Yes - (public)
Priority: 0
Finished/Done: Yes - 4/14/2021 2:43 pm
Finished/Done By: Cory Warden
Budgeted/Estimated Value: 0.00  
Actual/Real Value: 0.00   [donate]
Invoice/Quote Status: Blank (n/a)
General Amount: $0.00
 
Time Id: 1880
Template/Type: Community Funded Projects
Title/Caption: SARS USA Templates
Start Date: 10/5/2020
End Date: Unknown... (open or blank)
Total Time: Unknown... (open or blank)
Target/Due Date: 10/5/2020
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

As of 2/3/21: $4984

10/5/2020: Created for Charles billing for templates

See sub notes for more details.


Additional Comments/Notes - Subs (1)
Title/Caption Date Time Done By Comment/Note
Meeting on 10/5/20 10/5/2020 3:33 pm Brandon Moore

Chuck, Danny, Steve, and Brandon were on the meeting.

Chuck had some quick and dirty mock-ups. We also talked about some light flow and where things would be hosted.

- Maybe a new site. Just an idea. They may already have one coming.

- Chuck had 4 pages in the mock-up. We also talked about hosting those pages on their server (normal HTML and CSS) and then we would handle the brain portion (ColdFusion code). We can configure this in lots of ways, more than just one way to skin the cat.

- The templates that Bill has are more like email questionnaires.

- We do need to capture and store the info based on the customer. We may have customers with multiple registrations that need to be kept on file.

- We for sure need to capture the info and then send an email out to the client. On the email stuff... we can do an address like sar.usa@adilas.biz right now. We could also setup some auto forwarding to them at some other custom email address.

- The customers will be real customers in the system. There were some talks about storing info in JSON objects or real flex grid or flex attributes. Leaning towards flex grid.

- We also heard something about an image - sales receipt or some other image or copy of specific paperwork.

- As these transactions happen, we collect the data, we send an email, we then setup an element of time to start tracking the virtual work order or ticket (whatever is needed for the firearm).

- Currently, he is getting 40+ emails a day. We want to switch that load over to real data being caught inside of adilas. Then we help him advance the ball via a data assembly line type process inside the system. As they progress, through elements of time, we stamp and advance the ball.

- Somewhat of an end goal is automation and diversify who touches what. Currently, Bill is the main gatekeeper. We need to catch the info and then spread that info where it is needed.

- Currently, we are seeing between 10-20 different models. We could do some sort of photo/grid where they could click on a gun/pistol and then we could auto populate the related data into the registration forms. This could be done by a look-up or just passing it along in the URL/web address from the picture gallery. Looking ahead... if they get a bunch more, we could build other nav on top - such as pistol, shotgun, ar's, rifle, etc. We may start small and then build as needed. Our current scope is just the pistols.

- Some of the pistols look very similar (family or main model) however, there are differences. We may need pictures and/or text search options. We want to make it as easy as possible (few clicks and less typing). Maybe do top level filters such as pistol, rifle, shotgun and then ask for the caliber. Maybe build as if we are headed here, but hide the pistol selection for now... keep it simple.

- Flex grid is already ready to handle one-to-many relationships. It is searchable and we can configure the verbage. Already exists.

- Link from Chuck to basic mock-up: https://xd.adobe.com/view/254b3d41-db95-4c9b-be8a-72db1c717c72-7018/?fullscreen