- 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
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- App templates
- Additional resources
- Out-of-the-box Tags and Due dates
- Editing data transformations in a local environment
- Setting up a local test environment
- Designing an event log
- Extending the SAP Ariba extraction tool
- Performance characteristics
Process Mining
Create new app wizard
In the Process Mining portal, you can easily create new apps. When you select the Create new app button, a wizard opens that guides you through the process of creating a new app step-by-step. When you leave Create new app wizard at any step, the current state is saved. You can continue creating the app with the state you left the wizard before.
1. In the Process Mining portal, go to the Development tab, and select Create new app.
A wizard starts and the Select app template step is displayed, where you can select an app template to be used for your app.
You can choose to use an existing app template as a starting point for a new app.
See App Templates for an overview of the available app templates.
1. Select the Create app button on the tile representing the application template you want to use as a base for your new app.
The Basic details step is displayed with the default information from the process app type you selected.
1. Edit the name to define a unique name for the new process app in the App name field.
2. If desired, edit the description in the Description field.
3. Select Save & Next.
It can happen that you enter a name for an app that already exists but that you do not see in the All process apps list. In this case, it can be an app for which you do not have View permission.
See the illustration below.
The Data source step is displayed.
.csv files, or load data using an extractor. The data is ingested after you have created the new process app.
For performance and security reasons, it is strongly recommended to use a small dataset for app development and testing data transformations.
The development dataset is used for testing the data transformations. It does not affect the data displayed in the dashboards of the published process app.
Once your app is ready to be used by business users, you can publish the app and ingest new data for use in the published process app.
1. Select the applicable option for your data source.
2. Select Save & Next.
.csv files.
For large amounts of data, it is recommended to use CData Sync or Theobald Xtract Universal (for SAP) to upload data.
Make sure the .csv files have the suffix _raw.
Follow these steps to upload data files.
-
Drag and drop one or more files that contain the data for the process app, or select
to select the files from your computer.
-
Check the detected details for your dataset for Encoding, Delimiter, and Quote character. If needed, select the appropriate settings.
You can select the type of process model to be used for the process app.
Discover process model and Import BPMN model introduce detailed semantic events for exclusive, parallel, and loop behaviors that enhance process precision but may affect app scalability. As a result, this might impact the maximum number of real events supported in a Process mining app.
1. Select the process model type for your process app.
2. Select Save & Review.
The "directly follows" relationship represents the order in which activities occur in a process. It is based on event logs that contain records of activities performed during the execution of a process. By analyzing the event logs, Process Mining techniques can identify which activities are typically executed one after another. Between these two activities, an edge is defined as A➝B.
If, for example, paths A→B and C→D in a process can be performed in parallel, the activities of the two paths can occur in the event log in any order. In the "directly follows graph" approach, these events will not be considered to run in parallel, and the resulting process flow can be the following: A➝C➝B➝D.
A Discover Process Model or a BPMN process model however will take parallel structures into account.
Discovering a process model allows you to have a better understanding of your process structure. By analyzing the whole process (the whole event log) with advanced process mining techniques, activities that happen in parallel, are part of a decision, or are part of a more complex loop are automatically discovered. These relationships are called the process semantics.
Below is an overview of the process semantic types.
|
Semantic node type |
Description |
Visual representation |
|
Parallel gateway (AND) | Represents two or more branches that happen in parallel. |
|
|
Exclusive choice gateway (XOR) | Represents an exclusive choice (decision point) between two or more branches. |
|
|
Loop gateway | Represents a repeatable sub-process with one loop body path and one or more rework paths. |
|
Select Import BPMN model if you want to import your own BPMN 2.0 model and use it as a process model for your process app.
WIth the BPMN model, advanced process algorithms will map your event log data on top of the BPMN model, allowing you to analyze how the BPMN model and your data relate.
-
Drag and drop the
.bpmnfile that contains the BPMN 2.0 model you want to import.When the file is successfully imported, the Save & Review button will be enabled. -
Select Save & Review to finish the import of the BPMN model.
If you want to use a different BPMN model after you created the process app, you can import a BPMN model in Process manager.
BPMN model requirements
Below is an overview of the requirements to successfully import a BPMN 2.0 model for use in Process Mining.
General requirements for the BPMN model
-
The BPMN must adhere to the BPMN 2.0 standard.
-
The BPMN must contain a single process definition.
-
The BPMN can only contain supported elements.
-
All nodes in the BPMN should have an id.
-
The BPMN model should contain no more than 999 nodes.
Supported BPMN elements
The following BPMN elements ares supported:
-
Start events
-
End events
-
Tasks
-
Exclusive choice gateways
-
Parallel gateways
-
Sequence flows
Task and flow requirements
| Requirement |
Example |
| A start event must be defined, and there can only be one start event. |
|
| An end event must be defined, and there can only be one end event. |
|
| At least one activity task must be defined. |
|
| There must be at least two sequence flows defined for the BMPM model. |
|
| The tasks must have unique labels. |
|
| All sequence flows must have a source and a target. |
|
| Each task must have a single incoming, and a single outgoing sequence flow. |
|
| The start event only has a single outgoing edge. |
|
| The end event only has a single incoming edge. |
|
| All nodes and sequence flows in the BPMN are connected in a single model. |
|
Gateway requirements
The gateways in the BPMN must form pairs. Each pair has an opening gateway, which splits the process flow into multiple process flows. Each pair has a closing gateway, which joins the split process flows into a single flow. This structure is called a block. The flows inside a block may contain other, nested blocks. However, the only flows to enter and exit the flows within a block, are via the split and join gateways.
Below is an example of a BPMN model with gateway pairs, forming blocks. The blocks are highlighted.
|
Requirement |
Example |
|
Each gateway is either a split or a join gateway. | |
| A split gateway has a single incoming edge, and at least 2 outgoing edges. |
|
| A join gateway has at least 2 incoming edges, and a single outgoing edge. |
|
| For every split gateway, there is a corresponding join gateway of the same type, and vice versa. |
|
| Every split-join gateway pair and the elements between them are a single-entry-single-exit component: a model component that has only a single entry edge and a single exit edge. |
|
| Each path from a split gateway its corresponding join gateway must also be a single-entry-single-exit. |
|
| There cannot be any direct sequence flows between corresponding splitting and joining parallel gateways. |
|
| Every exclusive choice split-join gateway pair that describes a loop flow to a previous point in the process cannot have an empty main path and an empty redo path, as this allows for indefinite looping without a task being executed. |
|
-
Review the app details.
-
Select Create app.
The process app is created and will be displayed in the Process apps in development list. A progress bar is displayed to indicate the progress of the data ingestion of your process app.
When the data ingestion is completed, the new app will be published and displayed in the Process apps in development list.
You can now customize the app and edit the transformations to your needs. See Customizing process apps.
The app is in development mode and only available in the development environment. To make the app available to business users, you must publish the app. See Publishing Dashboards.
Upload data using extractor
If you have selected the Upload data using extractor option in the Selecting the data source step, the Upload data using extractor step is displayed.
End of upload API
When loading data using an extractor, you use the End of upload API in the post-event of in the extraction job to signal that the extraction was finished. See Create a job.
-
Copy the End of upload API and save it, for example, in a Notepad file.
-
Select Finish.
