Registered user adding their own users (thus registering them)
I would like to require email confirmation for both but for the latter, I would like to send a custom email template. It seems as though any registration will trigger the Confirmation template email—which I cannot disable if I want to preserve Require email confirmation. I would even be open to bypassing the email confirmation for the second type of user but I don’t know if that is possible.
Is there a way to either:
Require email confirmation while using either one of two different email templates?
Bypass the email confirmation requirement when using the User registration (via Codeless)?
In order to send out different emails, you need to register users differently. If you use the user registration API (regardless whether it is from code or using Codeless), it boils down to the same event which triggers the email. However, if you use the registration API for (1) and Database API for (2), then it would be possible to send out different emails. The first email type would be sent from an event handler for the Register user API and the second email would be sent from your Codeless logic.
This still triggers the Confirmation template email to be sent, as if using the Users API. I don’t want the standard registration email to be sent in this situation.
I apologize for misguiding you. I didn’t realize the database event of creating a user in the Users table triggers the email.
When a user registers someone else, does that call need to happen in Cloud Code? That’s the part that makes it very challenging. The reason is there is a rule that Backendless will not call Cloud Code for anything that got triggered from Cloud Code. For example, if you save a user from Codeless (or any other form of Cloud Code), the registration API event will not happen. If it did, it would be a solution for what you need. So my question is - does the second scenario, when a user registers someone else, need to happen on the server side or you can do it from the client?
I don’t have a preference for how the user registers someone else. I’ve tried both. I have tried a couple of Codeless approaches (Data API > Save Object in Backendless and Users API > Register User) but so far both have triggered the registration email. On the client, I’ve tried registering via the User and Data APIs.
Do both direct user registration and registering a user by another user on the client side. The former will use the Registration API and the latter will use the Data API.
Add afterRegister event handler in Business Logic. It will be called when the registration API is used. In that handler you will send out an email (using a custom template perhaps) to the users who register directly.
Add afterCreate event handler in Business Logic. The event handler should be created for the Users table. It will be called when the Data API is used to register a user by another user. You will need to add logic here as well to send out an email.
Thanks, Mark. That is a good approach but the tricky thing is that Backendless currently insists that in order to use Email Confirmation, I must use the Confirmation template. I am finding that limiting because I do want to use Email Confirmation… but I need to register users in two different ways that require different messaging.
Yes, the email confirmation toggle is coupled with Confirmation template. With the solution I proposed (2 event handlers for separate API events), you’d need to implement the email confirmation link in your business logic.
Unfortunatelly currently there is no way to chage userStatus from Codeless due to security reasons and internal logic constrains. We will discuss today possibility of extending API for covering your case.
Thank you. I’m interested to see what comes out of the conversation. For me, this was driven by my need to have control over the Confirmation template being sent only when I want it to (not on every User registration) while still being able to require users’ Email Confirmation. I hope that helps inform the discussion.
Unfortunately, there is no way to separate the registration process using build-in API, because it doesn’t matter which API you use to register a new user, BeforeRegister and BeforeCreateObject EventHandlers will be invoked for both cases below:
create a new User object using Data Service
register a new User using Users Service
However, we can propose you a workaround
create a new API Service to replicate the EmailConfirmation flow,
the API Service will be able to generate/store and verify the confirmation token
in your logic, you can request a new token for a particular user and send specific Email with the token
you can build the verification URL which will point to your app which in turn will send a request to verify it and change the user’s status
We have added an API for changing UserStatus which works only inside BussinessLogic, but it’s not released yet, I assume it will be released in a few days (BKNDLSS-21736)
To store these verification tokens you can use Data Service or Cache
Also, we are going to add another API for requesting the verification URL but it won’t be soon.
We’ve just updated cloud servers with a fix for the issue you described above. We have added a new Codeless block to solve your problem.
You can find it in the Users API section. https://monosnap.com/direct/Gtg0jse6RiSW7wW16e9nYlbgJaVAyv
