Upgrading and additional details.

We have several membership levels and allow upgrades upwards. All of the application forms contain different fields so the Full membership requires more detailed information that the Basic, for example. How do I force a user to complete the registration form relevant to their new, desired level and collect this information? At present it just requires a payment and nothing more.
Thanks

Under the Workflows tab you can set plans to hide fields that aren't relevant to that plan during registration. You can also use CB Conditional for this as it supports CB Paid Subscriptions plan conditioning. For profile edit you can use CBSubs Fields Tabs integration or CB Conditional. So for existing users you would need to collect that information after payment.

There is no way to require and capture additional fields during payment without developing a CBSubs integration plugin specifically to do that. In a future release we'll be implementing support for capturing additional required field data during payment, but that won't be until after CB 3.x as currently our fieldtypes are profile specific but in CB 3.x they'll just be generic reusable Joomla fieldtype plugins.

OK thanks. I already hide certain fields at registration but it would have been nice to collect further data upon upgrade.

Is it possible then to have the upgrade paused pending approval? Some members might not be qualified for upgrading.

No, there's no functionality to force a payment to pause then collection information then collect payment.

Typically the way you'd deal with this is it sounds like you may have different profile types. So you'd have a select field for them to select their profile type. This would then present fields via CB Conditional to collect whatever information you need. This profile type would also be used to condition plans in CBSubs to only show plans relevant to their type.

If you can provide how you're trying to use subscriptions with profile data I can try and provide a more accurate recommendation.

OK how about using Auto Actions to change the Approved status to Unapproved following an upgrade? This would allow me to pull out the upgrades as a user list.

I tried with one example but it didn't work using the trigger OnAfterUserApproval, conditions - any plan after upgrade and setting the Approved field to 0.