Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 2/28/2019 10:24 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 4446
Template/Type: Brandon Time
Title/Caption: Adilas Time
Start Date/Time: 3/7/2019 9:00 am
End Date/Time: 3/7/2019 1:30 pm
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

Steve and Alan were talking about frontend automation on the credit card side of things. We are looking into API sockets for USAePay (our credit card gateway that we are using) and being able to pull reports that show customer credit cards that have expired, will expire, or expire during a set date range. It would be super cool to get this information in order to help our billing department.

- Steve is really excited to see what the AWS (all of the stats and such) side of things will bring to the table. We really want switch our billing based on storage, throughput, bandwidth, requests, etc. That would be awesome.

- Two parts, the gateway side and the adilas side of things... we need the header and app side of the communication process (extension of the invoice due date project). The goal there is to use adilas and be able to communicate back to the users (different companies) and let them know if their invoices are getting to a certain age. Based on settings, the goal is to warn and help get a payment and if needed, to shut off and prompt for payment before usage resumes. There are more details, but that is the general idea.

------

Got on a Zoom session with Calvin. He was having a problem with an existing API socket. As he was looking deeper, we recently made a number of changes to that page back in January. It is dealing with sub inventory, searches, and calculating sub inventory quantities. I scheduled an hour, later today, to look into his question.

------

About 11 am, Steve, Bryan, and I got on a meeting to look at Bryan's adilas community projects page. This is an area where adilas users and consultants can submit and vote for what projects they want us to work on. Basically a way to get outside input on priorities and what is needed and wanted. Steve sees some of this as each user having their own little individual user account (almost outside of adilas). They then could do whatever they need to outside of any specific corporation, just as a user. When they want to go in and do some work, they would need to enter a corporation and/or world. Basically creating a separation between users and worlds (adilas accounts).

Some of our conversations turned to possible misuse, abuse, rants, and managing potential problems. In a way, it is almost like opening up a virtual forum and public facing entry point. We also talked about design and styling out the page to make things look more modern. It is crazy how deep, sometimes just a single decision goes to crazy deep levels, and it is hard to see what is going to happen. Lots of cause and effect decisions. Steve was talking about how the look and feel almost helps guide the process. How well does it show? Do people want to spend time doing something that looks old? If it looks modern and smooth, would they use it more? What do people accept? What do people want?

After the discussion about look and feel, Steve ended up back on the master user accounts topic and being able to use a single sign-in type interface. This deals with users being able to independently use certain functionality outside of an assigned corporation. We also talked about being able to submit projects and notes and having some sort of sign-off and/or approval type process.

We also talked about timelines and being able to show other projects, ideas, completion rates, what project are on target and/or in progress, and other ways of communicating as to what is going on. Long story made short, we love the ideas and concepts, but it still needs some loving and direction. Eventually, we want to open this adilas community forum and community projects to all users and consultants.

-------

Talking with Wayne about the new open/general login process. He was talking about an open id (somewhat of a master user id - a hashed username string). We were talking about questions about what happens if a user gets setup but hasn't been associated to a specific world and/or a corporation? How do we allow those assignments to be made, requested, and eventually approved. Wayne was talking about an authorization queue and a way to approve and allow access to certain users.

------

Worked with Dustin on adding new entries in the sub GPS/RFID tag table. This is a sub of elements of time. He is tying things into his cultivation and production pages.