all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Uploaded Media/Content & Other Files
(2)
|
||||
| Media Name | File Type | Date | Description | |
| itunes_build_your_own_play_list.jpg | Image/JPEG | 2/22/2017 | iTunes custom configuration for a user-driven play list. Idea for building logic and criteria for loyalty points and special accounts. | |
| special_account_tracking_ideas.jpg | Image/JPEG | 2/22/2017 | idea on tracking special accounts such as loyalty points. | |
|
Notes:
|
|
We started out the GoToMeeting talking with Alan about MySQL and database stuff. I then helped Steve with some custom reports. Recording notes from yesterday and getting things semi-caught up. I then jumped in and did some research on database project for the world building piece. Lots of good data on element of time id # 2333. Eric joined us around 11 am to talk about loyalty points and special accounts. - Eric would like to keep it simple. - A possible configuration form - stored in JSON. The JSON would then work with a service layer. The service layers could then have a version number. The JSON would hold all of the setup values that are needed. Basically one record per special account type. - Continue calculating points based on sales. - We talked about global start dates vs. start dates per account. - Other fields we may want to track... - >>> corp, name of the account, what item loads it, what item unloads it, factors (multiplier), quantity based, dollar based, what type of account (asset, liability, virtual), account number, description, customer, vendor, user, generic person, running total, exceptions, start dates, end dates, conditions (rules), extra flags, etc. - Eric would like to use some simple lists and SQL in statements. This could be lists of items, categories, customer types, etc. Simple lists that hold multiple pieces. - We want the users to define their own program and setup the rules. This concept would also translate into the smart cart logic. User-facing and configurable options. - Eric uses iTunes and would like to make a similar type function to allow the users to setup their own rules and such. Each data fields has options such as contains, ends with, does not contain, is great than, less than, equal to, like... etc. They you set the criteria. You basically get to add as many new rules as you need. Add as many rules and criteria as needed. You can set limits and control other values. - Eric is thinking about customer types, discounts, exclusions (items and quantities), inclusions (items and quantities), item categories (include or exclude), date ranges, time ranges, ratios, limits, reusable, etc. What about multi-level cascading criteria such as referral programs, direct sales, affiliate programs, etc. - We are maybe seeing 3 tables: main accounts, account criteria settings, and account transactions. A fourth table might be for sales and special promotions. This needs to be thought out a bit more. - What about rounding for points and credits? Round things, don't round things, what are the settings. - What about data qualifications such as only use customers that have a valid email, cell phone, and address. Otherwise, they don't qualify. - What about data over rides. If x field has y value, this either allows or doesn't allow things to happen based on that data value. Basically, a data driven value that either allows and/or denies certain logic to play out. - What about combining points and credits over multiple corps. We might have lists of corps, lists of items, lists of part categories, lists of customer types, etc. We need to allow for cross corp stuff and allow them to write things into the code. They will need to look up Id's and build the correct lists. Also, we need to validate that corp x can and should be able to talk with corp y. They also need to be on the same server (as of right now). We may need to allow for cross corp passwords or special fields that have the same value (kinda like a virtual password or acceptance option). We then need to total up points and credits for multiple corps. That could be a little bit funky. What about recording the details. We need to keep running totals to allow this to work fully. As a side note, we may do this in a later version. Maybe just stick to single corp stuff for right now. We do need to look at cross corp security and allowing cross corp actions. We already have some of this built in for cross corp sales, PO's, invoices, etc. Look into that. - Think of the bell curve model - develop to the peak and basic audience first. Then look at the outside pieces as custom and/or extensions. - Sub criteria drop-down options: inventory items, item categories, customer id's, customer types, special fields (state, license number, customer tax id, cell phone, email, home phone, terms, etc.). As a side note, what about date/time features. - Eric could end up helping clients setup their more complicated rewards and special account stuff. - Do things run out and/or how do you flush things? Say points earned but not used and then the program ending or something like that. What about transfer of points and/or credits? - What about doubling points during certain sales and/or promotions. What about more rules based on date/time stuff. - We are still seeing that promotions and/or special sales need to be a separate table. We would then need to tie into those tables. - Eric started talking about aggregate functions, analytics, and other business intelligence models. We could help them see the traction and/or activity on sales, promotions, campaigns, etc. Data and the analytics are huge... :) - On the analytics, dashboards, and summary reports we need to move away from the transactional data and show more of the summary and aggregate data. We are seeing this need on all fronts. |