Subscribe

UiPath Process Mining

The UiPath Process Mining Guide

Updating a Customized Version of AppOne

Introduction

When a new version of AppOne is released you should update your app to the new version. Normally, when updating, you would lose any custom adaptations you have made to AppOne. This guide describes how you can update to the new version of AppOne, without losing your customizations.

Application files

Make sure that you have the following <application>.mvp files available on your computer.

  • Your modified version of AppOne.
  • A clean version of AppOne of the same release your modified version is based on.
  • A clean version of AppOne of the release you wish to update to.

🚧

Important

These files must all have the exact same name.

Versions

To avoid errors, it is strongly recommended to update AppOne by at most one major release. While you can update AppOne by more than one major release at a time, it is recommended to keep your app updated when new versions come out to avoid having to update more than one major release at a time. To do this, it is recommended to keep a branch where you commit every major release of AppOne, so you can use this branch to update your app. No other commits should be made on this branch.

Setting up the branch for updating AppOne

Follow these steps to set up a branch to use for updating your customized version of AppOne to the newest version of AppOne.

📘

Note

If you have set up a branch for updating your customized version of AppOne before, you can use this branch and commit the newest version of AppOne on this branch.

Step

Action

1

Go to the Superadmin Workspaces tab of your developer environment.

2

Create a new branch.

3

Create a new workspace using the branch created in step 2.

4

Upload the <application>.mvp file of the version of AppOne on which your modified version is based on your workspace.

5

Commit your changes.

6

Upload the <application>.mvp file of the latest version of AppOne to your workspace.

7

Commit to save the newest version of AppOne to the branch.

8

When a new version of AppOne is released, upload the <application>.mvp file to your workspace and commit.

Updating your customized version of AppOne

Follow these steps to update your modified version of AppOne to the newest version of AppOne using the update branch explained in the previous section.

🚧

Important

Do not make any new commits when doing these steps, as this will mean you cannot use your update branch for updating more applications at a later point.

Step

Action

1

Go to the Superadmin Workspaces tab of your developer environment.

2

Open the workspace on the branch you created for updating AppOne.

3

Click on the Workspaces menu icon and select Show log....

4

Right-click on the commit belonging to the version of AppOne your customized version is based on and select Revert to revision.

5

Upload the <application>.mvp file of your customized version of AppOne to your workspace.
Your workspace now contains all modifications you made as local modifications.

6

Click on the Workspaces menu icon and select Update.
This updates your workspace to the latest revision, which is the newest version of AppOne (as long as your update branch is up-to-date).

7

Right-click on the <application>.mvp file and select Download file. This is your new updated version of AppOne with your customizations.

8

Right-click on the <application>.mvp file and select Revert. This reverts the workspace to the clean version of AppOne without customizations, so you can use the update branch again at a later point to update more apps.

Updated 4 months ago



Updating a Customized Version of AppOne


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.