Teamwork collaboration through Bizagi Studio

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Bizagi Studio installation > Teamwork setup >

Teamwork collaboration through Bizagi Studio

Overview

Bizagi Studio provides a collaborative environment where you and co-workers can work simultaneously on the implementation of processes.

Bizagi supports a teamwork collaborative setup for the Development/Authoring environment, so that you can move an existing Bizagi project into a central server anytime (or create a new one), and have several users work with from their workstations.

As a result, everyone can work at the same time on the same set of processes, and use the teamwork collaboration features as described at Teamwork setup.

 

 

Bizagi Studio connectivity features

Through Bizagi Studio connectivity features, Bizagi Studio is used both at the server to host the project, and to connect to and work on that project from workstations.

This is the recommended setup for teamwork collaboration in the implementation of processes, the one most widely used in corporate automation initiatives since it easily enables people with different profiles and skills to work together.

 

This setup requires that the network connection between workstations and the central server hosting the project presents an optimal latency (ideally the workstations being on the same network of the central server).

No special considerations required when installing Bizagi both at the server or at user workstations and no special hardware or appliances are required.

Given that it common that the Development environment is set up at the corporate premises, where the network configuration involved for this usually meets the optimal conditions, and due to the fact that Bizagi Studio does not require licenses, this alternative is recommended for teamwork collaboration.

 

The following image illustrates this concept:

Development_using_Bizagi_Studio

 

Technical requirements

For the communication between workstations using Bizagi Studio and the Development servers, the following technical requirements must be met:

Enabled UDP port numbers: 50051, 50052 and 50053 to initially establish communication with Bizagi services.

Enabled TCP port number 5679 to send and receive information.

Enabled TCP port number specific of your database service (e.g, 1433 by default for SQL Server, 1521 by default for Oracle, or similar).

A local admin account at the central server to create the Bizagi project (or further administration tasks such as to upgrade the project's version, or deploy the processes to another environment). Users connecting to the created project to work on the implementation do not need administrator rights but an authorized entry at the Bizagi group.

 

 

What you need to do

You will first need to explicitly define:

The database server having a SQL Server or Oracle instance installed.

For doubts about the required configuration for this server, refer to Database server requisites.

The server to be the central server, hosting the Bizagi project.

It is recommended to use a different dedicated server to host your Bizagi project, though you may use the same Database server to use Bizagi Studio and host your Bizagi project according to the characteristics of your implementation.

Which users will be working on this project, by connecting from their workstations to the central server.

 

For a teamwork collaboration setup, these steps are carried out:

1. Install Bizagi Studio at the central server.

2. Create the Bizagi project at the central server.

3. Include authorization entries at the central server for your users.

4. Install Bizagi Studio in each of the workstations of users connecting to this project.

5. Connect to the project, from each of the workstations.

 

 

Procedure

Follow these steps to achieve teamwork collaboration through Bizagi Studio.

 

1. Install Bizagi Studio at the central server.

Install Bizagi Studio by running the installer with administration rights at the central server.

Carry out the installation steps as described at Quick start setup, but this time you may skip the option to install a bundled SQL Server instance and use the corporate instance of your database server.

 

You may verify access to your database if you will be using a SQL Server instance:

 

install04

 

 

2. Create the Bizagi project at the central server.

Upon a completed installation, create a new Bizagi project at the central server, as described at Creating a new project.

Recall that in order to create a Bizagi project, you need a local admin account.

 

If you already have some progress on an existing project, it is still best that you create a new project at this server.

Then, you may easily import your progress by creating a backup of your existing project's database, and restoring this backup into the new project's database.

 

 

note_pin

If you are using a SQL Server database, and you are relying on advanced configuration of SQL Server login accounts, make sure you create the project by specifying the use of an authorized login account.

You will need a Process administrator login account or an account with higher privileges, as described at Advanced configuration of SQL Server login accounts.

 

 

3. Include authorization entries at the central server for your users.

At the central server, make sure you add as users all of your team member's accounts into the Bizagi group.

Notice that this group is created automatically by Bizagi's installation and by default, only the local administrator is included.

 

To add users into this group, browse the local management options to locate the local user and groups item.

Right-click on the Bizagi group to use the Add to group.. option:

 

WorkingRemote01_BizagiGroup

 

Then choose specific users which will be authorized to open the project:

 

WorkingRemote02_BizagiGroup

 

 

note_pin

You may also rely on Bizagi Studio security feature, in order to define authorization options of who can work in which processes.

For more information about this option, refer to Bizagi Studio security.

 

4. Install Bizagi Studio in each of the workstations of users connecting to this project.

Install Bizagi Studio in each of the workstations of the team users.

Make sure:

You install exactly the same Bizagi Studio version installed at the central server (as in step #1).

You run the installer with administrator rights.

 

Carry out the installation steps as described at Quick start setup, but this time you may directly use the option to skip the steps related to the database instance.

 

 

5. Connect to the project, from each of the workstations.

To connect to the project from the workstations, open Bizagi Studio, and select the Recent Projects option at the main window.

 

 

Working in Bizagi with your team1

 

Select the central server hosting the project, and then select the project.

Then click Finish.

 

Working in Bizagi with your team2

 

 

note_pin

If you are using a SQL Server database, and you are relying on advanced configuration of SQL Server login accounts, make sure you connect to the project by specifying the use of an authorized login account.

You will need a Process analyst login account or an account with higher privileges, as described at Advanced configuration of SQL Server login accounts.

 

Once the project loads up, you will have ensured that the setup is complete.

From this point on, process analysts may connect to this project by simply using the shortcut appearing in the Bizagi Studio splash window:

 

TerminalS_Workstations

 

Important

In this setup, it is important to acknowledge that deployment of processes (promoting and publishing the processes from the Development environment to a Test or Production environment), as well as upgrading your Bizagi version needs to be done at the central server.

It is not recommended to perform such tasks (deployments, project upgrades) from user workstations.

 

 

note_pin

In this type of setup, it is also important to ensure that the UDP port number 11000 is allowed in all machines with Bizagi Studio installed.

This UDP port is involved in the cache communication and synchronization used by Bizagi's components.