> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/platform-administration/maintenance-mode-applications/wallboard/configure-wallboard-views.md).
# Configure Wallboard views
Configure Wallboard Config.xml settings, common options, and supported view configuration areas.
Wallboard stores local client configuration in `Config.xml`. Use this page to locate the file, back it up, and configure common settings and supported view configuration areas.
## Locate Config.xml
The default path depends on the installed bitness:
| Installation type | Default configuration file path |
| ------------------- | ---------------------------------------------------------------------- |
| 32-bit installation | `C:\Program Files (x86)\Anywhere365 InFlight WallBoard\I01\Config.xml` |
| 64-bit installation | `C:\Program Files\Anywhere365 InFlight WallBoard\I01\Config.xml` |
{% hint style="warning" %}
Back up `Config.xml` before editing it. An invalid XML file can prevent Wallboard from starting or connecting to the configured UCC.
{% endhint %}
After you edit `Config.xml`, restart Wallboard and confirm that it opens the expected view.
## Configure common settings
Use these settings to control general Wallboard behavior. Keep XML element names exactly as they appear in the installed configuration.
| Setting | Purpose |
| ------------------------------ | ------------------------------------------------------------------------------- |
| `DefaultView` | Default view shown when Wallboard starts. |
| `MultipleUCCGroup` | Multi-UCC group behavior used by multi-UCC views. |
| `LogLevel` | Local logging level. Increase only when troubleshooting requires more detail. |
| `LowestSkillValue` | Lowest skill value included in Wallboard calculations or display logic. |
| `Language` | Wallboard interface language. |
| `DefaultDepartmentView` | Default department view behavior. |
| `DepartmentsAlphabeticalOrder` | Controls whether departments are ordered alphabetically. |
| `LyncVersion` | Legacy configuration name. Do not use it as a Microsoft Teams version selector. |
For SLA calculations, use only variable names confirmed in the installed configuration. Do not copy formulas from another environment without checking the exact variable names and queue logic for the customer.
## Configure views
The following view configuration areas are supported for Wallboard. For a user-facing explanation of each view, see [Wallboard views reference](/use/existing-dialogue-cloud-neo-connect-apps/wallboard/views-reference.md).
| View | Configuration areas |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Views 1 and 2 — Normal views | `DashboardServer`, presence indicator display, queue alerts, queue animation, privacy, and credentials. Use the Dashboard Service host or URL supplied for the customer; do not publish or reuse example endpoints. |
| View 2 — Skill filter | `SkillFilter` with semicolon-separated skill titles. Confirm skill names against [Skills and Routing Criteria](/contact-center-configuration/queues/skills-and-routing-criteria.md). |
| View 3 — Multi UCC | UCC groups, per-UCC SLA labels and values, skill thresholds, Dashboard Service entries, and multi-view animation. |
| View 4 — Agents | Top-left and top-right UCC sections, display names, skills, presence-agent behavior, Dashboard Service URL, and activity-token labels such as lunch, break, admin, and training. |
| View 5 — Statistics | `AgentsReasonCode`. |
| View 6 — Reason Code Rows | `ReasonCodes`, first reason code as InCall, second reason code as Discharge, optional `*` catch-all, and `ShowAgentTotalNumberCallsPerDay`. |
| View 8 — Multi UCC Group | Group display and order, `MultipleUCCGroup`, and animation settings. |
| View 9 — Reason Code Columns | `ReasonCodes`, first column as InCall, second column as Discharge, last column as Other, and `ShowAgentTotalNumberCallsPerDay`. |
Reason-code XML key caution
Some installed configurations use exact XML key names that include legacy spelling. If you publish or edit reason-code XML directly, preserve the key name as installed. For example, the source configuration includes `DetermineSecondReasonCodeDischarg` without a final `e`.
## Validate view configuration
After configuration changes:
1. Start Wallboard from the installed shortcut.
2. Confirm that the expected default view loads.
3. Confirm that Wallboard connects to the configured UCC.
4. Confirm that queue, skill, agent, and reason-code information appears according to the selected views and the customer's configuration.
If the page does not show expected data, use [Troubleshoot Wallboard](/use/existing-dialogue-cloud-neo-connect-apps/wallboard/troubleshooting.md).
---
# 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://atlas.anywhere.now/platform-administration/maintenance-mode-applications/wallboard/configure-wallboard-views.md?ask=&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.