> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/release-notes/release-notes-archive/release-1.7.0.md).

# Release 1.7.0

Published to the Chrome Web Store on June 19, 2022

✨ Enhancements

* Support for nesting bricks in the Page Editor including If/Else, Try/Except, Looping, and multi-brick Document Builder sub-panels and actions
* Document Builder UI overhaul, including element formatting controls, outline view, drag and drop, and more!
* Add new trigger types: Selection Changed, Page State Changed, and Custom Event ([#3554](https://github.com/pixiebrix/pixiebrix-extension/pull/3563))
* Add new triggers for sidebar panels: Selection Changed, Page State Changes, Custom Event, and Manual
* Revised “Add Brick” model layout in the Page Editor with categories ([#3541](https://github.com/pixiebrix/pixiebrix-extension/pull/3541))

### 🐛 Bug Fixes

* Eliminate flickering when rendering Sidebar panels ([#3571](https://github.com/pixiebrix/pixiebrix-extension/pull/3571))

### 🧱 New/Updated Bricks

* The new “Emit Custom Event” brick `@pixiebrix/event` allows you to dispatch a custom event with data. You can receive these events the new “Custom Event” trigger ([#3564](https://github.com/pixiebrix/pixiebrix-extension/pull/3564))
* 🎲 Generate random numbers with the `@pixiebrix/random` brick
* 🌳 Control flow bricks: If-Else, Try-Except, Retry, For-Each, and For-Each Element
* The Show Sidebar brick now automatically shows a panel from the current blueprint. You can additionally specify a specific panel to show ([#3566](https://github.com/pixiebrix/pixiebrix-extension/pull/3567))

### 🎨 User Experience

* Automatically switch between Sidebar panels when working in the Page Editor ([#3566](https://github.com/pixiebrix/pixiebrix-extension/pull/3567))
* Improved look and feel of cancelled and errored Sidebar Panels


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pixiebrix.com/release-notes/release-notes-archive/release-1.7.0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.