Decisions Developer Debug Mode
- 28 Aug 2024
- 1 Minute to read
- Print
- DarkLight
Decisions Developer Debug Mode
- Updated on 28 Aug 2024
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
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 Required
The Settings configured in this article require Administrator privileges in the Decisions environment and on the host machine.
Enabling Decisions Developer Debug Mode
- Navigate to C:\\Program Files\Decisions\Decisions Server.
- Open Settings.xml in a text editor.
- Use the find function of the editor (Ctrl+F or cmd+f respectively) to locate <EnvironmentName>.
- Change the value between the <EnvironmentName> </EnvironmentName> tags to Development.
- Save and close the file.
- Restart Decisions Server (or IIS App Pool).
- 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.
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.
Was this article helpful?