> 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-april-2024/27-april-2024.md).
# 27 April 2024
## iManage integration
New feature Launch of our integration with iManage. Features:
* Users can send workspaces and/or multiple files to a Truffle Basket of their choice.
* Users can choose a Clause9 or ClauseBuddy template right from within iManage, and then open that Q\&A in a browser window.
***
## ClauseBuddy
### Summarization improvement
There's a new filterable dropdown list, that also supports summary deletion, and remembers recently selected entries.
The summarization feature now also works in Outlook.
### Reviewing PDF files
New feature Users can now upload PDF files for the Review feature.
### Reviewing improvements
Some simplifications were added to the Reviewing feature, to facilitate the user's experience.
The prompting instruction sent to the LLM was also revamped.
### Saving prompts
New feature In several LLM-enabled modules of ClauseBuddy, users can now save their prompt (through the "..." button at the right of the edit-box), so they can then easily retrieve those prompts later on.
*Note that the prompts are saved to the personal settings of the user: they are not currently shared within a team.*
### AutoSuggest "unsupported language" message
When the user tries to use AutoSuggest on an unsupported language (e.g. a German document, when using a Belgian server that only supports English/Dutch/French), there will now be a clear error message.
***
## Clause9
### Addition of "uncovered export"
New feature In the “...” menu at the top right of Assemble Document, users can now do an “Uncovered export” of a template towards a DOCX file.
This allows other team members to see which parts of a text contain conditional logic, which can be useful for reviewing complex documents. Of course complex documents remain challenging to review (cf. your feedback-list), but this new tool should help.
By using the special function @explain (e.g., in an enabled-field), you can provide a description instead of showing a complex formula. This is also possible for other fields.
### Special functions
`@extract-number` now also accepts a duration
Addition of `@explain`, for the uncovered export described above.
---
# 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://operations.clausebase.com/updates-april-2024/27-april-2024.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.