For further information see our eLearning videos here.
Studio Collaboration Services
Bizagi’s new cloud service completes the cloud journey, you can now model, build and run on the Cloud. Studio 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.
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.
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.
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.
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.
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.
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.
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.
Import BEX files in the Management Console Web (AS Enterprise users)
The Import process button where you import a bex file is not available in the Run portal any more. Now deployments are executed from the Management Console Web.
Improvements in Management Console Web (AS Enterprise users)
Bizagi Management console web now features the following options:
Delete cases: deletes all existing cases and the data stored in the master entities in the current environment. This feature applies for Test environments.
Web administrator password: changes the Admon user password. This feature applies for Test environments.
Working Time Schema: edit the work schedule for each user.
User groups: Use the Management Console Web create groups, and to include or exclude users to them.
Security CORS: define the domains that can interact with Bizagi. If you haven't defined a domain, all the domains are enabled.
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.
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.
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.
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.