- Release notes
- Before you begin
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Transforming data
- Customizing process apps
- Publishing process apps
- App templates
- Additional resources
Process Mining
Key concepts
A Process is an end-to-end sequence that combines multiple automated workflows, human-in-the-loop steps, and various system integrations. It consists of multiple process traces and can initiate multiple automation workflows.
The process identifier is the Process name (e.g., Order processing, Customer on-boarding). By default, the trace name is the name of the automation where the tracking starts. The name can be customized by using the Sequence with the Process Tracking support.
Creating meaningful and informative process names that effectively convey their purpose is key to maintaining an organized and efficient workflow. The main goal is clarity. Each process name should be immediately recognizable and understandable. This aids in the overall efficiency and productivity of your organization.
Make sure to set a process name that doesn't change based on the trace, as the process name is intended to group together all traces for the process instances associated with the process.
Below are some best practices for defining process names:
-
Descriptive and meaningful: Effective process names are specific, clear, and state what the process actually is or does, e.g., " Order to Cash", "Employee Onboarding", "Invoide Processing", etc.
-
Consistent: Apply consistent naming conventions across all your processes. This could include a certain format or syntax, like starting with a verb or keeping the essential objective of the process at the beginning.
-
Brief and simple: Keep names as concise as possible. Short, simple titles are easier to remember and understand, thus reducing confusion.
-
Avoid ambiguity: The process name should not create any confusion. Avoid using technical jargon.
-
Reflect the process structure: If your process is part of a larger, structured process, consider incorporating this into the name to create a hierarchical structure. This could help to understand and navigate the various processes in the framework.
-
Think of users and stakeholders: Keep in mind all those who will interact with or be affected by the process. Try to make sure the terminology used is common across your organization.
-
Collaboration: Include team members when naming the processes. They can provide good insights based on their on-the-ground experience and may help to identify names that are intuitive and easy to adopt.
A trace is an instance of an end-to-end process comprising one or multiple tasks.
The trace is identified through a Trace ID. The Trace ID is a unique identifier, generated and managed automatically by the UiPath Platform.
For example, the Trace ID for the instance of an employee onboarding can be: 4fc8ff69b41742deb01f2492207cc3bf.
A task is a specific step within an end-to-end process, performed during the execution of the process, that represents a business step you would like to track from a business perspective.
A task is identified by a Task name and a Task ID. The UiPath platform automatically generates the Task ID, and the task name can be either default or custom, configured through the Sequence with the Process Tracking Support.
Make sure to set a Task name which doesn't change based on the trace, as the goal is to use a generic name for the task.
Below are some additional best practices for defining Data Service task names:
-
Use task action: Including the action in the task name becomes more identifiable. For example,
Update_CustomerDetails_Everydaydescribes the action (Update), the theme or aspect involved (Customer Details), and the frequency (Everyday). -
Reflect the task sequence (if any): If the task forms a part of a sequence, consider including the sequence order in the name. For instance,
01_DataExtraction,02_DataCleaning,03_DataLoadingprovide clear order to tasks. -
Versioning (if needed): If you are creating a new variant of an existing task, consider including a version number in the task name.
An Object is a business entity along with all the interactions that automations have with it during execution. It is defined at the Task level, and the Trace inherits it.
An object is defined by a combination of Object Type, Object ID, and Object Interaction. The Track Object system activity can link an object to a task. One Task can have one or multiple different object references.
We recommend that the Object type and Object ID be captured from the referenced system of record: SAP, Salesforce, ServiceNow, etc.
Adding information about objects can be used in analytics to connect automation data with data from other systems, enabling richer process analysis that takes business-relevant information into consideration. Check out Automation data for more information on how to connect system data with automation data.
The Integration Service package's activities automatically add the business objects to the tasks.
The objects you track will depend on what is important to your particular process and organizational goals. Useful objects to track usually pertain to tasks, activities, events, and resources that are part of the process.
-
Tasks and activities: these are the most crucial objects to track. They represent the work to be done. Their attributes might include Task ID, Name, Description, Start time, End time, Duration, Status, Priority, etc.
-
Events: Events refer to triggers that start or end processes or activities. They might include Event ID, Name, Trigger Time, Source, Resulting Action, etc.
-
Resources: These can be physical (hardware, servers, etc.) or non-physical (robots, software, bandwidth etc.). Attributes to track may include Resource ID, Name, Type, Status, Capacity, Utilization, etc.
-
Process data: This could be any input or output data of the tasks, activities, events, and resources. Depending on your process, you might track data like Sales Order ID, Customer ID, Invoice ID, etc.
Object example:
Object type: Invoice
Object id: UIP-100
Object interaction: Create
Object properties: Disctionary<String; String>
{
Customer name: UiPath;
Total Value: 1000$
)
E.g. Create Invoice in SAP Updated Invoice UIP-100
Task name: Create Invoice
Object interaction: "Create"
Object type: Invoice
Object ID: <SAP Invoice ID>Object type: Invoice
Object id: UIP-100
Object interaction: Create
Object properties: Disctionary<String; String>
{
Customer name: UiPath;
Total Value: 1000$
)
E.g. Create Invoice in SAP Updated Invoice UIP-100
Task name: Create Invoice
Object interaction: "Create"
Object type: Invoice
Object ID: <SAP Invoice ID>
