> 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-2.2.7.md). # Release 2.2.7 ### :bug: Bug Fixes * Add validation for Google sheet id patterns * Fix stale/duplicate FAB actions and hotkeys on deployment updates ### :bricks: Brick Updates * Display Temporary Information: add option to toggle on/off header for modal * Capture Audio: add fields for audio bit rate and MIME type (container type, codec) * Document Builder: allow Row as child of Column * Element Reader: add value property that returns HTML Input/Select element value * YAML Parser: add YAML parser brick * Fill Template: add support for Nunjucks templates and providing custom template context ### :art: User Experience * Emit a Custom Event: warn in Page Editor if emitting a reserved event name * Run Automation Anywhere Bot: improve error in Page Editor when connection to Control Room fails due to an untrusted/invalid Control Room HTTPs certificate --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pixiebrix.com/release-notes/release-notes-archive/release-2.2.7.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.