devdocs/specs/core-license-key-system.txt

@@ -43,12 +43,15 @@ FOR CODE:
 		- This request is stored in the db because it may need to be re-sent later on subsequent erasure of biz data
 		- RAVEN makes and stores internally into a new DB a DBID value which uniquely identifies *THAT* database installation	
 		- RAVEN transmits the request details (with dbid value) to ROCKFISH 
-		- RAVEN starts a repeating job that will periodically check the ROCKFISH server for a license response
+		
 	- ROCKFISH validates the request by verifying the email address provided is (is still) valid and by getting our approval after that.
-		- Verifies email by sending an email and waiting for a response to verify the email is valid
-		- If the email is valid then it creates a trial request record for us to view and approve or not approve with cause entered as text
-			- This part we might automate in future but for now it's a good "fuse"
-		- The DBID value is associated permanently with a site in ROCKFISH 
+		- Verifies email by sending an email with a special trial code they need to enter into the license page which indicates they received the message and the email address is valid.
+		- When they successfully enter the trial code and it vets as good (just some simple checksum system, nothing fancy at all, just needs to be uniqueish and confirm valid, probably part of an epoch timestamp) 
+		- If the code is good then the email is valid so the RAVEN server contacts an api route to confirm the code was entered properly which then triggers the rest of the ROCKFISH process
+		- If the code is good then RAVEN starts a repeating job that will periodically check the ROCKFISH server for a license response
+		- If the email is valid then it creates a trial request record for us to view and approve or not approve with cause entered as text which will be sent to the user (like don't use fake names or profanity or something similar)
+			- This part we WILL automate in future but for now it's a good "fuse"
+		- The DBID value is associated permanently as a SITE in ROCKFISH 
 	- We get a notification of a request sitting in ROCKFISH and we approve it or not
 		- IF APPROVED:
 			- ROCKFISH generates (or looks up if repeat) a customer record, flags it as a trial type customer with a created date (for later GDPR removal or turning into a real customer record)
@@ -56,11 +59,13 @@ FOR CODE:
 			- ROCKFISH stores the DBID value in the SITE record
 			- ROCKFISH generates a valid TRIAL license DBID code is the temporary fetch code.  
 			- ROCKFISH Ultimately should do this automatically unless we specifically flag something
+			- CLIENT LICENSE PAGE UI if refreshed or auto refreshed or whatever it will do updates the status showing licensed trial and expiry date etc
 		- IF NOT APPROVED 
-			- ROCKFISH creates a not approved type of license with the fetch code
+			- ROCKFISH creates a not approved type of license with the fetch code so that the server will stop polling
+			- CLIENT DISPLAYS the not approved message right in the UI with the rejected message
 			- ROCKFISH sends and email to the user explaining that it's a fail and why
 	- RAVEN knows a request has been sent and has a license job that checks to see if a license is available periodically 
-		- ROCKFISH returns a "no-op" type response if there is no license
+		- ROCKFISH returns a "no-op" type response if there is no license (as minimal as possible for bandwidth purposes since it's polling regularly)
 		- ROCKFISH returns a "FAIL" type response if there is a fail with reason code to display to user
 			- RAVEN CANCELS the check for license job and removes the request
 		- ROCKFISH returns a license key when available under the dbid fetch code