all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
-A shopping bag or grocery bag is a great one-to-many analogy. I was trying to bring things into my house and had a huge full arm load. I was using both hands, arms, and chin. Then I thought, man, if I just had a grocery bag or two this would be easy. The more I thought about it… the more I think it could be a good one-to-many relationship example. All you need is a small container to hold the pieces… -See sketches in photo gallery: Person trying to hold all of the pieces – too many to manage. VS Good use of a one-to-many relationship: Person using a container (shopping bag) to hold smaller details or items. -We had another request to show grouped data per day. They wanted the daily, weekly, and monthly totals. Basically, they wanted the financial history homepage report that will show data specific totals based on categories. See notes from 9/12/13 in adilas university for info on the financial history report. Commission Structure for 3rd Party Solutions: • To adilas: a. 20% • To 3rd Party: a. 80% • What: a. External solution. They bill the client. Then they pay us back 20%. • To adilas: a. 30% • To 3rd Party: a. 70% • What: a. External solution. We handle all the billing. We pay the 70% back to them. • To adilas: a. 40% • To 3rd Party: a. 60% • What: a. Internal solution. We host the files, pages, and apps. We handle all the billing. We then pay the 60% back to the vendors. Usually, this is an adilas developer that creates an internal 3rd party solution. • To adilas: a. 50% • To 3rd Party: a. 50% • What: a. Internal solution. We host the files, pages, and apps. We handle all the billing. The developers create, makes and does the maintenance on the project. We handle all the billing and pay back the 50% commission back to the developers. This is an option for adilas developers who basically make the app or feature happen and then maintain it. The original work and effort are on the developer. The maintenance also falls on the developer. They also get a perfect 50/50 split of the revenue. |