allynalford / com.statuspilot.meteor.ui Goto Github PK

We need to build a tabbed form for data entry.

This form will be tabbed with 3 sections.

1. Customer information
2. IG Account Information
3. Billing information

The goal of this form is to allow the entry of data into the system for pre-validation.

1. The customer information will be saved to the Customer Collection as all customer information shall be. Upon completion of the form, the data entry user will click a button labeled next to move on to the next tab. This action should create the customer in both the customer collection and within Stripe for future billing purpose. In step 3 we will be adding a credit card to stripe for this customer and the customer must be tied to it.

2. The customer IG account will be tied to the customer just created. This form will capture all the information needed to setup the IG account within the system. Upon completion the data entry user clicks a button labeled next that takes them to the next tab. Upon this action taken, the IG account information is saved to the IG collection as in active and unvalidated.

3. On the final tabbed labeled billing, we will capture the billing information for credit card processing. Of course we can use the existing form again. Once the data entry user has completed the data entry. The information is saved to Stripe and an ID for the CC information is added to the customer collection for future billing. The data entry user simple clicks done and are presented with a success message if all goes well. Then presented with a clean form for the next entry.

Change IG accounts page to a list of accounts in a table. Selecting an account should take them to the page to edit the settings and view detailed information about the account.

We need to add a new role to the system for users that only enter data via a new form(s) we will create to capture information to avoid duplicate data entry.

Let's fork the repo so that we have the original code. As we need to change the flow of the site a bit. as it's now going to be used by account managers and not general users.
so here are the changes to the new site.

So we will have to different sites now.

• on the register page, remove the IG fields. IG accounts will only be added thru the dashboard add account method.
• Upon registration via the register page. The account is in the Account Manager role.
• add a company name to the profile.
• We will move the stripe payment page to be within the dashboard. After an account is added, the payment page should show up to make payment for the new IG account.

• username naming validation
• strong password validation

mongodb://:@ds161913.mlab.com:61913/statuspilot

Sync up with Andrey and the data structure needed or the service.

Sync with Andrey about getting and setting password in the master_app backend

Account managers will have the ability to create customers and add IG accounts to them
Customers collection is only for tracking now. The payment will be done by Account managers.

Publishable key: pk_test_8LOPFgX1zgS6qMwpGFrmaCt9
key: sk_test_Xlvot5lSlBLb313mOMpaMrjH

• follow_user_followers (Check box to activate, Open Text Paragraph field for user names, amount int field)
• like_timeline (Check box to activate, amount int field)
• follow_by_location (Check box to activate, Open Text Paragraph field for locations , amount int field)
• follow_likers_by_location (Check box to activate, Open Text Paragraph field for locations , amount int field)
• like_likers_by_location (Check box to activate, Open Text Paragraph field for locations , amount int field)
• Direct_message_followers (Check box to activate, Open Text Paragraph field for locations , amount int field)
• Direct_message_new_followers (Check box to activate, Open Text Paragraph field for locations , amount int field)

Features should be listed as UI elements.
These features correspond with the service features and elements of the data structure that is required by the broker service.

Set an expiry time in mongo lastPayDate key, so it will automatically expire after a certain amount of time eg. 30 days, depending on selected subscription. If someone pays again before subscriptions end, we can just add the extra time with the previous expiration time.

Use Bert.alert() for different events to notify users: https://github.com/themeteorchef/bert/

Currently, we are setting a session to hold the value for which IG accounts customers are paying, we can simply set up a router with IG collections _id to the template to avoid conflict in payment.

Ability to load different payment processor form based on flags.
Stripe is the only payment processor now, we will add more choices later.

We need to add a box to the IG account UI to be able to add locations. These locations should be added to the "features.like_medias_by_location.bot_params.locations" array.

We will be adding features, one which will be follow_users_by_location.

This feature will also need a list of locations. I think we should have an extra box for this. Labeled locations users to follow or something like that.

So add a similar structure to the IG collection named "features.follow_by_location"

As an admin i should be able to activate and de-activate accounts via the UI..

Please add a checkbox or drop downbox to take this action via. Only admins and the account creator should be able to modify this flag.