Advanced Configuration Editor
The Advanced Configuration Editor lets you view and edit Moveworks Setup configurations directly in JSON format. Found under Troubleshooting Tools in the left navigation bar, this power tool puts full configuration control at your fingertips — enabling bulk operations, configuration duplication, environment migration, and faster troubleshooting.
The Advanced Configuration Editor is intended for Moveworks partners and Advanced Moveworks users. We do not recommend admins use this mode as it directly modifies live configurations and can break existing functionality — use the standard UI instead.
Key use-cases for using advanced configuration editor
How to Use
Step 1: Navigate to the Advanced Configuration Editor
Go to Moveworks Setup > Troubleshooting Tools > Advanced Config Editor in the left navigation bar.
Step 2: Select a Configuration
- Use the Configuration dropdown to search for and select the configuration you want to view or edit.
- Configurations are identified by their Moveworks configuration name (e.g.,
TicketWorkflow,CustomDomainConfig,TicketRoutingConfig). - Only a subset of configurations are available. These are vetted by the Moveworks team.
Step 3: View and Edit the JSON
- The full JSON configuration is displayed in the editor.
- Make your changes directly in the JSON editor.
- Click Save to submit your changes.
On success: You will see a confirmation message: “Your change is now successfully saved.”
On error: The editor will display a specific error code and message. For example:
- Error 13009 — Validation failure (e.g.,
display_name must contain at least 1 character) - Error 13002 — Deserialization failure (e.g., submitting empty or malformed JSON)
Step 4: Add a New Configuration (Multi-Cardinality Only)
For multi-cardinality configurations:
- Select the configuration type from the dropdown.
- Click + Add new config.
- The editor opens in create mode with a blank JSON template containing the required fields.
- Fill in the required fields and click Save.
Important Guardrails
Common Use Cases
Reference list for Setup left nav page to configuration name in the dropdown
Enterprise Search
Ticketing Automation
Access Management
Core Platform
Chat Platforms, Display & Notification Configs
Organization Details
Frequently Asked Questions
- What happens if I submit invalid JSON?
The editor will reject the save and display an error. For example, submitting empty JSON returns Error 13002: “Failed to save config due to precondition check: Unable to deserialize data.” - Are standard UI validations applied in JSON mode?
No. UI validations such as required fields, minimum length, and DSL hints are not enforced in JSON mode. You are responsible for ensuring the JSON is valid and complete. - Can I create new configurations, or only edit existing ones?
You can do both. For multi-cardinality configurations, use the + Add new config option to create a new configuration from a blank template. - Will the JSON structure change in the future?
Yes, the JSON structure may change in future updates. Always refer to the current configuration schema and avoid hardcoding assumptions about field names or structure. - Can I update secrets or sensitive credentials through this editor?
No. Please refrain from updating secrets or sensitive credentials via the Advanced Configuration Editor. Secrets are represented as UUIDs mapped to values stored securely — direct modification is not supported in v1. - Why can’t I find a specific configuration in the dropdown?
Only approved, customer-facing configurations are shown. Internal UIVars and configurations that haven’t been approved by engineering DRIs are intentionally hidden from the dropdown.