---
title: "Decisions Developer Debug Mode"
slug: "decisions-developer-debug-mode"
description: "This document explains how to troubleshoot Front End code issues in Decisions, by using the Decisions Developer Debug Mode.  The document also describes the procedure for the required restarting of the Service Host Manager (SHM) after modifying files in Debug Mode. "
updated: 2024-08-28T15:43:09Z
published: 2024-08-28T15:43:09Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Decisions Developer Debug Mode

## Overview

**Decisions' Developer Debug Mode** helps troubleshoot front-end code issues. When there is an error, this mode provides the line number of code throwing the error. To set up the Decisions Developer Debug mode, the Settings.xml file must be modified. This file has two locations in the Decisions file system. After the files are modified, a Service Restart is required to apply changes.

Admin RequiredThe Settings configured in this article require Administrator privileges in the Decisions environment and on the host machine.

## 

---

## Enabling Decisions Developer Debug Mode

1. Navigate to **C:\\Program Files\Decisions\Decisions Server**.
2. Open **Settings.xml** in a text editor.
3. Use the find function of the editor (Ctrl+F or cmd+f respectively) to locate **<EnvironmentName>**.
4. Change the value between the <EnvironmentName> </EnvironmentName> tags to **Development**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-01-28_11h31_48(1).png)
5. Save and close the file.
6. Restart Decisions Server (or IIS App Pool).
7. Refresh the platform browser page.

---

## Decisions Studio

Once logged into the environment, the **DECISIONS** will display a small **[DEBUG MODE]**declaration next to it, indicating that the environment is in the **Developer Debug** mode.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-08-28_11h32_43.png)

---

## Viewing the Logs

The user-interface logging can be accessed from the browser developer tools, typically by pressing F12 (or Ctrl + Shift + i) on the keyboard.

![2020-01-20_15h11_33.png](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2020-01-20_15h11_33.png)

---
