1.2.3

Release notes:

• Hotfix for an issue where cookies won't be set

1.2.2

Release notes:

• Switched from JavaScript to TypeScript

1.2.1

Release notes:

• The SDK dependency was updated to the latest version 3.7.4
• Options requests can now be ignored, there's a variable to enable this
• Added queue-it connector headers
• QueueITToken is now retrieved from the headers if not present in the URL
• Options requests are not ignored by default, there's a variable to enable this
• Connector can now be used as an NPM package

1.2.0

Release note

• Possibility to call queueit code as subroutines and combine queueit code with other workers
• Limiting body reader to 2k characters
• Improving code readability

1.1.2

Release note

Bugfixes

• Only remove 'queueittoken' (via 302) if trigger matches 'queue' action.
  Some integrations have a page matching and ignore action. On this page AJAX calls are made to queue protected endpoints.
  When user returns from queue (triggered by AJAX call), then queueittoken would be removed without user getting a valid cookie (because it matched the ignore action). Now, tokens will only be removed on queue actions (so we are sure user either has or will get a cookie).

• Correct method name 'getRequestBodyAsString' in httpProvider implementation
  With this change the experimental requestbody trigger condition actually works.

Changes

• New setting 'READ_REQUEST_BODY' has been added to js code.
  If you want to use the experimental requestbody trigger condition you will need to set this variable to 'true'. You can find this variable just below QUEUEIT_CUSTOMERID and QUEUEIT_SECRETKEY.
  We did this change because majority of integrations are not using this condition, therefore there is no need to read the body of the request every time. This change will in these cases result in much better performance of the connector.

1.1.1

Release note

• Updated to Javascript SDK 3.6.1: Always remove old, no longer valid, queue-it (queue passed) cookies:
  Only if client sent queue-it cookie to server.
• Updated cache headers.
• Ensures that triggers with match any value for cookie condition will work correctly.

1.1.0

Release note

This release includes the latest KnownUser/Connector code version 3.6, containing:

New features

• Support for matching any value (*) in a contains trigger operator.
• Matched action name available in code. Found as property on action result and config models.
• Correctly encode white space in custom layout names, e.x. "my%20layout".
• Improved system diagnostics
  • Matched action name included as query string parameter in URL for queue redirect.
  • Matched action name available in diagnostics/debug cookie as part of (queue/cancel)config information.
  • Runtime, connector name and version available in diagnostics/debug cookie.
  • Exception (if any) available in diagnostics/debug cookie.

Quality improvements

• Consistent error handling in case of invalid tokens.
• Ensure that invalid/manipulated queue-it (queue passed) cookies are never accepted.
• Perform expiration checks on debug tokens.
• Always remove old, no longer valid, queue-it (queue passed) cookies.
• Ensure that debug information (cookie) is always available, ex. when integration configuration is missing or invalid.

1.0.1

Update README.md