> 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.1.6.md).

# Release: 1.1.6

Published in the Chrome Web Store on on 6/8/2021

### Improvements

* Workshop:
  * Add "Export Blueprint" button on active brick configuration page
  * When an integration is added, defaults the key and credential (matching behavior in the Page Editor)
* Page Editor: Add ability to attach a button to an existing menu item foundation in the page editor
* Brick Configuration:
  * Blueprints: support for exposing options in a blueprint that the user can configure when activating from the marketplace
  * Integrations: support baseURL option in key-based authentication
* Infrastructure: we've cleaned up some stuff under the hood to help us make releases faster!

### Notable New Bricks

* `@pixiebrix/template` : a transform for filling in template with the context. Useful for working with the new blueprint options feature
* `@pixiebrix/hide`: hide or remove elements from the page
* Bricks for working with Automation Anywhere and AARI:
  * `@pixiebrix/automation-anywhere/aari-request-create`
  * `@pixiebrix/automation-anywhere/aari-request-new`
  * `@pixiebrix/automation-anywhere/aari-requests-list`
  * `@pixiebrix/automation-anywhere/aari-tasks-list`


---

# 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.1.6.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.