Has any one implemented moderated self-registration?

  1. How to activate-deactivate access to registered user?
  2. Is it better to duplicate BO that is self registering? So When user registered BO "DuplicatedUserBO" is created. Then when it moderated-approved - the actual "UserBO" is created filled WITH data from "DuplicatedUserBO" .

Yes this is how we are implementing it:

Create a BO "ApplicationToBecomeAUser" with an attribute "ApplicationStatus" which is defaulted to "Application Made"

Rule on New: notify the administrator about the new application. Include the URL to the form in the e-mail. (The manual has a set of URL "commands" you can use for this.)

Rule on Modify: If ApplicationStatus is "Approved" Create a new User and copy all the details from the ApplicationToBecomeAUser including preferred login name and password. You may need to add some code to ensure the loginname is unique.

If "Rejected" notify applicant.

On the User BO have a rule on New: Notify the User with an e-mail. Include the (new) login name in the mail.

Both BO's should be "intelligent".

The administrator will receive a notification about the new application and then click through on the URL to change the Application Status to Approved or Rejected. The rule on the User BO will now notify the user.

Thank you very much, pniehaus! I will try it that way.

What do you think is a better way to close access then to userBO?
Process that sets access level to undefined?

7 days later

Not sure if I understand your question.
Remember the rules around Guest access for the application BO. You must give access to the Guest level to the BO as well as to the attributes within the BO. Also don't forget read only access to related BOs (attributes with a BO type)