dustins_adilas_notes.txt =================================================================================================================================================================== Dev Query: -There is an issue with news_and_updates.cfm where if you narrow the page, the buttons no longer work. Also, when all of the header columns(links) are used(in snow owl) =================================================================================================================================================================== News and Updates: (4,5) -Like Montana, report API Keys that have been awarded for each state. -Report that we are working on the transfer page and seek out beta testers. -Per function news and update to help users understand how to use each one with link on the corrosponding page. -Add a new display photo to the Montana news and update. Suggest that he put the metrc logo on a handheld device image and a laptop image. -New Labling Rules M and R 1001-1, 1002-1, 1003-1. Need to parse out the differences and see how this affects labels. =================================================================================================================================================================== Emails: -Email Danny to schedule a time to work on the distillate label (At least find out if he has done any work on it and if not,let him know that I am jumping in.) Find the label and add the fields into it. (variables, params etc.) 1. Find the right label page. 2. Check the variables from the pdf. 3. On the page. Add to the page notes with my changes (be specific). Possibly rename the variable on the pdf if there is already a relevent var. -Connect with Renee about using her system to test the transfer piece. Compile for her a list of all of the information needed for a transfer post for both the sending and receiving location. That way we can produce some mock packages and stage them for transfer. (Keep it short and sweet!) (2,3) we will need: ID Number, Manifest Number, Shipper Facility License Number, Shipper facility name, Name(null), Transporter facility licence Number, Transporter facility name, Driver name, Driver occupational license number, driver vehicle license number, vehicle make, vehicle model, vehicle license plate number, delivery count, received delivery count, package countm, received package count, created date and time, Created by user name (null), Last modified date and time, delivery id, recipent facility license number, recipient facility name, shipment type name, shipment transaction type, estimated departure date and time, actual departure date and time (null), estimated arrival date and time, actual arrival date and time (null), delivery package count, delivery received package count received date and time. "Id": 1, "ManifestNumber": "0000000001", "ShipperFacilityLicenseNumber": "123-ABC", "ShipperFacilityName": "Lofty Med-Cultivation B", "Name": null, "TransporterFacilityLicenseNumber": "123-ABC", "TransporterFacilityName": "Lofty Med-Dispensary", "DriverName": "X", "DriverOccupationalLicenseNumber": "", "DriverVehicleLicenseNumber": "", "VehicleMake": "X", "VehicleModel": "X", "VehicleLicensePlateNumber": "X", "DeliveryCount": 0, "ReceivedDeliveryCount": 0, "PackageCount": 7, "ReceivedPackageCount": 0, "CreatedDateTime": "2016-10-10T08:20:45-06:00", "CreatedByUserName": null, "LastModified": "0001-01-01T00:00:00+00:00", "DeliveryId": 1, "RecipientFacilityLicenseNumber": "123-ABC", "RecipientFacilityName": "Lofty Med-Cultivation A", "ShipmentTypeName": "Transfer", "ShipmentTransactionType": "Standard", "EstimatedDepartureDateTime": "2016-10-11T14:48:30.000", "ActualDepartureDateTime": null, "EstimatedArrivalDateTime": "2016-10-11T16:50:00.000", "ActualArrivalDateTime": null, "DeliveryPackageCount": 7, "DeliveryReceivedPackageCount": 0, "ReceivedDateTime": "2016-10-11T16:42:19-06:00" =================================================================================================================================================================== Pages: production_home_page.cfm: -colaborate with Steve on this. He knows what needs to be done. (4,5) metrc_dispensary_homepage.cfm: -remove active and inactive plant batches from more options. (2,3) -make the edit link "smart" by giving it the ability to have a button pop up that allows them to sync changes with metrc. (1) -put some space between the card and the results columns. (7) -move the "update inventory csv" button so that it is between "add new inventory" and "transfers" buttons. (2,3) -we need to talk to Alan about pushing the amount of time before the metrc query returns a id number. (to 5 minutes) metric_dispensary_csv_homepage.cfm -extra closing div tag on/near line 806 needs to find its mate. (1) -Temperarly put in a warning in the form of a note. Also, link to the news and updates and meke it state that csv files should only be submitted once, so only do it after all sales are completed each day. (Need to think about the best way to convey this without being hamfisted. that only allows to be seen in CO) (1) cannabis_plants.cfm -Select All checkbox is not working. (1,2) -update mother plant id so it only goes 2 integers past the decimal point. (2,3) -In the "Change Phase on Selected Plants" note. Add in the number of plants being acted on. Also on the related pages. -Validate that users are not choosing a future date for phase changes. -Add in the ability to kill columns that are not needed. cannabis_plant_batch_add.cfm -make "Mother Plant" dynamic so we can pass in other types like "seed from", "manifest number" or "package number", etc (7,8) metrc_inventory_update_csv.cfm -validation needed: error message when notes field is empty. (3,4) adilas_third_patry_solutions.cfm -need to add functionality that allows for selected employees to have their own API keys. (2,3) cannabis_packaging.cfm -need to write some javascript that automatically calculates the leaf/trim as well as a setting that lets users select how they want to parse the product. (2,3) metrc_get_endpoints_home.cfm -add GET for package adjustments. (3,4) mmj_operations.cfm -major cleanup and redesign - it would be nice if that this page worked with subs. I would also like to be able to see it over a date range (instead of just one day). =================================================================================================================================================================== General To Do's: Need to Have each page check for the color of the background and adjust the card to be a lighter complimentary color (universal). (4,5) Need to have api key capability for each employee that performs metrc api interaction. Need to set up custom permission setting capabilities so that they can set permissions for multiple employees over time without having to do a redundant process. Themes and standardized user type templates. Make a excel or csv spreadsheet that templates the fields needed for api integration to give to a customer to fill out. Maybe a master list that passes in all of the general fields and passes over unneeded fields based on customer needs. Need a graphical repesentation of the entire seed to sale process with tie-ins to each adilas feature/tool. Need predictive on the search vendor field on the add/edit page. Need to have customer password fields auto-populate wherever needed. (e-commerce) Need to have a set to default button on the nav menu for setting any page as a default homepage. Need to have a toolbar button for page relevent tips and tricks with links to news and updates. Need to update how people reset thier login attempts: lets add a captcha or at least put the copy paste link on the same page. Maybe two step varification would work. When you are switching corps, instead of needing to click on the little box link, make it so that you can click on anywhere on the corp piece. Need to have UOM type indicators on any field that holds wieghts. In most cases this could probably be hard coded. Need to create the ability to check a box that opens all of the subs for inventory search for adding to cart. =================================================================================================================================================================== General Notes: Try to spend an hour or two per week with Russell taking a look at look and feel stuff. Have him show me the bootstrap pages tied into Snow Owl and see what looks good and will work in other pages. Invoices for Adilas go to craig@adilas.biz (Once per week) The page where State API keys go: adilas_third_party_solutions_action.cfm Play site: corp name: Cannabis User: bobmarley PW: 1234 Works on all servers: corp name: Adilas User: Guest PW: 1234 =================================================================================================================================================================== Labels: -Kelly Wants: Avery, Dymo, Zebra, and Continous functionality. -Have steve show me how to put it together. - Look to see which fields need to be dynamic so Steve can help me get started. Steve is rolling with this right now, my goal is to get the page name and URL for the custom labels. Go to edit mode on PO for PDF link on child po. (edit_po_line_items w/corp id.) (PDF link page.) (1) Parse out the variables from the url (easy data), read each page and see if I can find the hard data. Page Name: doc_form_989__medical_sub_po_label.cfm: -Variables: (subInvId=13818, partNumber=Distillate%20Cartridge%20-%20Tijuana%20-%20500mcL, subQuantity=1.00, partCategoryId=4455, vendorName= partId=343321, vendorPayeeId=51713, partWeight=.5, poDateReceived=5/26/2018) doc_form_989__medical_package_label.cfm -Variables: (subInvId=13818, partNumber=Distillate%20Cartridge%20-%20Tijuana%20-%20500mcL, subQuantity=1.00, partCategoryId=4455, vendorName= partId=343321, vendorPayeeId=51713, partWeight=.5, poDateReceived=5/26/2018, id=8356) doc_form_989__item_sub_po_label.cfm -Variables: (subInvId=13818, partNumber=Distillate%20Cartridge%20-%20Tijuana%20-%20500mcL, subQuantity=1.00, partCategoryId=4455, vendorName= partId=343321, vendorPayeeId=51713, partWeight=.5, poDateReceived=5/26/2018, id=8356) doc_form_989_bulk_sub_po_label.cfm: -Variables: (subInvId=13785, partNumber=Dr%2E%20Rogue%20OG, subQuantity=0.00, partCategoryId=4292, vendorName=, partId=337203, vendorPayeeId=51713, partWeight=, poDateReceived=5/24/2018, id=8354) po_line_items_body_989.cfm - this page is where I find the links and dynamic URL data - follow those variables to see what is passing to the label pdfs Ask Steve: How does adilasDewyDecimal work? Steps for building a po_line_items_body page: 1. Check for a auto redirect and show a success message. 2. Build the page with a form that passes in the url, checks for photos and thumbnails, checks the media/content results, provides a link to the print friendly page and buttons for editing, printing, menu, etc. 3. if statements that uses querys to check to see if the line item amounts match and privide a link to a printable version. Also, provide the ability to parse out the different pieces of the PO. 4. Check for various permissions and display accordingly: Internal build po, admin, edit mode, flex grid, photo management, add/edit, media/content, basic payables. Chek the bulk flip options, query the details and display varifications. If there are at least 2 line items and if so, allow permissons. 5. Grab existing media/content pieces. Grab links to help files, label wizard, etc. 6. Grab the add/edit PO line items page. Links to create new purchase orders, and recent activity. 7. Grab a mini search page and query to display the details with links for adding items. *8. (line 446) if statement that checks for special requests, vender Id, business name, vendors etc. and pass in data: parts, vendor payee id, corp id, po date recieved, po number, po type id, store id, and use part search. *9. (line 498) else statement for internal build po and get the same info from inputs as from 8. *10. (line 583) Grab Vendor info, User info, Po info, Vendor/payee details, location, store name, po number, address, varification, PO amount, etc. 10. Check for math issues, and what flag message to show if there are issues. *11. (line 639) Query and display city state and zip, who created the po, the creation date, account number, recieved by, date recieved, phone number types (lots of length, trim stuff to get the format right), dynamic po name types, external reference and invoice numbers, if the po is paid, and notes. 12. Check to see if there are any po's and if none. display a message and abort. 13: Output: display line items, request po's with links to go live. PO line items, running total, remaining amount, quantity, cost, rounding, extended, location, part number, labels, vendor, Unit of measure, bin num, description, line, sort. 14: Output: Sub inventory: PO info, current corp id, category id, message and extra text. 15: Find the total child count. 16: check for voided status and admin permissins. 17: Check for a request po and display line items with item cost, rounding errors. Check for user type. 18: Query to grab the part weight. 19: Generate a barcode and display prices, and generate URL link to the barcode generator. 20: display username, UOM, bin num, RFID tag, etc. 21: display subs with quatity, cost, price, description, sub id num, time id, attr name, total quantity, parent quantity sub inventory id, sub ref id, date planted, current corp, . Loop over the data to display. 22: Check for voided status and if no, then show drill downs. *23: (line 1132) display the pdf label links and pass in the data via url based on the dynamic variables that need to pass to that label. 24: Check for cost disconnect, new or sub package, using RFID tags, if there should be a link to elements of time. *25: (line 1385) Loop over the attributes to generate the variables to pass to the label. Check for errors and reset the counter variable. 26: Display rows, check for unlocked po's, loop over line items and perform varification. 27: Provide a link to an edit/add form and show form. Provide link to special requests and loop through vendor data and grab the values tied to the vars. 28: Check if in add mode and provide a forms to search for part numbers or part names and add in the search data. 29: Check if in edit mode and provide forms for editing existing data. 30: check to see if the rfid tag number should be displayed. *31: (line 1796) provide a form for adding sub inventory and use inputes to create instances of the variables *32: (line 1833) Check if internal build po and provid eform for adding in recipes and generate instance of the variables. =================================================================================================================================================================== Word press notes: Review and Edit: - Janna - She will review and edit posts before they are uploaded. Email her the link provided at the top of the post. - Russell - He can add display images and review video. Ultimatly Janna will have him upload posts once she is done editing. -How to sign in to WordPress: Sign in to Adilas inc. Click last Icon on footer of homepage -Images: should be JPG (or png), sized 1024X 852 - Select Better Quality at about %80. -Tabs: only add tabs if it is very important and ask Steve first. -Categories: Select relevent categories so that users can find updates. Generally I'll be using "cannabis", "general news and updates", "mj tips and tricks" and "help files". -Dates: Choose a date that fits where in the news and updates I want it to fall. If I want it on top, use todays date. -Video: Send video off to Russel to edit and review. =================================================================================================================================================================== Future Development: "Pop In Notices" that only show up when something has changed so people know about it. Object Orientation: Mobile endless scroll, User specificity, etc. Anywhere that we need to hit the back button in order to do multiple entries, we should have a submit type button instead that appends the data to the page. Custom Validation Form: So a corp can specify what they need validated. ie.: what fields need to be filled out every time. Adilas social/work profile and networking: connect super users with clients in need. On Rails: Have Modals (or something) that guides users through processes and sets up new users. Segmentation: Parse out the different pieces of Adilas based on specificity of use so that users only need to interact with relevent sections. Sell individually or as a suite. Adilas API for utilization on other apps. City/State mandate and integration. =================================================================================================================================================================== Snippits: