Running a project

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio Collaboration Services > Accessing Studio Collaboration Services >

Running a project

Overview

Running your processes in the Work Portal is a crucial part of the development cycle since this is the way you can be sure that your processes are working as expected. This functionality works slightly different in Studio Collaboration Services compared with how they work in your On-premises Studio. This article explains all the important considerations you must have when running your Work Portal from Studio Collaboration Services.

 

Use Cases

With Studio Collaboration Services, you have several options available for your project development and execution. This article shows a brief description of each case.

 

Developing your projects on the cloud and running them in a cloud environment

The most common use case for our Studio Collaboration Services, since this let you use the full capability of our cloud offerings. Here developers all around the world can develop and test their projects in a single subscription-based platform. You must have at least one environment for each of your projects. This scenario lets you share Your Work Portal and your Studio among all your developers. They can improve and test your processes from any place, at any time, and reflect all changes to everyone.

 

Developing your projects on the cloud and running them in an on-premises environment

In this scenario, you produce your processes on a cloud-based Studio and test them at your machine. You must create a local execution environment in which your Work Portal will run. To correctly provision this environment, follow the steps described at Running a project locally. This Work Portal exists in your machine and is not shared with the members of the subscription.

 

Bringing your on-premises projects to a cloud-based environment

This scenario is quite common when you first acquire Studio Collaboration Services, and you want to bring all your previously developed processes to your subscription environment. The article From on-premises to Studio Collaboration Services explains this particular scenario.

 

How to run your Studio Collaboration Services project on the Cloud

The first time you run your project, you must link it with a cloud environment. Follow these steps to associate your project with a free environment.

 

note_pin

Before linking a project with an environment keep in mind that you can only relate one project to one environment. If all your environments are linked to a project you need to buy a new environment or disjoin a project from its environment.

 

1.In the Home tab, Click Run on cloud located in the project group. You can also find this option in the Cloud Services tab.

 

RunCloud000

 

2.A pop-up window appears asking if you want to relate your project to an environment. Click Yes.

 

RunCloud001

 

3.Bizagi will automatically find an available environment and link your project to it. this action may take several minutes.

 

RunCloud002

 

From this moment onwards, when you click the Run on cloud button, Bizagi will open the Work Portal. Furthermore, in the Cloud Services tab the Management Console web button appears to let you start the console where you can administer Development environments. For more information, refer to Management Console web.

 

RunCloud003

 

Differences with the run functionality in Studio on premises

Since Studio Collaboration Services run works slightly different than the On-Premises Studio. Keep in mind these differences when working with Studio Collaboration Services.

 

1.To reflect any changes in your Work Portal, you must click the Run button. Refreshing your Work Portal doesn't synchronize it with your Studio modifications. To reflect your changes in your Work Portal, you must click the Run button.

2.Each time you run your Work Portal, all volatile information is lost. As such, if a colleague is filling a form or executing a query when you click Run, this information will be lost. We strongly suggest that you define running time windows with your colleagues beforehand to avoid any inconveniences while developing and testing your processes. Saved data is not volatile data as such, continuously saving your changes is a recommended practice.

3.If you make any modification to these elements:

Entities

Attributes

Facts

Component libraries

Rules

Business options

Environment parameters

Authentication

 

A maintenance window appears for all the users during the synchronization of these changes. Click Run after a few minutes to remove the maintenance window.