In looking at the demo, I see the "require a user to be logged in" button for the form. I'm guessing that means that the user will automatically be tied to the response entry when it is entered in the database.
This is true. The logged in user will be captured as part of the entry. The entry will be associated with that user.
I'm 80% sure you can do what I want with the developer license. Here's the basic Process flow:
1. User will be created by an admin from a phone call (User's cannot register themselves)
2. User will then log in and fill out additional demographic information
Where will they will out this demographic information? Will you create a form for them to submit, or will this be a form to update their profile?
3. User will go through a multi-part form to purchase a service with several add ons.
- choose main package
- choose add-ons (each with it's own pricing information)
4. User will "sign" disclosure (checkbox to verify reading)
5. User will pay for product through Authorize.net (will probably integrate with wooCommerce or cart66)
I can't help you with that. We can help add the product fields to the form and total it for checkout if you want to use Authorize.net or some other payment gateway for which you have an add-on, but a cart would have to be provided by other software.
4. User will have to checkout and pay for service
I am unclear what the form(s) in step 2 and 3 will do and how the information will be recorded, and what you need to do with it after that.
Posted 9 years ago on Tuesday April 9, 2013 | Permalink