Community > Ideas
56 views
Under Review

Add "Set Account Settings To..." option in the Actions of On Form Submission-->DNN

USE CASE

For some security reasons, the clients wish to disallow any new portal users added via DNN native registration and to set the security DNN Registrations = NONE . All submissions are to be made using the Mandeeps Live Forms which we hope to be fully automated. 

The applicant would complete form, successfully pay their membership fee and -- meeting certain form-based criteria -- automatically become AUTHORIZED = 'true' users // while other form criteria would indicate their user account/profile be created, but remain Unauthorized. For example, as an international organization, some users wish to apply for membership but live in countries that are not supported by PayPal, or they do not own Credit Cards, and must pay via a check in the mail. We would like the form to be able to make the CC payment OPTIONAL, and offer the choices  "Pay Now via PayPal" --> Authorized User // or "Pay via Check" that results in an Unauthorized user.

A Second Use Case would be for the Membership Secretary to have a LiveForm to update a member's membership account - to change various profile data AS WELL AS move their User Authorization (or other settings) to a different status. (A LiveForm is preferable for low-skill volunteers  vs. teaching them how to use and giving them admin access to the actual DNN User application.)

While this MIGHT be able to be accomplished by some SQL action, having it as an easy-to-complete DNN ACTION would make the LiveForms so much more functional in options for payments related to portal access. I would imagine a similar situation would arise in the eCommerce application too.

The Action would need to apply if the form has a Register or Update Profile Action and reference the UserID pointer established in the form. Then it would offer the DNN choices of status: AUTHORIZED, UNAUTHORIZED, VERIFY or "NO CHANGE"// 

  • (I would not want to have the option for SUPERUSER !! too much power in the form!)
  • (VERIFY EMAIL might be a challenge in this action, as it requires the applicant to get a system-generated email with a code/link. This Registration status might have to be a separate Action because it requires an email editor, etc. --or-- in the  EMAIL ALERTS options?)

While we are at it, the form should also offer changes to the Account Settings status parameters

  • Set Lockout Status: (restore to 'false')
  • Set Update Password: true // false [force password update]
  • Set Is Deleted: true // false [soft delete]
David Loofbourrow David Loofbourrow
published 12/14/2020 19:57
Add Comment
Last Activity 12/14/2020 19:57