Open Roxie-32 opened 2 months ago
@Roxie-32 we need to get this on Stefano's desk.
Hi @snebo , can I get updates on this task?
In the last pull, a lot of duplicates/unnecessary files and collections were created, and the initials provided data from users module wasn't used wasn't used. I'd have to move, remove and reimplement some things to make it usable and scalable. I am still reviewing the existing code and haven't started on this yet
when a user register to be a lead, we have two different process to get this done,
First scenarios;
when we have a new user applying to be a lead directly using the application form, the users will need to supply all the information on the user table, and also the one for the leads module so it can be populated. This process entails that the user entity will be populated and the details from that will be used to populate the leads table so it can complete the registration of the user.
Second scenario;
when we have a registered user; there will be a button on the front end which will state apply to be a lead. In this process we already have the user details from the frontend, all the details will be sent to the backend.
USERID will be made option in the request and when it is being sent it will be used to pull out the record of the user, after being validated to be a correct user in the application. then the lead table will be populated.