Bizagi version 11.2.3

Released on 09/17/19

In this release

New features, improvements and fixes

New features
Studio Collaboration Services

Bizagi’s new cloud service completes the cloud journey, you can now model, build and run on the Cloud. Studio Collaboration Services enables multiple developers, throughout the world to contribute 24/7 to a Studio project. You can focus just on the development of the application, while Bizagi takes care of all the underlying infrastructure, saving the entire automation definition in our secure cloud.
When using Studio Services, developers just need Bizagi Studio installed (or via Pen Drive). We eliminate the need to create and manage your own infrastructure by saving your automated projects directly in the cloud. Studio installer has been revamped to provide the best user experience and enable access to projects located on our secure cloud or on premises as well.


OData query services

Our OData layer now has two brand-new endpoints that let you query your Bizagi’s Master Entities. These queries can obtain information on all your cases and third-party reporting tools, such as Tableau and Power BI, can use this data to monitor your business.

  • OData/query/entity: This endpoint shows all the entities you can query.
  • OData/query/executeEntityQuery: This endpoint executes a query for a specific entity.


Multiple authentication

Bizagi now features a new Authentication method which enables to configure two or more authentication types and domains. The method used at runtime is instantiated according to the domain selected when the end user enters to the Work Portal.

Forms authentication

Bizagi now supports forms authentication, which can authenticate a user against an identity provider by a cookie present in a form. Therefore, with this feature, when an external application generates an authentication cookie based on Forms Authentication, Bizagi can log in without the need to request credentials.

SCIM for user synchronization

Bizagi now exposes new RESTfull services for user synchronization. These services rely on the System for Cross-domain Identity Management standard (SCIM), which several Identity Providers like Azure AD use. You can perform CRUD operations through these services, enhancing user synchronization in On-premises and cloud-based projects.

User permission report

The user permission report generates an Excel file containing the information of all the users in the project and their access rights for the entire Work Portal. With the produced file, auditors can filter, sort or search, to comply with their needs of information regarding permission rights.

Technical API for CHelper available

We have created the CHelper API that can be consumed like other known technical APIs. The API documentation will help understand the methods available, and how they are used when automating processes.
Other methods, like Me will be included shortly.

Push notifications

Push notifications let you keep informed when you have been assigned to a task by displaying a message in your mobile device. By demand, you can enable them in your Bizagi Project.

Tableau Connector

Bizagi has a brand-new integration with Tableau. This new Web Data Connector lets you acquire data from Bizagi directly from Tableau. Use this new integration to generate reports and analytics that expand the understanding of your business.


Power BI Connector

Bizagi has a brand-new integration with Power BI. This new Data extension lets you acquire data from Bizagi directly from Power BI. Use this new integration to generate reports and analytics that expand the understanding of your business.


SharePoint connector

Our new SharePoint connector lets you manage your SharePoint files and folders directly from Bizagi. Download it from our Bizagi Xchange and add it to your processes in Studio.



In version 11.2.3 the feature for Activating /deactivating encryption in an existing attribute is temporarily disabled in Bizagi Studio, and it applies for both on-premises and SCS projects. This consideration also applies for deployment, meaning that you cannot change an encryption configuration, and deploy using Bizagi Automation Services or Server. The restriction applies only when you change the property. If you update a project from a previous version to version 11.2.3, the encryption configuration remains the same. Our development team is working to get this option available soon.

Windows authentication for data virtualization and replication

When using data replication or virtualization, in an SQL database, you can now use Windows authentication to grant access to your external database. With this method you can use your Windows account to manage all your resources.

Copy from selecting the preferred form version

Now, from the advanced tab of the Copy from button, it is possible to select the form version which you want to copy the information from. This applies for entity forms.


On-premises SharePoint Web parts improved

Bizagi Web parts have been improved to enable authentication with SAML 2.0. The configuration has been simplified and has been enhanced, avoiding authentication in configuration time.

Delete attributes from Live Processes

There is a new option for Live Processes in Draft, to safely delete attributes that have no dependencies. If an attribute has a dependency you will be notified so you can remove said dependency.

Improved usability of case users

Now the case owner is separated from the other allocated users. Additionally, the details window shows all the pending activities the selected user has for the case.

Cancelled cases notifications

Bizagi will now send a single cancel notification of a case, when users have multiple activities in it. You can set up the cancel case notification to include the list of all the user’s allocated tasks. You can also set it to include the allocated events.

New Admin menu categories

Our Work portal now sorts all our administration options in four new categories: Customization, Process Management, Security, and User management. With them, you can now quickly locate the option you’re looking for in our Admin menu.

Hot deployment

Bizagi Automation Service activates automatically the maintenance window depending on the content of the BEX file. If there are no changes related to entities, attributes, relationships, component libraries, environment options, or the business configuration in the deployment package, you can now deploy without affecting the current session and execution of the Work Portal. Therefore, all the components like the Scheduler or the Work Portal in the target environment remain unaffected, so users can continue working on that environment without shutting down the application to open a maintenance window. Bizagi Automation Service analyses the BEX file, and if needed, activates the maintenance window automatically. So, users do not have to open a maintenance window in every deployment.

RPA improvements

We improved the following for RPA:

  • Fire and Forget – Bizagi now offers a property in the configuration of RPA bots, that lets Bizagi fire a Bot, but forget about the result of its execution.
  • Error Handling: You can now attach an Error Event to your Bot Task to handle errors and exceptions.
    Monitor bots from the Management Console: You can now monitor your Automation Anywhere and UiPath asynchronous tasks from the Management Console Jobs.
  • UiPath add work items: UiPath now can add workitems to a queue without selecting a process.
  • UiPath queue system parameters: When you use a UiPath queue, you now can set some properties of your queue item like the priority or reference. Likewise, you can retrieve additional information of the processed queue item, like the robot that executed the transaction item and in the machine that hosts the robot.
Other improvements
  • We have changed the height of combos to 310 px to allow displaying more elements. If the control contains less elements, it will adjust the size.
  • Now, you can edit table rows by double clicking them. Up to now, you had to select the pencil button to edit it.
  • Performance improvements when exporting query forms to excel.
  • Our package visualizer has been improved to enhance your user experience.
  • Disabled users are now ignored during task reassignment.
  • Timeline is now available for Live Processes.
  • You can now create users in the Work Portal with LDAP authentication.
  • Now, when you invoke QueryCase web method, the parameters guidApplication and idEnt are mandatory to avoid errors when having multiple applications in your project.
  • Issues regarding assignation to everyone have been solved, now the ownership of the case is taken by the assigned user while in the inbox of other users involved the case no longer appears as unassigned.
  • Within the Actions & Validations module in Studio, the container height calculation of the list of values for a parameter entity is fixed.
  • When standard connector is configured with “continue on error and map error response” under Actions output Mapping window, the Work Portal showed an exception.
  • In a form with multiple tabs, when dragging a field into the second or third tab, the field remained in the first tab. A Tab Item was created but now is fixed and the Tabs can be modeled correctly in the Forms Editor.
  • The Entities search is adjusted to use the Name and not the DisplayName in the filters.
  • The massive deletion is adjusted to include the roles deletion of the Deleted Users, i.e. USERROLE table.
  • The “Import/Export” option is now enabled in the mapping for SOAP 1.1 interfaces.
  • In Parameter Entities filters for message templates, all the characters are now supported except for the single quotes ”.
  • The “values violating non-null unique or foreign key constraints” error on Data Sync is solved. This error appeared when trying to export deleted parameter values.
  • In the Forms Editor, the nested forms could not be changed because the Edit button was not being displayed.
  • It was not possible to see the Entity action ‘ADD’ in the Entity log.
  • The Data Model XPath selector was generating a wrong XPath on the process attributes. This is fixed for the XPath used on Process Forms and Expressions.
  • It is now possible to have independent forms to edit/add information and visualize Entities.
  • The “Release/Take Ownership” button continued visible although the functionality is disabled.
  • The method that queries the processes to be shown in the Reports-Analytics section were applying the filter in a wrong way. An adjustment is done to the query, so it does not filter by process type and, then, all the processes types are shown without any issue.
  • Adjustments were done to allow duplicating forms without inconsistencies regarding References, Resources and FormClass.
Version Updates