The following list includes improvements or fixes that enhance existing features and procedures.
If you are upgrading to version 11.2.4 using Web apps (and not Virtual machines) take into consideration the following topics:
Our Enterprise administrators now have a new portal, called Customer Portal, specially designed as the place where subscription managers can administer the users of all the Bizagi cloud products in a centralized manner.
Automation Service and Studio Collaboration Services, customers have a centralized summary of all project and environments. In it, customers can review the number of provisioned environments, the category of each environment, and the Bizagi version installed. Additionally, they can manage administrators of each subscription’s projects.
For information in Automation Service refer to: https://help.bizagi.com/automation-service/en/bizagi-customer-portal.htm
For information in Studio Collaboration Services refer to: https://help.bizagi.com/bpm-suite/en/bizagi-customer-portal.htm
We have upgraded our authentication platform introducing new technology and making it more robust. This upgrade centralizes the login of all cloud services through our Accounts platform. All services are authenticated relying on the same Identity Provider.
From 11.2.4 you can define an external Identity Provider to be integrated with Accounts 2.0. This let you define one SSO for your cloud-based services portals: SCS, MCW, Customer Portal.
Note: The Work Portals of your Automation Service environments are not authenticated with accounts 2.0. This change will not affect Automation Service’s Work Portal.
We have temporarily disabled the support for Okta as identity provider for the Management Console. If your Management Console relies in said provider, you can change the provider for the upgrade, or upgrade in the next release where Okta will be supported.
We have deprecated the autologin option for Management Console as this option was not recommended.
Note: This change will not affect Automation Service’s Work Portal, which supports Okta with SAML.
If you are using SSO with Azure or ADFS, with the upgrade to version 11.2.4 your IT team needs to perform adjustments in your Identity Provider:
After the adjustment has been made, the configured URL needs to be delivered to the Cloud Operations team via support ticket.
Below you will find the steps to configure authentication to the new platform. Steps are the same for all products, as these are performed just once and they apply for all your cloud products:
Azure AD
ADFS
Business Insights for third party tools, offered for Automation Service customers, features two new and independent services.
The first service is Bizagi Datasets, which lets you expose and store your processes’ information using cloud datasets, to create and consume contextualized and denormalized business data. This service helps you make smarter business decisions by monitoring your business using external reporting tools such as Tableau, PowerBI, SQL Server reporting services and more.
The second service is an ODS that creates replica of the Production database with read-only capabilities for customized reporting purposes. This service allows customers to report their queries directly to it, without affecting their Production processes in the main transactional database.
Bizagi Artificial Intelligence is a new application that lets you execute powerful machine learning algorithms directly in your Bizagi processes. You can implement a predictive analysis based on the reliable data provided by your Business Insights (dataset).
Bizagi Studio and Automation Server are FIPS-140 compliant.
In version 11.2.4 Automation Service customers have a new web-based management console, that replaces the traditional console accessed via virtual machines.
This web-based console enhances the user experience bringing:
Our new RPA Dashboard for the Management Console Web provides charts that monitor the execution of your jobs and queue items. Get information about your Orchestrator operation and how it is improving. Know whether your RPA jobs were successful or not. You can now monitor your UiPath processes and get a sense of the quality of your robots.
In our Bizagi Xchange, you can now find the new RPA Life Cycle Management process, for UiPath. You can use this brand-new process to ease your RPA development or transition. Control your improvement cycles, report bugs, and update your Orchestrator directly from Bizagi. Additionally, you can keep track of all your machines, environments, assets, queues, and processes involved in your RPA expansion.
In our Bizagi Xchange, you can now find the improved Dynamics 365 connector that allows a deeper integration between your Bizagi processes and your Microsoft CRM. Manage all your accounts, contacts, leads, opportunities, and competitors with this new connector.
Bizagi is now RAML compatible. RAML is a modelling language for API managers, where you can define the lifecycle of all your APIs. This compatibility opens integration with MuleSoft or any RAML compatible technology.
Now you can grant or deny access to the Users Authorization Report from the Authorization options in the Security module of the Management Console.
Now you can activate a switch in the Package Visualizer. This feature compares the generated package against the development environment and displays the objects that are not included in a BEX file.
.png)
Now, there is a new check-box available on Bizagi Studio’s advanced Business options. When enabled, users who match allocation preconditions (on the assignation method everyone) and take the ownership of an activity on their Work Portal, visualize the release button. When selected, the activity becomes unassigned and available for all users matching the allocation preconditions.
We added a new category to the filters for the microdeployment. You can now choose to add global objects such as application forms, entity forms and global forms to your microdeployment.
Now, on the advanced Bizagi Environment options there is a new check-box: Include events on notifications. When enabled, each time a case is cancelled, users allocated to events are notified. Before this release, only task assignees were notified.
Now, when working with Actions and Validations over grouping controls such as reusable forms or groups, it is possible to respect each control’s original editability setting, by selecting a new option: Default. Until now, when editability was set on true, all controls were set to editable even if their individual-control original setting was read-only.
Three new functions have been included in the function editor and the IntelliSense:
CHelper.GetCaseAccessUsers(idCase): Returns the list of users who have access to a case.CHelper.ClearCaseAccess(idCase): Removes the visibility of all users associated with this case, returns true if it works correctly and false if it fails. CHelper.ClearCaseAccess(idCases[]): Removes the visibility of all users associated with the cases in the list.The run portal now features two new options for restarting the Bizagi Server. The Partial restart cleans the global cache and temporary files and the Full restart performs the same operations plus cleaning form’s cache.
When you create users from the Work Portal administration option, the username, domain and email, have regular expressions that validate that the field does not have unsupported characters.
Automation Anywhere lets the robots return outputs using a new functionality called callbacks. Bizagi now can interact with this new type of robots along with all your queues in your control room.
The out-of-the-box SAP connector now can be used in our cloud-based services including Studio Collaboration Service enterprise subscription, and Automation Service.
When configuring virtualization or replication, Bizagi validates the external database with additional validations. For example, avoiding reserved words, making sure that keys are configured, and making sure that the table exists in the external system. Therefore, the configuration becomes ore reliable for execution.
Now the User permission report includes user information. You also can choose if the report shows the disabled users. The authorization for this report is now handled independently from user management authorization.
It is mandatory to set a value in the field Condition rule. Now, when creating a trigger, the application throws an alert message if the Condition rule field has no option selected. Until now, it was not mandatory.
Now, when you close the expression editor, the expression validation runs automatically, letting you know if there are any issues in the entered code. Before this version, the validation was done on demand, when the Validate button was clicked.
Now, our native Excel connector can filter ranges. You can import a filtered range to a collection in Bizagi and use Excel filtering capabilities to reduce the amount of data that is sent and processed in Bizagi.
According to the BPMN 2.0 regarding link events, the following error validation messages have been added:
CHelper.RevokeCaseAccessToUsers and CHelper.GrantCaseAccessToUsers have been improved to get a better performance when invoking them.Due to security improvements, some widget versions are no longer compatible with Bizagi 11.2.4. If you are using any of these widgets, make sure you install and deploy the following version:
