The Bizagi Run portal is where admin users manage all projects and environments created in Automation Service.
To access the Run Portal, click the Run option the Management Portal.
A project created in Automation Service corresponds directly to a project developed in Bizagi Studio. A single project can contain two or more environments.
All project environments must have packages imported from the same Bizagi Studio project.
The projects and environment features available are:
•Create and delete projects
•Create and delete environments
•Import (deploy) packages to Testing environments to conduct user-acceptance tests, and to Production environments, so end users can use the final production versions of your applications. When importing (deploying), take into account all steps mentioned in the Importing a process article. Some additional steps are required when bringing an application live in Automation Service (whether Test or Production environment). Learn more in From Studio to the cloud.
Project and environment creation requires a commercial agreement to be in place. A sales representative is ready to help you with this. Contact us.
Creating new projects
To create a project, go to your subscription and select the green plus icon.
Give the new project a name and a brief, meaningful description.
All projects must have unique names, even within subscriptions.
Bizagi creates the project without environments.
The subscription owner can delete projects at any time. Bear in mind that this action is not reversible and will delete every environment contained in the project you delete.
Once you select this option, Bizagi displays a confirmation dialog to make sure you want to delete the project.
Type the name of the project and mark the checkbox Yes, I want to delete the project. Then click the Delete button.
Every project has information displaying the number of active, created and with-error environments. They display under the project name:
•Total environments: The number of created environments.
•Active: The number of environments with an uploaded package.
•Created: The number of environments without an uploaded package.
•Error: The number of environments with error(s) when running the uploaded application.
When an environment presents errors, please contact our support team.
Creating new environments
Creating a new environment lets you upload a packaged application and run it. New environments are created in the latest available Bizagi Version.
To create a new environment, select the Create environment option in the three-dotted menu for the project.
Select the environment category for the environment. Contact us if you want to create an environment with a category different from Trial.
Give a meaningful name, of up to 20 characters, to the new environment.
When you are ready, click Continue.
Bizagi displays the environment characteristics. Click Create to start creation of the project.
During environment creation, do not close your browser or log out until the process finishes to avoid errors.
The new environment will have the Created state, which means it is ready to upload and install an application package.
Importing a package
Importing a package is a deployment to a Automation Service environment. This action requires steps you must follow carefully. An article detailing each step and consideration can be found here.
Running an application
When you click the Run button, the Work Portal of the environment opend in a new window. The Work Portal is where end users or testers work with the uploaded application.
The Work Portal's URL will vary depending on the environment:
•Testing environment's URL:
•Production environment's URL:
Make sure you have imported an application package before running the Work Portal. If you have not, the server displays an empty Work Portal.
Monitoring an environment
Each environment has an Activity Monitor icon so you can monitor the environment's resource use and BPUs consumed.
A thorough explanation of monitoring is found in the Resource monitoring article.
Deleting an environment
Every environment can be deleted. All data stored in the environment, along with log files and metrics, is deleted with it.
Select the trash can icon of the environment to delete.
Once you select this option, Bizagi displays a confirmation dialog to make sure you want to delete the environment.
Type the name of the environment and mark the checkbox Yes, I want to delete the environment. Then, click the Delete button.
Updating an environment
When an environment uses an older Automation Server Version, you can update it to the last available version by clicking the Update to [Version] button.
Deploying from one environment to another
You can deploy an application you have in one environment directly into another one, as long as the target environment is empty and has been created within the same Automation Service project. Select the Deploy to another environment option in the three-dotted menu of the environment.
A window displays to let you select the target environment. Click Make deployment to deploy the application.
This system deploys the application but NO DATA is copied from the source environment to the target one.
Changing the category of an environment
You can change an environment's performance level to match demand. This option is available for Enterprise subscriptions.
To request a change in the Performance Level, locate the Change category option within the three-dotted menu of the environment. For more information, refer to Scaling an environment.
Resetting an environment
Bizagi's Run Portal lets you reset your Bizagi server, which is like cleaning up the cache of a browser, to allow changes deployed to be updated in the Work Portal.
To reset your Bizagi Server, locate the Reset option within the three-dotted menu of the environment. For more information, please refer to Resetting an environment.