With every release of a standard Process Mining app or discovery accelerator, UiPath will provide you with a link to download the UiPath Process Mining files.
As a developer, you must first create a release of the app or discovery accelerator. See Creating Releases. This release can then be deployed on the same server, or it can be distributed to be deployed to other servers. A release package consists of a specific version of an app. Typically, there is no data in this release package yet.
This document contains a quick guide for updating to the latest version of UiPath Process Mining and deploying an app or discovery accelerator to give end-users access to it.
Typically, the following roles are involved in deploying applications to end-users.
- a Superadmin account on your UiPath Process Mining installation.
- a dataset that is compliant with the app or discovery accelerator.
- downloaded the latest version of UiPath Process Mining.
- the release file (
.mvtag) of the app or discovery accelerator.
If you want to install UiPath Process Mining, you need access to an environment, and you need a valid UiPath Process Mining license. Please consult your UiPath Process Mining contact.
To update to the latest version of UiPath Process Mining and to make the latest version of the app or discovery accelerator available to end-users the following steps must be performed.
- Upload and activate the UiPath Process Mining build.
- Upload and activate the released version of the app or discovery accelerator.
- Generating a cache.
It is strongly advised to test the deployment of the new UiPath Process Mining release and perform these steps on a separate installation.
If the build used by the release is not yet available on the UiPath Process Mining installation, the build must be uploaded in the Builds tab.
Follow these steps to upload and activate the build.
Go to the Builds tab of the Superadmin page of your UiPath Process Mining installation.
Click on the menu icon in the top-left and select Upload build….
Drag the build file you downloaded, for example
Right click on the build that is uploaded and select Activate build.
The uploaded build is now activated.
See The Builds Tab.
In UiPath Process Mining 20.4 the look and feel has of the application has been changed, whereas the application code has been changed also to ProcessMining instead of ProcessGold. This change has effect while updating existing environments in the following ways:
- All user rights are linked to the application code and will need to be set up again. However, the users only will be able to open the application after the first cache with this code is finished.
- Existing end-user Favorites will be broken since those are linked to application codes.
To deploy the release, it must be activated in UiPath Process Mining. The release file of the app or discovery accelerator can be uploaded to the UiPath Process Mining installation either by using the upload option or by dragging a release file onto the Releases tab.
Follow these steps to upload and activate the release.
Go to the Superadmin Releases tab.
Click on the menu icon in the top-left and select Upload a release to this server… .
Right-click on the uploaded release file and select Make active on > production.
Select the desired default access for new modules, if any, and click on OK.
The Active on column now says production in front of the release and the release can be accessed by users with the proper access rights once a cache has been generated.
See The Releases Tab.
Next, data can be generated for the newly activated release. This data extraction can be scheduled to run every night, so the data is updated daily.
Follow these steps to generate a cache.
Go to the Superadmin Released data tab.
Click on Generate Cache Now.
Select the dataset you use for the app or discovery accelerator from the Dataset list and click on GENERATE CACHE.
When finished, click on CLOSE.
A window Loading Data… appears. If any unexpected errors are displayed during cache generation, please consult your UiPath Process Mining contact.
If a data extraction fails, the new release will not yet become available. End-users will see the last working version with the corresponding old data. Using the data instances screen, the extraction errors can be investigated, and it is possible to choose which version is shown to end-users.
Once data is generated for a certain release, the desired end-users can be given access to that release. See End User Administration.