August 6, 2024

Pagination now appears when you open a folder or sub-folder from the Flows page.

On the board, you can select multiple actions with your mouse.

• Previously, you could only select multiple actions using the Control (ctrl) key. Now you can also click and hold your mouse to highlight a group of actions. You can then move or delete multiple actions, as needed.

Use the Invert Port Orientation toggle to change which side of the action the entrance and exit ports appear on.

• By default, the entrance port is on the left side of an action and exit ports are on the right. Select the toggle from the Action section of the Configurations Panel to move the entrance port to the right and the exit ports to the left.

The History section now displays a new entry when saving a flow with errors.

• Previously, if you attempted to save a flow with errors, a new entry did not appear until the errors were resolved and the flow was deployed.

• Now, even if there are errors, if you click the Save or Save As button, a new entry will appear in the History.

The following updates were made to the External Web Call action:

• If you choose the "GET" Method, the Body field no longer appears.

• The maximum Timeout value is now 100 seconds (previously 200 seconds).

  Note: If your flow currently has a Timeout greater than 100 seconds, the next time you redeploy your flow an error message will appear advising you to update the Timeout value.

For the Condition and Switch actions, the "String Contains" option in the Condition field was renamed "Contains Variable".

• The underlying functionality remains the same, and this new label more clearly describes that a variable is being evaluated (as opposed to a literal value when using the "Contains" option).

The 1 second and 2 second Interval options are no longer available for the Schedule trigger action.

• Legacy flows using the 1 or 2 second Interval will not experience any errors or have to make a change, but those options will no longer appear when you view the action.

The following bugs were resolved:

• On the Flows page, when opening a folder containing many flows the folder would appear to be empty, and the flows were not loading. This issue was resolved, and all flows now appear as expected.

• On the Audio Library page, the "Reset" message now only appears when hovering over or clicking the Reset button and disappears when you move your mouse away.

  • Previously the message would linger on screen unexpectedly.

• You can now easily select the correct connector when an action has many connections attached to it.

  • Previously, if a port had multiple connectors attached to it, the connectors would layer on top of each other, and they were not clearly separated. You can now more easily select the appropriate individual connectors and zoom in to more accurately view and select the connectors.

• The Play hold music check box was hidden for External Web Call actions with the "POST" Method and Content Type "x-www-form-urlencoded".

  • This issue was resolved, and you can now view the Play hold music check box at the bottom of the Inputs section as expected.

• When a number beginning with zero was included in the Value field of the Condition action, it was incorrectly being read as text instead of a string of numbers.

  • This issue was resolved and values beginning with zero are now correctly compared to other numeric values.

• An intermittent issue was causing some flows using default text-to-speech (TTS) settings to experience a "Failed generating Audio for TTS..." deployment error.

  • This issue was resolved and flows using default TTS now deploy without errors.

• After clicking Save As an error was causing flow Sharing configurations to change from "Public" to "Private".

  • This issue was resolved and Sharing configurations no longer change when using the Save As feature.

• An issue was causing some previously deployed flows to be stuck when attempting to re-deploy after changes were made. This issue was resolved, and flows can now complete re-deployment as expected.

• In the History section, flows created prior to March 2023 were missing the "Deployed" label next to the currently live version of the flow.

  • The "Deployed" label now appears next to the correct entry in the Version History list for all flows.