> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-for-salesforce/delpha-upgrade/whats-new/data-quality/build-3.56.md).

# Build 3.56

## New Score Meter: Review & Fix Everything in One Place

[The Score Meter has been redesigned](/delpha-for-salesforce/delpha-apps/delpha-score-meter.md) to simplify your workflow and make issue resolution faster and more intuitive:

* **Before**: You had to switch between the Score Meter and the Bot to review and apply corrections.
* **Now**: Everything happens directly in the Score Meter — **review**, **select**, and **apply** corrections all in one place.
* **New interface**: Cleaner, clearer, and optimized for batch actions. You can now apply changes to **1 / some / or all** suggestions with just a few clicks.

No more back and forth. Just smarter data review in a single streamlined experience.

Try it out now and speed up your remediation process!


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.delpha.io/delpha-for-salesforce/delpha-upgrade/whats-new/data-quality/build-3.56.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 `build a script that syncs our docs to a CMS` 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.