![]() ![]() We are currently evaluating other workflows that currently use Sync that could be improved by reducing dependencies. Will Sync be removed from other parts of Flex UI? Flex is still populating Sync with the same data as it did before. Yes, Sync can still be used for building additional functionality on top of Flex. We have only removed it from the parts of Flex UI mentioned above. The hiddenWorkerFilter and hiddenQueueFilter default props on the WorkerDirectoryTabs dynamic component can be used to filter the workers and queue that appear in the transfer directory. This means more workers and/or queues may appear in the transfer directory than before. Workers and queues are soft deleted from Sync Maps after 30 days of inactivity, but this is not true of Task Router. Transfer directoryįlex UI now fetches workers and queues from an alternative backend service, Task Router, rather than Sync Maps. The workaround for these inconsistencies is to use the native outbound dialer now built directly into Flex. This particular issue was reported for a customer plugin based on this Twilio Professional Services plugin that renders participants of a call. So far we have had a report of duplicate ‘Left call’ participants appearing in the call canvas. In cases where a Flex customization makes heavy use of Conference data for advanced call use cases, there is the potential for inconsistencies in the UI. However, the same information is still published to Sync Maps in order to enable backwards compatibility with Flex UI customizations and plugins. Under the hood, Flex UI now receives and displays Conference information from an alternative backend service, Flex Orchestrator, rather than Sync Maps. When making an outbound call, all queues are available to be selected. When transferring a call, the lists of workers and queues now show all possible workers and queues. The parts of Flex UI that no longer use Sync can now fetch all workers and queue no matter when the last change was made. This affects lists of workers (users) and queues that previously did not include workers or queues that had no change for 30 days. Sync only stores data for 30 days since the last change to a status. Sync limits on data retention no longer limit the fetching of workers and queues However, there are some UI changes that you may see. This change only affects the internal operation of Flex UI and does not introduce any breaking changes that customers should be aware of. This was done to reduce the number of dependencies in these workflows for better performance and increased resilience in the event of an incident.įlex UI versions 1.33 and above also include the same changes to Sync usage inside Flex UI. All of these now get data from TaskRouter SDK instead of Sync. This included Conference state management as well as Outbound calls and Transfer workflows. In Flex UI version 2.0 we introduced updates to some internal operations within Flex UI to no longer rely on data provided by Sync. Getting Started with React Plugin DevelopmentĬhanges to Sync usage in Flex UI What has been done? ![]()
0 Comments
Leave a Reply. |