> 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-may-2024/4-may-2024.md).

# 4 May 2024

## Document Reviewing

Users can now add independent questions to a reviewing set (instead of being required to add questions as a sub-element of a condition). This will help towards generating reusable, generic reviewing sets.

***

## Smart Templates

### Automatic question generation 

<mark style="background-color:orange;">New feature</mark> With the help of an LLM, users can now automatically create questions & predefined answers for their Q\&A.&#x20;

<figure><img src="https://1414353930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc1g6bv00az2hAVxclF4w%2Fuploads%2FZk9p7NUneWBHiJ51HG9x%2Fimage.png?alt=media&amp;token=02f08c55-d5b1-405e-9d3b-12a5eead19ba" alt="" width="563"><figcaption></figcaption></figure>

***

## Truffle Hunt

### Detection of "fallback titles"

Paragraphs that are now position above a list of bullets, will be taken into account in the clause splitting algorithm.&#x20;

### No results message in multi-lingual documents

The "no results" message for Truffle Hunt was improved, so that it is less frequently showed in multilingual documents.

***

## Single Sign On

The Clause9 SSO token cookies were changed to have an expiry date equal to the number of expiry hours configured in the SSO settings (instead of having session cookies), to avoid issues with the token cookie not being taken into account after network interruption in Chrome

***

## Clause9

### Various improvements

Polish language support (particularly for dates) was improved.


---

# 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-may-2024/4-may-2024.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.