βœ…Release 1.8.11

Published to the Chrome Web Store on March 25, 2024

circle-exclamation

πŸŽ‰ New Features

  • Introducing the new Text Selection Menu. Quickly access your context menu options anytime you select text. No need to right click! (#7980arrow-up-right)

  • Introducing the new Shortcut Snippet Menu. Quickly inserting static and dynamic snippets into text fields (#7980arrow-up-right)

    • To add static text to the Shortcut Snippet Menu, see the Add Text Snippets brick in the Page Editor

    • To add dynamic text to the Shortcut Snippet Menu, see the [Experimental] Add Dynamic Text Snippet in the Page Editor

πŸ› Bug Fixes

🧱 New/Updated Bricks

  • Adds a Run API Task brick to run Automation Anywhere API Tasks (#7996arrow-up-right)

  • Adds support for setting the default number of rows for a paragraph text field in the Form Builder (#7850arrow-up-right)

  • Adds new Submit Toolbar configuration for paragraph text fields in the Form Builder (#7807arrow-up-right)

  • Adds support for http: URLs in the IFrame brick (#8020arrow-up-right). Note, however, that most browsers block insecure iframes on secure sitesarrow-up-right. The Chrome Console will show an error: "Mixed Content: The page at 'PAGE' was loaded over HTTPS, but requested an insecure frame 'FRAME'. This request has been blocked; the content must be served over HTTPS."

🎨 User Experience

  • Re-labels Integrations in the Extension Console to Local Integrations to avoid confusion with Team Integrations in the Admin Console (#7810arrow-up-right)

  • Added informative message in a banner that displays in the Extension Console when the local browser database (IDB) is unresponsive. Directs users to restart their browser. (#7846arrow-up-right)

  • AA Automation Co-Pilot branding updates (#7888arrow-up-right)

Changes Required for Invalid Integration Configurations

Some previous versions of PixieBrix did not properly validate Integration Configuration fields.

In the 1.8.11 release, integration configurations containing invalid values will now correctly throw an error when authenticating an API request.

If you are impacted, update the configuration for the integration (See Configuring Integrations).

Known impacted integration configuration fields:

  • Automation Anywhere Control Room:

    • Folder Id: if you want to exclude the folder id, click field toggle and select "Exclude". Blank is not a valid value for Folder Id.

If you have questions or need assistance, please reach out to [email protected]envelope or message in the Community Slackarrow-up-right.

Last updated

Was this helpful?