Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Flex Backend Release Notes


(error)

Danger

Twilio Changelog

This dedicated Release Notes page is no longer updated. Updates to the Flex backend, as well as all other product updates across Twilio's services, are available on the Twilio Changelog(link takes you to an external page).


July 17, 2019

july-17-2019 page anchor
  • New Flex accounts created will have Enforce Logout enabled by default with an Offline Threshold of 30 seconds. This feature automatically logs out users who are not reachable from within the Flex UI after 30 seconds. These settings are configurable in Flex Settings(link takes you to an external page) .

These changes only apply if you're using FlexUI 1.8.0+.

Changed

changed page anchor
  • All plugin URLs are now available from https://flex.twilio.com/plugins/plugin-test.js?v=123 , instead of your Twilio Runtime domain. You can always find your plugins and their URLs at https://flex.twilio.com/plugins .
  • Internally routed plugins provides enhanced performance & caching semantics.
  • Support for creating Private Plugins that are only accessible with your valid Flex JWE Token.
(information)

Info

Note: Plugins uploaded as public assets will remain accessible via the runtime URL, but if using that URL within Flex you won't get the performance benefits, or the ability to restrict access to Flex agents only.


  • Enforce Logout allows you to automatically logout users if they are no longer reachable from within Flex. For example, if a user closes their browser tab or turns off their computer, that user can be automatically transitioned to a TaskRouter activity that makes them unavailable for tasks and which will not be charged by Active User Hour Pricing.
(information)

Info

Note: A previous version of this changelog entry stated that this automatic logout would also happen if a user "locks their computer." We have removed this because this is dependent on OS behavior and is not guaranteed.



  • The admin and supervisor chat deployment roles are provisioned within the Flex Chat Service of existing projects.

  • Two deployment chat roles are included in the Flex Chat Service on account creation. The admin and supervisor roles are provisioned to support chat monitoring in a future release.

  • Default agent activities are now Offline , Unavailable , Available , and Break . These are configurable via the TaskRouter Activities API.
  • The custom1 , custom2 , custom3 , custom4 , and custom5 Task Channels are no longer created by default. New channels used for routing can be created using the TaskRouter TaskChannels API.

Rate this page: