1.2.10

Release notes:

• Bugfix for an issue where the KnownUser JavaScript SDK couldn't be loaded

Changes from previous versions:

1.2.9:

• Bugfix for wrong integration configuration domain

1.2.8:

• Options requests are not ignored by default, there's a variable to enable this
• QueueItToken can be retrieved from the headers now (x-queueittoken)

1.2.7:

• The SDK dependency was updated to the latest version 3.7.4
• Started ignoring OPTIONS and HEAD requests
• Added queue-it connector headers
• The connector can now be used as an NPM package

1.2.6

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).

1.2.5

Release note

Bug fix

• Added exception handling to download configuration.

1.2.4

Release note

Bug fix

• Update the configuration download URL.

1.2.3

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.2.2

Release note

New features

• Using secure integration config

1.2.1

Release note

Bug Fix

• IntegrationConfig is cached for 5 minutes.

1.2.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.1.1

-fixing getAbsoluteUri

1.1.0

-Downloading and caching integration configuration initiated by request.