- Hardware and Software Requirements
- Server Installation
- Updating the License
- Deploy a Release
- End User Administration
- Cache Generation
- Environments
- 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
- Introduction to SAP Connector
- 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
- 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
Deploy a Release
Introduction
Deploying a release requires the following steps:
Uploading a Release
A release that has been made available by a developer as an .mvtag
file can be uploaded to the server either by using the upload option, or by dragging a release file onto the Superadmin Releases tab.
Follow these steps to upload a release.
Step |
Action |
---|---|
1 |
Go to the Superadmin Releases tab. |
2 |
Click on the menu icon in the top-left and select Upload a release to this server…. |
3 |
Drag the desired release file onto the Upload File dialog or browse for it on your computer. |
4 |
Click on OK. |
The uploaded release is now visible in the list of releases.
Importing a Release
An existing release can be imported from a repository.
Follow these steps to import a release from the repository.
Step |
Action |
---|---|
1 |
Go to the Superadmin Releases tab. |
2 |
Click on the menu icon in the top-left and select Import a release from the repository…. |
3 |
Select the repository that contains the desired release. |
4 |
Select the branch that contains the desired release. |
5 |
Select the desired release. |
6 |
Click on IMPORT. |
The imported release is now visible in the list of releases.
Uploading a Build
The build used by the release must be available on the server to be able to activate the release. Which build is used by the release can be seen in the Build column in the Releases tab. If it is not yet available, the required build can be uploaded in the Builds tab. The build should be made available by the developer.
Follow these steps to upload a build.
Step |
Action |
---|---|
1 |
Go to the Superadmin Builds tab. |
2 |
Click on the menu icon in the top-left and select Upload build…. |
3 |
Drag the desired build file onto the dialog or browse for it on your computer and click on OK. |
4 |
Right click in the list on the build that has been uploaded and select Activate as Superadmin. |
The uploaded build is now activated and visible in the list of builds.
See: The Builds Tab.
Activating Releases
When activating a release, a dialog is shown. Any modules not present in the previous active release are highlighted in green.
The default access rights of these new modules can be set to:
- All users: all current and future users will automatically have access to the module.
- No users: no current or future users will initially have access to the module. The individual user rights will need to be set for the module.
Any changes in the name and/or description of previously active modules will be highlighted in orange.
See illustration below.
Follow these steps to activate a release.
Step |
Action |
---|---|
1 |
Go to the Superadmin Releases tab. |
2 |
Right click on the release that is to be activated. |
3 |
Select Make active on - production. |
4 |
Select the desired default access for new modules, if any. |
5 |
Click OK. |
The Active on column now says production in front of the activated release and the release can be accessed by users with the proper access rights once a cache has been generated.
See: The Releases Tab.
Automated release deployment
The following command-line functions are available that you can use to automate your release pipeline:
ImportRelease
to import releases either from a local file or a Git repository.ActivateRelease
to activate the release.
You can use these commands in a batch script, to automatically release a new version to different (production) environments.
For example, the processgold.bat
script that is available in the Builds folder of your UiPath Process Mining installation.