> For the complete documentation index, see [llms.txt](https://operations.clausebase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://operations.clausebase.com/updates-december-2024/1-december-2024.md).
# 1 December 2024
## Export Q\&As
New feature In Clause9's Q\&A editor, you can now export the categories, cards, conditions, questions and predefined answers to a DOCX-file.
The typical use case is to allow external editors (e.g., reviewers) to learn the structure of a Q\&A.
## Cross-tags
New feature In Clause9's Assemble Document module, there's a new *Cross-tags* panel. This panel shows all the cross-tags that are available in the document and allows you to navigate to both the clauses/documents that implement this cross-tag, and the clauses that refer to those cross-tags.
## Allow Shift & Control-click in user lists
Improvement In lists of users (e.g., members of a Group or Profile) you can now Shift-click to select a contiguous range of users and Control-click (Alt-click on Mac) to selectively add/remove individual users. This allows much quicker configurations of large user configurations.
## Filename separately stored in Truffle Hunt
Improvement In Truffle Hunt, we now store the filename of uploaded DOCX/PDF files separately from the title of the document. Previously, the filename was only stored when no title was found inside the document (either within the metadata, or within the document's contents).
## User interface tweaks to the Summarise module
Improvement The arrangement of the main toolbar buttons, configuration panel and save dialog box are slightly changed.
## @subdoc-crosstags special function
New feature The `@subdoc-crosstags` [special function](https://help.clause9.com/special-functions/references#subdoc-crosstags) allows you get an overview of all the cross-tags of all enabled subdocuments in a Binder. These crosstags can then be used for other purposes, e.g. for compiling an inventory of subdocuments.
---
# 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://operations.clausebase.com/updates-december-2024/1-december-2024.md?ask=&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.
