process-mining

2021.10

true

Release notes
- 2024
  - 2021.10.4
- 2022
- 2021
Getting started
- About Process Mining
- Introduction to UiPath Process Mining
- User roles
- UiPath Process Mining components
- Platform architecture
  - Server architecture
  - Integration options
- From data to dashboard
- App and Discovery Accelerator development
Installation
- Hardware and software requirements
- Server installation
- Updating the license
- Deploying Apps and Discovery Accelerators
- Deploying the UiPath Process Mining Profiler
- Deploying a Connector (.mvp)
- Updating UiPath Process Mining
- Updating a customized version of an App or Discovery Accelerator
- Installing a training environment
Configuration
- Server configuration
- Using a Git repository
- Creating accounts for developers
  - Two-Factor authentication
- Backup
- About telemetry
- Set up Audit Logs
  - Category details
Integrations
- Set up integration with UiPath Automation Hub
- Set up Actionable Insights
Authentication
- Set up single sign-on through Azure Active Directory
- Set up single sign-on through Integrated Windows Authentication
- Set up single sign-on through SAML for Microsoft Active Directory
  - Configuring ADFS
- Adding Superadmin AD Groups
- Adding End-user AD Groups
- Set up LDAP
- Two-Factor Authentication
- Set up a Credential store
  - Setting up an Azure Key Vault Credential store
  - Use a Credential store
Working with Apps and Discovery Accelerators
- Working with charts
- Working with Process graphs
- Sending automation ideas to UiPath Automation Hub
- Filters
- Favorites
- Export
- Selecting the preferred language
AppOne menus and dashboards
- Introduction to AppOne
- Analyzing data in AppOne
- Overview of menus and dashboards in AppOne
- Menu Overview
- Menu Process
- Menu Timing
  - Timing - Timing
  - Timing - Due Dates
- Menu Conformance
- Menu Users
- Menu Details
AppOne setup
- Input tables of AppOne
TemplateOne 1.0.0 menus and dashboards
- TemplateOne menus and dashboards
- Menu Overview
- Menu Analysis
- Menu Efficiency
  - Efficiency - Automation
- Menu Compliance
  - Compliance - Tags
  - Compliance - Due Dates
- Menu Details
TemplateOne 1.0.0 setup
- Getting Started with TemplateOne
- Steps to roll-out TemplateOne 1.0.0
- Input tables of TemplateOne 1.0.0
- Adding custom attributes
- Configuring the context bar
TemplateOne menus and fashboards
- TemplateOne menus and dashboards
- Menu Overview
- Menu Analysis
- Menu Efficiency
  - Efficiency - Automation
- Menu Compliance
  - Compliance - Tags
  - Compliance - Due Dates
- Menu Details
TemplateOne 2021.4.0 setup
- Getting started with TemplateOne
- Steps to roll-out TemplateOne
- Input tables of TemplateOne
  - Input tables of TemplateOne 2021.4.0
- Loading data into TemplateOne
Purchase to Pay Discovery Accelerator menus and dashboards
- Introduction to Purchase-to-Pay Discovery Accelerator
- Analyzing data with Purchase-to-Pay Discovery Accelerator
- Overview of menus and dashboards
- Menu Overview
  - Overview - Procurement
  - Overview - Accounts Payable
- Menu Procurement
- Menu Accounts Payable
- Menu Efficiency
- Menu Compliance
- Menu Details
Purchase to Pay Discovery Accelerator Setup
- Input tables of the Purchase-to-Pay Discovery Accelerator
  - Input tables of Purchase-to-Pay Discovery Accelerator 21.10
  - Input tables of Purchase-to-Pay Discovery Accelerator V. 21.4
- Adding automation estimates
Order to Cash Discovery Accelerator menus and dashboards
- Introduction to Order-to-Cash Discovery Accelerator
- Overview of menus and dashboards
- Menu Overview
- Menu Analysis
  - Analysis - End to End
  - Analysis - Deviations
- Menu Efficiency
  - Efficiency - Automation
  - Efficiency - Customers
- Menu Details
  - Details - End to end
Order to Cash Discovery Accelerator Setup
- Input tables of the Order-to-Cash Discovery Accelerator
  - Input tables of the Order-to-Cash Discovery Accelerator V21.4.1
  - Input tables of the Order-to-Cash Discovery Accelerator 21.4
- Adding automation estimates
Basic Connector for AppOne
- Deploying the Basic Connector
- Introduction to Basic Connector
- Input tables of the Basic Connector
- Loading data
  - Mapping attributes
  - Cleaning input data
- Adding tags
- Adding automation estimates
- Adding Due dates
- Adding Reference models
- Setting up Actionable Insights
- Setting collapsible charts
- Using the output dataset in AppOne
- Output tables of the Basic Connector
SAP Connectors
- Introduction to SAP Connector
- Loading data in the SAP Connector for AppOne
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
SAP Order to Cash Connector for AppOne
- Order-to-Cash Process in UiPath Process Mining
  - Roles in the Order-to-Cash process
- Introduction to SAP Order-to-Cash Connector for AppOne
  - Entities
  - Activities
- Input Data of the SAP Order-to-Cash Connector for AppOne
- Other settings
- Optional attributes
- Order-to-Cash tags
- Order-to-Cash Due dates
- Order-to-Cash Reference models
SAP Purchase to Pay Connector for AppOne
- Purchase-to-Pay process in UiPath Process Mining
  - Roles in the Purchase-to-Pay process
- Introduction to SAP Purchase-to-Pay Connector for AppOne
  - Entities
  - Activities
- Input data of the SAP Purchase-to-Pay Connector for AppOne
- Other settings
- Purchase-to-Pay tags
- Purchase-to-Pay Due dates
SAP Connector for Purchase to Pay Discovery Accelerator
- Introduction to SAP Connector for Purchase-to-Pay Discovery Accelerator
  - Entities
  - Activities
- Input Data of the SAP Connector for Purchase-to-Pay Discovery Accelerator
- Configuring the SAP Connector for Purchase-to-Pay Discovery Accelerator
- Configuring the activity code
SAP Connector for Order-to-Cash Discovery Accelerator
- Introduction to SAP Connector for Order-to-Cash Discovery Accelerator
  - Entities
  - Activities
- Input data of the SAP Connector for Order-to-Cash Discovery Accelerator
- Configuring the SAP Connector for Order-to-Cash Discovery Accelerator
Superadmin
- The Superadmin page
- Collaborative development
  - Workspace conflicts
  - Commit
- Creating releases
- Viewing the branch history
- Creating Apps
- Modules
Dashboards and charts
- Creating dashboards
- Adding charts on a dashboard
- HTML panels
- Process graphs
- Legacy charts
  - Adding a compare period filter to a dashboard
- Migrating legacy charts to new charts
Tables and table items
- Connection string tables
  - Connection string types
  - Table scope
- Join tables
- Global tables
- Introduction to table items
- Datasource attributes
  - Attribute selectors
  - Adding new attributes to an App or Discovery Accelerator
- Metrics
- Filters
- Display format
- Expressions
- Maps
- Actions
Application integrity
- Maintain Application integrity
- Application issues
  - Finding Application issues
  - Solving Application issues
- Application Profiling
  - Profiling aalysis
  - Example analysis
How to ....
- Rebrand and restyle Apps and Discovery Accelerators
- Translate apps
- Use sharding in your applications
- Use generic script datasources
  - Example: Creating a Python Script
  - Example: Creating an R Script
- Create an anonymized dataset
- Set up native SAP extraction
  - Installing the Z_XTRACT_IS_TABLE Function Module on Your SAP System
- Set up automated data refreshes
- Use an access matrix to enable role-based access to data
Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
Useful resources
- Troubleshooting
- Performance
- Security

Process Mining

DELIVERY:

DELIVERY:

Automation Cloud Automation Cloud Public Sector Automation Suite Standalone

RELEASE: 2021.10

Last updated Sep 2, 2024

Separate development and production environments

Introduction

This page describes a suggested setup for separate production and development environments. This enables you to work together with multiple developers on a SQL connector. After all changes are done, a finished SQL connector can be released to a production environment.

See the illustration below for an overview of the suggested setup.

This is a suggested setup.

SQL Server Database

There are two instances of the SQL Server database, one for development and one for production.

SQL Server database instance	Description
Development database	• All developers should have access to the development database to inspect the data and validate transformations. • A schema per developer (per connector) should be created to ensure that developers do not interfere with each others work while running transformations during development.
Production database	• Access to the production database can be granted on a need-to-have basis or based on a certain role. • Only one schema is required that contains the production data.

Instead of two separate SQL Server database instances you can choose to store the development and the production schemas in one SQL Server database.

CData Sync

There are two instances of CData Sync, one for development and one for production. For both instances, the basic installation instructions should be followed. However, there are some differences in configuration.

CData Sync instance	Description
Development environment	• A CData Sync user account per developer should be created such that each developer can create connections and jobs for development and testing purposes.
Production environment	• Only user accounts needed to configure production runs are needed. • Only jobs and connections necessary to extract production data and store it in the production SQL database are required.

Instead of two separate CData Sync instances you can choose to store the development and the production jobs in one CData Sync instance.

Dbt

Dbt needs to be installed on the local development workstations and on the production server. Local developers only use the development database, whereas the production instance of dbt will connect to the production database.

Dbt consists of multiple parts, the core dbt-core and some adapters like dbt-sqlserver. Make sure the version of each of the components is the same on all environments to prevent problems. Refer to the dbt documenation for a list of available adapters.

Connector Checkout

See Setting up a SQL connector for a description on how to make a connector checkout for a new SQL connector.

On this page

Introduction
SQL Server Database
CData Sync
Dbt
Connector Checkout

Was this page helpful?

PREVIOUSSetting up a local test environment

NEXTTroubleshooting

Support and Services

Get The Help You Need

Learning RPA - Automation Courses

UiPath Community Forum

Trust and Security

© 2005-2024 UiPath. All rights reserved.