UiPath Orchestrator Management Enterprise Automation Best Practices

A successful enterprise automation environment should tell a story. Anyone looking at your UiPath Orchestrator should immediately understand:

• What business area owns the automation
• What process the automation performs
• What assets, storage, triggers, and dependencies belong to that process

The Orchestrator structure should represent the organization’s operating model. A well-designed automation ecosystem improves: maintainability , supportability, troubleshooting, knowledge transfer, governance and scalability

1. Orchestrator Folder Structure Standards

Orchestrator folders should represent business departments, functions, or operational units. Avoid folders based on temporary initiatives or technical categories

Recommended Folder Naming

Use business-aligned names where names are too long use meaningful abbreviation with a description. Orchestrator folders should answer which business area owns this automation?”

3. Process Naming Standards

Process names should be descriptive and written in PascalCase (prefferably). Avoid generic names that do not clearly explain the purpose of the automation. Do not include words such as Process, Automation, Bot, Robot, or Workflow, as everything deployed and managed within UiPath Orchestrator is already an automation process. Ensure every process in Orchestrator has a clear description and relevant labels to help identify, understand, and support the automation. Where the automation interacts with a specific system or application (for example, a web portal), include the system or application name within the process name where possible to make dependencies and ownership clearer.

Bad Examples Of Process Names : Process1, InvoiceBot ,PayrollAutomationProcess CustomerUploaderRobot

Good Examples Of Process Names : RightMoveMortgageOfferValidator, WorkDayEmployeeDataCreator

A screenshot of a well-named process in a production Orchestrator demonstrating good naming conventions, along with a clear description and appropriate labels.

4. Storage Bucket Naming Standards

Storage buckets should match the process name and end with the word bucket. i.e if Process name is RightMoveMortgageOfferValidator then the bucket should be RightMoveMortgageOfferValidatorBucket.

Bad Examples Of Storage Bucket Names : FilesBucket, Documents, TempStorage

5. Asset Naming Standards

Assets should be descriptive and begin with the process name because assets should communicate: Which automation uses it and What the value represents. i.e if the process name is OneTopCustomerCertificateUploader an asset to hold the share point url for the process should be OneTopCustomerCertificateUploaderSharePointURL

A screenshot of a well-named asset in a production Orchestrator demonstrating good naming conventions, along with a clear description.

If assets are of credential types or secrets, they should end with the word “Credential” or “Secret” and begin with the name of the system they authenticate for, for example WorldRemitApiCredential or OneTopAppSecret.

Note: always ensure to add a description

A screenshot of a well-named asset in a production Orchestrator demonstrating good naming conventions, along with a clear description

6. Data Fabric Entity Naming Standards

When using Entities in Uipath Data Fabric, always include the process name in the Display name . i.e if process name is CustomerCertificateUploader then an entity display name can be CustomerCertificateUploaderUploadHistory

7. Trigger Naming Standards

Triggers should be written as a phrase or sentence fragment. A trigger name should explain: What automation starts, When it runs and Why it exists. Someone should understand it without opening the trigger settings.

A screenshot of a well-named trigger in a production Orchestrator demonstrating good naming pattern

Good Examples

• Start CustomerCertificateUploader 10:30 AM
• Run PayrollReportGenerator Every Monday 06:00 AM
• Execute InvoiceValidation Daily At 02:00 AM

Bad Examples

Trigger1 ,ScheduleA , DailyTrigger , CustomerTrigger

8. Queue Naming Standards

Queues should follow the same naming philosophy. Format: {ProcessNameQueue} i.e CustomerCertificateUploaderQueue if process name is CustomerCertificateUploader

9. Machine Naming Standards

Machines should represent environment and purpose.

Example:

• PROD-PAYROLL-AUTO01
• TEST-REVENUE-AUTO01
• DEV-BILLING-AUTO01

11. Environment Separation

Maintain clear separation:

• Development
• Testing
• Production

12. General Enterprise RPA Principle

Every automation should tell a story:

A business user should be able to look at Orchestrator and understand.