Studio Collaboration Services Considerations

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio Collaboration Services >

Studio Collaboration Services Considerations


Bizagi Studio empowers development teams for intelligent process automation fulfilling business requirements with agile results, and focusing on your business. Through features that help automation of processes, and a set of different applications, features, and functionalities offered by Bizagi, developers control the business logic, enhance the user interface, and integrate systems in the development environment.


When using Bizagi Studio, you have two options. You can work collaboratively using on-premises resources, where all the underlying infrastructure related to your development environment  are managed and run by you. This option is usually very costly and demands resources for its management. A second option is using a Studio Collaboration Services subscription, in which Bizagi takes care of your infrastructure in the cloud, offering services so globally distributed teams can work collaboratively.


There is a list of features that are applicable to on-premises projects because they are built for administration of resources rather than features that you can use in a process. In a Studio Collaboration Services subscription, the administration of all resources is managed by Bizagi, which means that you no longer need those features.  When you are working using a Studio Collaboration Services subscription in the cloud, you do not have to worry about features that apply to on-premises projects.


As explained here, you can migrate from On-Premises projects to Studio Collaboration Services as soon as you purchase a plan.  In this scenario, you should review features which are intended to work on On-Premises projects. This article presents all the features that apply to On-Premises projects and points to consider when developing using Studio Collaboration Services.


Features that apply to On-Premises projects

Bizagi Studio can be used to build business applications for both On-Premises or run on the cloud environments, while Bizagi Studio not being aware of which of the two is the final target of your implementation. Some features and configuration parameters that you find in Bizagi Studio are built to manage and complement On-Premises components. For example, features like the Bizagi database encryption, make sense for On-Premises setups, where the customer is entirely in charge of the technological stack (managing the database server and its access, operating systems, redundancy options, etc.), and may rely on this feature to choose to encrypt sensitive/confidential information.

Such configuration is not targeted for, nor taken to Studio Collaboration Services, given that for the cloud Bizagi already manages encryption for data at rest. Encryption for data at rest is in place with Studio Collaboration Services, and this is taken care of by the cloud expert operations team personnel, rendering customer data secure in terms of integrity, privacy, and availability.


Configuration Options

The following options apply to On-Premises projects:

Bizagi database encryption.

Operational Data Store.

Query Engine ODS.

Scheduler options (environment configuration).

Email integration (in SCS is done by Bizagi when the environment is provisioned).

Tracing configuration


Bizagi Studio displays a message next to these options that are applicable to On-Premises projects.




Additional features that apply to On-Premises projects

The following features are not part of the environment configuration, therefore there is no message warning that apply to On-Premises projects. However, you need to note that the following features cannot be used or configured through Studio Collaboration Services:

Unused objects cleanup

This option cleans the meta-data of unused objects. Click here.


There is no license per user in Studio Collaboration Services therefore you do not need to manage any licenses.

One-click deployment

When you use Bizagi cloud services, you deploy by exporting a BEX file containing metadata. Therefore One-click deployment does not apply to Studio Collaboration Services projects.

Entities Values

The values of master, parameter or application entities are not displayed in the expert view. Refer to Manage values of entities in Studio Collaboration Services.

Migrate users to stakeholders

This feature lets you assign stakeholders using rules. This option is not applicable to Studio Collaboration Services.


Considerations about using Studio Collaboration Services as your cloud development environment

When working on Studio Collaboration Services, you can run the Work Portal in two ways:

Using the Studio Collaboration Services cloud infrastructure. You can run as many portals as the number of packages you have purchased. Refer to Studio Collaboration Services.

Using local resources. In this scenario, you have to install all the necessary infrastructure to run the Work Portal. Refer to Studio installation.

If you run the Work Portal using the Studio Collaboration Services cloud infrastructure, you need to consider the following:


1. Running the Work Portal

With one purchased package, you can run one project in the cloud. Other projects must be executed locally. Refer to Running a project. Additionally, always see the latest changes done by your co-developers, you have to execute the Work Portal clicking the Run button in Bizagi Studio. Do not access the Work Portal directly from the browser URL or by refreshing it.


2. Work Portal Authentication

The Work Portal in Studio Collaboration Services supports the following authentication types:

SAML 2.0

OAuth (with OpenID extension)


LDAP (this requires a VPN)

Other authentication types not listed above cannot be used in Studio Collaboration Services.



These authentication types are available for the Work Portal of the development environment. Developers access Bizagi Studio use different credentials, which are related to the subscription.


3. VPN

Virtual Private Networks are supported for SCS.  Whenever the applications you want to integrate with, do not offer a cloud-ready architecture and use protocols other than HTTP/HTTPS, you can use a VPN to perform Unit tests for integrations with those systems. The VPN is an additional service with extra cost.


Features that are configured in Bizagi Studio and require to retrieve information in the configuration wizard from an endpoint, are:



Web Services



Consider as cloud-ready, systems and services which are either cloud-native, cloud-enabled or simply published for access through a public channel such as the internet. This means a service which has an HTTP/HTTPS (the later preferred) endpoint.


4. Integration with other systems and services

When you configure integrations in Bizagi Studio using Studio Collaboration Services, and you want to test them using your cloud Work Portal, you must consider the following:


4.1 ECM

If you are developing an integration with ECM systems using the Bizagi out-of-the-box connector, as explained here, your CMIS compliant system must be cloud-ready (published and accessible via HTTPS through the internet). If your ECM system does not comply with this, you need a VPN.


4.2 Web services and connectors

If you plan to configure and test invocation of web services (SOAP or RESTful) or connectors using the Work Portal in Studio Collaboration Services, the external system has to expose those services to be accessible via the internet. That is, those services must be cloud-ready. If your external system services are not cloud-ready, you need a VPN.


4.3 SMTP

Acquiring a Studio Collaboration Services plan allows the use of Bizagi’s cloud e-mail service to send notifications. This service is available for the project that you run on the cloud. No further configuration is needed in SMTP for your cloud environment.

Alternatively, you may also choose to provide your own SMTP, that MUST be cloud-ready.

If run a project locally you must configure the SMTP in Bizagi Studio.


When relying on Bizagi's cloud e-mail service, bear in mind that each email cannot be larger that 19MB, and attachments cannot exceed 7MB. If the email exceeds these values, it will not be sent.


4.4 Email Integration

Bizagi features a functionality to complete tasks via e-mail. Refer to Completing tasks via E-mail. When using this option with Studio Collaboration Services, you need an Exchange service mailbox. Other protocols different from Exchange, such as POP3 or IMAP, do not apply to this functionality unless you run the Work Portal with an On-Premises technological stack infrastructure.


4.5 Integration with other databases

Consider the following when integrating with your databases through Data Virtualization and Data Replication:

Integrating with Oracle databases or other engines different than On-Premises SQL Server instances, is not supported.

External Database must be accessed over the internet and be cloud-ready, in configuration and runtime.

Data Virtualization and Data Replication need a VPN.

If you use a VPN for Data Virtualization and Data Replication, use this feature wisely due to performance considerations.

Test provider option requires direct access to a local on-premises IIS (Internet Information Services) and is not available in SCS.

Access to an external database over the internet (from Bizagi PaaS), inherently depends upon factors which are beyond Bizagi's control, such as higher latency in data transmission, fluctuations, interference, and congestion affecting the speed of the channel, the quality of the networks used during transmission, etc. Using this feature wisely means that you have to analyze your application and assess your use cases thoroughly so that you can determine if they can sustain the performance. Most often, working on information of one record is okay; while fetching multiple records and working in them may not give a good user experience.


4.6 Component libraries

Although component libraries are supported in Studio Collaboration Services (to be deployed anytime on Automation services), recall that Bizagi cloud services, including Studio Collaboration Services, is built for scalability. Cloud computing resources are made available on-demand as elastic resources, so, point-to-point integrations which demand the installation of a component in a specific location are not a best practice. Additionally, you have no direct access to any folder or database located within the cloud infrastructure managed by Bizagi.


If you have no other option with integration types offered by Bizagi, and you develop a component library, consider that components must be self-contained (i.e, all libraries needed by a component must be uploaded via the component library). This means that a component may not rely on drivers, DLLs, files in general, or a connectivity setup that needs to be installed separately into the local machine.


4.7 SOA Layer and OData

External system invoking services from the Bizagi SOA layer or OData services have to be done using public channels such as the internet. If your external system is not cloud-ready, you need to use a VPN.


4.8 LDAP synchronization

You can use an LDAP system for two purposes. Authentication of the Work Portal, and synchronization of users. Synchronization of users is available for Studio Collaboration Services using a VPN. Therefore, you can see the LDAP configuration node, accessed from the Security module in the expert view only if you purchase a VPN.


5. UI extensibility and Work portal customizations
Widgets are supported and highly encouraged for enhancing the user interface. Performing customizations that modify the files, that are shipped in with Bizagi (such as JS, HTML or CSS overrides and modifications) directly must be coordinated with our support team with a notification in advanced using the ticket platform. Please share with the support team what you intend to do before actually requesting the modifications.

You may not modify the web.config file; or any other aspects of the Bizagi Work portal except through the theme builder or out-of-the-box features in general (Modifications of  IIS settings are also not allowedl). With your subscription to Studio Collaboration Services, you have access to a team of Bizagi experts, who take care of all infrastructure and services, and its related IT tasks involving provisioning, maintenance and tuning, and general technical support (includes 24x7 monitoring), so that you as a customer do not need a DBA, platform admins or other IT-related staff.


6. Deploying from Studio Collaboration Services to Automation Services

In Studio Collaboration Services you are able to work collaboratively in multiple projects in the same subscription. This permits to work on projects used as sandboxes for test or proof of concept purposes. Nevertheless, in Automation Services you can run one project per subscription. When you are deploying from Studio Collaboration Services to Automation Services, you cannot deploy different projects in the same Automation subscription. Make sure that you choose properly the project that you want to keep deploying in your cloud-based test or production environments.


7. Performing a Studio version upgrade

As part of Bizagi's continuous improvement, new versions are released periodically with new features and fixes. When you wish to upgrade your version for Studio Collaboration Services you have to create a ticket in our support portal requesting for the version upgrade.


Summary of considerations

The following table sums up the features not applicable to Studio Collaboration Services and considerations when you develop an application using our cloud service.



Feature / component / property

Supported in Studio Collaboration Services?

Environment Parameters

Bizagi database encryption


Operational data store (ODS)


Query engine data store


Scheduler options


Email integration

Configured by Bizagi. If the customer is using a server  different from cloud operation's, must be an Exchange server only.


Configured by Bizagi. If the customer is using a server  different from cloud operation's, must be cloud-ready.

Management Console Web

Clean cases

Scheduler - user jobs

Scheduler -waiting jobs

Scheduler - alerts jobs

Scheduler - system jobs


Admin password

Cluster management


External systems - Interfaces

External systems - Connectors

External systems - ECM

External systems - Excel connector


Organization - groups

Organization Working time schema

Data import / export

Bizagi Studio interface

Unused objects cleanup


Share processes



The Sites editor will open in the last environment the project was run.

Migrate users to Stakeholders


Studio Security for entities and global business rules


Work Portal Authentication


This applies to the project that you are running in the cloud Studio Collaboration Services infrastructure

SAML 2.0

OAuth 2.0



Applicable if the external system is cloud-ready. Otherwise you need a VPN.









Synchronizing users


Applicable if the external system is cloud-ready. Otherwise you need a VPN.


With SOA Layer method

If the external system invokes the SOA layer using a public channel such as the internet, otherwise, you need a VPN.

Data integration


Virtualization or replication

MS SQL server external DB

Applicable if the external system is cloud-ready. Otherwise, you need a VPN.

Oracle external DB




Integration with External Systems

Web services - SOAP or REST

Applicable if the external system is cloud-ready. Otherwise you need a VPN.


Applicable if the external system is cloud-ready. Otherwise you need a VPN


Applicable if the external system is cloud-ready. Otherwise you need a VPN

SAP using connectors

Applicable if the external system is cloud-ready. Otherwise you need a VPN

SAP using Bizagi Studio embedded connector


Component library

Applicable if the library is self-contained.


If the widget consumes services, they need to be cloud-ready

SOA Layer

If the external system invokes the SOA layer using a public channel such as the internet, otherwise, you need a VPN.

Services with WS-Security

If the external system invokes the SOA layer using a public channel such as the internet, otherwise, you need a VPN.


If the external system invokes the OData layer using a public channel such as the internet, otherwise, you need a VPN.

Web parts


Applicable if you are using SAML 2.0 as your authentication type

Any portal



Autotesting tool







Exporting Bex

Other options

CSS or JS overrides