Update README.md

README.md

@@ -152,6 +152,7 @@ and of type **Hidden** in Akamai property manager. The following table describes
 | PMUSER_QUEUEIT_SECRET_KEY | Yes | Find your Secret key in the GO Queue-it Platform. |
 | PMUSER_QUEUEIT_CONFIG_TYPE | Yes | 'inline' or 'cache' or 'edgekv' |
 | PMUSER_QUEUEIT_API_KEY | If 'PMUSER_QUEUEIT_CONFIG_TYPE' is set to cache  | Find your Api key in the GO Queue-it Platform. |
+| PMUSER_QUEUEIT_EXECUTED | For validation that the Queue-It EdgeWorker was executed | The Queue-It EdgeWorker will set the variable to `true`. This variable can be used in Akamai Property Manager to apply alternative logic if the EdgeWorker was not executed. | 
 
 ### Adding a Site Failover behaviour
 After the EdgeWokrewr behaviour you need to add a Site Failover to do a retry if EW fails.
@@ -170,3 +171,10 @@ If you need to protect AJAX calls beside page loads you need to add the below Ja
   src="//static.queue-it.net/script/queueconfigloader.min.js">
 </script>
 ```
+
+### Using EnQueueToken
+A token could be used for queueing the users. This makes it even more protected. The token will be included when the user is redirected from Akamai to the queue and vice versa. [QueueToken](https://github.com/queueit/QueueToken.V1.JavaScript) package has been used to generate this token. The generated token will be valid for 1 minute.
+
+To use the EnqueueToken follow the below steps:
+- The waiting room should be configured to accept this token. This configuration could be made in Queue-it Go platform.
+- SHOULD_INCLUDE_ENQUEUETOKEN variable should be set to ```true``` in the ```main.js``` file.