Flex UI 2.0 is released to Public Beta.
This is a major version upgrade of the Flex UI library and contains breaking changes that require you to update your plugins for compatibility. Check out our migration guide for more detail.
Beta products are not covered by a Twilio SLA. Learn more about beta product support.
For Customers building HIPAA-compliant workflows with Flex UI, Customers are responsible for ensuring that in the case that PHI will be exposed through Flex UI, that only those that are authorized to access PHI have access to Flex. In some scenarios, PHI may be available to be downloaded by an Agent to their workstation from Flex UI. It is the responsibility of the customer to ensure that those with access have proper training on HIPAA prior to being given access. To learn more about building for HIPAA compliance, please visit the latest requirements here.
The Flex UI allows developers to build a custom user experience and custom behaviors for the Flex Agents and Supervisors. You can leverage a set of client-side public interfaces to customize the look and feel, alter the behavior, and introduce additional features to the out-of-the-box experience.
The Flex UI provides a wider range of programmable capabilities:
- Configure the UI or manipulate default properties for standard Flex components
- Customize themes and styles
- Control localization and templates
- Add, replace, or remove components
- Take advantage of UI actions by listening, intercepting, and manipulating UI events
- Customize agent desktop notifications using the Notifications Framework
- Alter the behavior and appearance of native channels and define custom ones with the Task Channel Definitions API
- Mix in Task or Theme context to your custom components
- Leverage the Flex Manager object to get access to and control underlying SDKs
You can find a detailed description of all the Flex UI programmable interfaces in our API Docs and a collection of developer guides with examples of how to use them.
For Customers building HIPAA-compliant workflows with Flex Plugins, Customers are responsible for ensuring that any plugin developed and used are done so in a HIPAA compliant manner. This also includes not inserting PHI into error messages that may be collected by Flex (or any other third party services) for debugging and/or troubleshooting purposes. Twilio cannot guarantee plugins developed by a third-party, regardless of whether they are an official partner of Twilio or not, are HIPAA compliant. Plugins developed by Twilio Professional Services must not be assumed were developed with HIPAA considerations. It is the responsibility of the customer that wishes to use such plugins to ensure they are developed and used in a HIPAA compliant manner. To learn more about building for HIPAA compliance, please visit the latest requirements here.
Flex Plugins are the recommended way of customizing the Flex UI. Plugins have access to all of the frontend APIs: adding and replacing components, using the Actions Framework, triggering Notifications, and more. They also provide a few additional benefits:
- Plugins can be applied to any running Flex instance. This lets you use the same plugins across projects that simulate dev/stage/prod environments, and it's also the preferred path for any partner integration.
- It decouples the customizations from individual
flex-uiversions. As new versions are released, the plugins do not need to be rebuilt and redeployed.
- It allows for modular development. Plugins can be scoped to particular pages, personas, or functions to help separate concerns.
Flex provides the following tools to help you build and manage your Plugins: