Request
Donor Portal Sign Up Status: This is the new status that is needed in the for the donor record to allow hold the status of the donor’s sign up status, below are the status: Not invited, Invited, Signed up.
NetSuite to send out an email embedding the UUID generated on (4) with the donor portal link (Link Example: https://giving.cg.org.sg/donor/invite/{UUID})
NetSuite to generate a temporary UUID that represents the invitation intent that contain the donor’s ID. The UUID should have a Time to live of a specific duration (Suggested 3 days). The donor record’s Donor Portal Sign Up Status indicating that the donor is Invited.
Solutions
- When the user opens the Portal access URL, a validation API can be requested to NetSuite so as to identify if the Portal URL is not more than 3 days old from the Email sent date. Based on the NetSuite response Portal can allow or deny access to login. The customers that went through the login process will be given a new status of ‘Signed-Up’.
For Donors who haven’t logged in to the Portal even after sending the Portal access email, we will enable the Portal access button.
For this process, we need 2 API calls,- first for validating the Portal URL expiry (3 days condition) and
- the second is to inform NetSuite that the user has successfully set up the account and logged in. In this request, we will change the status to ‘Signed up’.
This method involves API calls from Portal to NetSuite only.
- Another solution involves API calls from NetSuite to Portal and Portal to NetSuite.
In this method, NetSuite will send an API request to Portal containing the data of the Donor ID as well as the Portal access email sent date & time.
So Portal can store the date and time. So during a Donor login, they can validate the User who opens the login URL within 3 days.
After a user successfully logs in, the Portal need to send an API to NetSuite informing that the user has successfully set up the account and logged in. In this request, we will change the status to ‘Signed up’.