orchestrator
latest
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Monitoring
- Queues
- Assets
- Business Rules
- Storage Buckets
- MCP Servers
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator user guide
Last updated Aug 6, 2025
Business Rules allow RPA developers to store and manage Decision Model and Notation (DMN) files as part of a workflow or process diagram, through the Evaluate Business Rule activity.
A developer can model a DMN file outside the UiPath platform with the help of a DMN-compliant editor. A DMN decision is a Studio project file composed of the following:
- The DMN file
- A workflow (.xaml or .cs coded)
When the DMN file is created, you can upload it to the folder context as a new business rule object.
The following table contains field descriptions for the Business Rules page:
|
Field |
Description |
|---|---|
|
Name |
The display name of the business rule. |
|
Current version | The version number of the DMN file currently used in a given business rule. |
|
Description | The description of the business rule object. |
| Labels | The list of all labels associated with the business rule. You can search the business rule list by Labels. |
| Properties | The list of all properties associated with the business rule. You can search the business rule list by Properties. |
