Tools View
Tools View
button.
## Commit Manager
The **Commit manager** displays notifications about commits pending to be approved. Any time a change (a transaction) is made in NSO, the Commit Manager displays a notification to review the change. You can then choose to confirm or revert the commit.
{% hint style="warning" %}
**Transactions and Commits**
Take special note of the Commit Manager. Whenever a transaction has started, the active configuration data changes can be inspected and evaluated before they are committed and pushed to the network. The data is saved to the NSO datastore and pushed to the network when a user presses **Commit**.
Any network-wide configuration change can be picked up as a rollback file. The rollback can then be applied to undo whatever happened to the network.
{% endhint %}
### **Review a Configuration Change**
1. Access the Commit Manager by clicking its icon 
in the banner.
2. Review the available changes appearing as **Current transaction**. If there are errors in the change, the Commit Manager alerts you and suggests possible corrections. You can then fix them and press **Re-validate** to clear the errors.
3. Click **Revert** to undo or **Commit** to confirm the changes in the transaction.
* **Commit Options**: When committing a transaction, you have the possibility to choose **Commit options** and perform a commit with the specified commit option(s). Examples of commit options are: **No revision drop**, **No deploy**, **No networking**, etc. Commit options are described in detail in the JSON-RPC API documentation under [Methods - transaction - commit changes](https://developer.cisco.com/docs/nso-guides-6.3/the-json-rpc-api/#methods-transaction-commit-changes).
{% hint style="info" %}
In the **Commit manager** view, you can fetch additional information about the leaf by enabling **more node options** 
and clicking the info 
button.
{% endhint %}
#### **Load/Save Configuration Data**
Start a transaction to load or save configuration data using the **Load/Save** option which you can then review for commit. The following tabs are available:
* **Rollback**, to load data that reverts an earlier change.
* **Files**, to load data from a local file on your disk.
* **Paste**, to load data by pasting it in.
* **Save**, to save loaded data to a file on your local disk.
#### **Commit Manager Tabs**
In the **Commit manager** view, the following tabs are shown.
* **changes** tab, to list the changes and actions done in the system, e.g., deleting a device or changing its properties.
* **errors** tab, to list the errors encountered while doing changes. You can review the errors, make changes, and revalidate the error using the **Re-validate** option.
* **warnings** tab, to list the warnings encountered while doing changes.
* **config** tab, to list the configuration changes associated with the change.
* **native config** tab, to list the device configuration data in the native config.
* **commit queue** tab, to manage commit queues. See [Commit Queue](https://nso-docs.cisco.com/guides/nso-6.3/operations/nso-device-manager#user_guide.devicemanager.commit-queue) for more information.
## Compliance Reporting
The **Compliance reporting** view is used to create and run compliance reports to check the current situation, check historical events, or both.
{% hint style="success" %}
The recommended and preferred way of running the compliance reports is through the Web UI.
{% endhint %}
The following main tabs are available in this view:
* **Compliance reports**, to create, run, manage, and view existing compliance reports.
* **Report results**, to view report results and compliance report status.
### **Create a Compliance Report**
1. In the **Compliance reporting** view, click **Add list item** 
.
2. In the **New report** pop-up, enter the report name and confirm.
3. Next, set up the compliance report using the following tabs. For a more detailed description of Compliance Reporting concepts and related configuration options, see [Lifecycle Operations](https://nso-docs.cisco.com/guides/nso-6.3/operation-and-usage/operations/lifecycle-operations) documentation.
* **General** tab: to configure the report name. Configuration options include:
* **Report name**: Displays the report name and allows editing of the report name.
* **Devices** tab: to configure device compliance checks. Configuration options include:
* **Current out of sync**: Check the device's current status and report if the device is in sync or out of sync. Possible values are **true** (yes, request a check-sync) and **false** (no, do not request a check-sync).
* **Historic changes**: Include or exclude previous changes to devices using the commit log. Possible values are **true** (yes, include), and **false** (no, exclude).
* **Device choice**: Include **All devices** or only **Some devices**. If **Some devices** is selected, specify the devices using an XPath expression, device groups, or devices.
* **Compliance templates**: If a compliance template should be used to check for compliance. See the section called [Device Configuration Checks](https://nso-docs.cisco.com/guides/nso-6.3/operations/compliance-reporting#device-configuration-checks).
* **Services** tab: to configure service compliance checks. Configuration options include:
* **Current out of sync**: Check the service's current status and report if the service is in sync or out of sync. Possible values are **true** (yes, request a check-sync) and **false** (no, do not request a check-sync).
* **Historic changes**: Include or exclude previous changes to services using the commit log. Possible values are **true** (yes, include), and **false** (no, exclude).
* **Service choice**: Include **All services** or only **Some services**. If **Some services** is selected, specify the services using an XPath expression or service instances.
4. Click **Save** when the report setup is complete.
### **Run a Compliance Report**
1. In the **Compliance reports** tab, click the **Run** button on the desired report.
2. Specify the following:
* **Report title**
* **Historical time interval**. The report runs with the maximum possible interval if you do not specify an interval.
3. Click **Run report**.
The report's results, available from the **Report results** tab, show if the report was compliant or has violations. Click **Show details** to fetch additional details.
---
# Agent Instructions: 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:
```
GET https://nso-docs.cisco.com/guides/nso-6.3/operation-and-usage/webui/tools.md?ask=