New features
- Deploy to Bizagi Cloud
-
New possibility which allows you to create deployment packages (.bex files) to be applied directly into Bizagi Cloud environments.
http://help.bizagi.com/cloud/en/exporting_an_app.htm - Oracle 12c support
- Build your processes while using an Oracle 12c database.
- SQL 2016 support
- Build your processes while using an SQL Server 2016 Microsoft database.
- SharePoint Online support
- Bizagi now supports SharePoint Online for Bizagi Web parts
Improvements
- New option in the One-click Deployment, which allows you to apply into the test environment those system parameters’ values as used in production (ignoring the definitions incoming from the development environment).
- New functions in the rules API (CHelper class) that promote best practices: getUsersForPosition, getUsersForRole, and getUsersForSkill work by using the name of the record to find, instead of an ID (those using ID become deprecated).
- General improvements for: the theme builder, email integration, Studio security, document templates, SharePoint web parts, federated authentication.
- Autotesting tool available and supporting the execution scenarios for processes using a broader set of BPMN elements (such as timers).
- The rules engine now smartly analyzes variants of Me.Context expressions to automatically identify references accurately.
Fixed
-
- Multiple adjustments on Experience design actions and its action launcher control, including handling scenarios with images and sub-processes.
- Query forms which contained a suggest control were having problems in execution.
- Shortcuts for saved Query forms were not being properly displayed.
- Certain special characters inputted in controls were not allowing Query forms to save changes.
- Case number and case link information were not being displayed in emails (CaseNumber and CaseLink respectively).
- Files uploaded within UI tables were not being sent in emails.
- Multiple adjustments for tables in emails (both for static and dynamic tables).
- Global forms were not being displayed while reviewing closed cases.
- The Entities admin option was shown with empty information whenever access was not granted (now resolved so that it isn’t available).
- Events were not displaying the UI when clicking on them.
Restrictions
- In the current version the following features are temporarily not available. We are working hard to get them up and running so you can try out and test our full functionality soon
-
- JEE version
Older versions
Version 11
Release date:August 29, 2016
New features
- Personalize your end user’s experience, making it unique for each end user
-
Bizagi lets you create a unique experience for each and every one of your end users. Bizagi adapts their Work Portal by understanding who they are, what they want and what they need.
The Work Portal has a new menu called Me, that dynamically adjusts to any change in each individual’s situation, presenting all the options and features that make sense to their particular circumstances.
http://help.bizagi.com/bpmsuite/en/Experience_design.htm - Stakeholders
-
Create Stakeholders to represent groups of end users in your application and make available similar capabilities to interact with the Work Portal, enabling deep personalization in their overall experience (i.e. Doctor, Patient, Teacher, Student, Credit Analyst, Customer).
Enabling a user as a Stakeholder brings a host of benefits. Stakeholders are decision makers that can launch processes, update data records (without being involved in any process) and link process together to create powerful cases. They can also view, order, sort and navigate data that belongs to them (i.e. their credit cards, their appointments, their cars, their tickets).
http://help.bizagi.com/bpmsuite/en/Studio_Stakeholders.htm - Actions
-
Actions enable Stakeholders to achieve an objective that he/she consciously wills, via a button. Actions can launch processes, update data records with the click of a button (independent of the processes it is related to), create new records of an entity (also being independent of a process) and link process together to create powerful cases.
Actions can be launched to affect or create an individual data records of your project, or multiple records at the same time.
For example, we can create Actions to book a hotel, update customer record or approve multiple requests at the same time.
http://help.bizagi.com/bpmsuite/en/Studio_ContextActions.htm - Search
-
Find the data you need. This version offers powerful search capabilities for Stakeholders to view and manage business data, independent of the processes it is related to.
The resulting list of data records will present the Actions defined in the authoring environment. For example, if a Patient is looking for General Doctors, the result set will contain, for each doctor, buttons that enable scheduling an appointment or viewing all their information.
http://help.bizagi.com/bpmsuite/en/Studio_SearchData.htm - My Stuff
-
Enable knowledge workers to view, sort, navigate and manage data that belongs to them via a new section in the Work Portal called My Stuff (i.e. their credit cards, their appointments, their cars, their tickets).
Each set of data is presented as a list where existing records can be navigated, filtered and sorted. Each record will present the Actions defined in the authoring environment.
For example, a Customer can access and view the cars he/she has purchased. When navigating the set of his/her cars, each car will display buttons that enable sending it to maintenance or selling it.
http://help.bizagi.com/bpmsuite/en/Studio_MyStuff.htm - Contexts
-
In the digital world Context is key. Bizagi 11 is context-aware and intelligently presents only the options and information that make sense in a particular situation. This empowers knowledge workers to make informed decisions, such as when to start a process or update data, boosting agility and productivity.
Create contexts within Stakeholders to define which actions, information and searches are shown in a particular state or situation. You need to define a condition for each Context. When met, the system shows the defined actions, information and searches within it.
For example, a context is created to display, for a pregnant Patient all her Ultrasounds and an Action to schedule a pregnancy check-up. Thus, if a male patient is logged in these options will not be displayed.
http://help.bizagi.com/bpmsuite/en/Studio_Contexts.htm - Templates
-
Different knowledge workers use data in different ways. Bizagi 11 lets you create several Templates for each data object, so you can define the visual appearance and the information to be displayed for each type of user.
For example, you can define two different Templates for the Appointment entity, in a Medical solution. Appointments for Doctors would display the Patient and time. Appointments for Patients would show the treating Doctor, the time and a location.
If you don't specify a data template, Bizagi creates a default template that includes some attributes of the entity.
http://help.bizagi.com/bpmsuite/en/Studio_DataTemplate.htm - Plans
-
Not all processes can be planned ahead of time - they arise from new circumstances. But once they have arisen, they should be managed. Think of a meeting and all the series of activities that are left to be done. Bizagi introduces a wonderful capability that allow to create a Plan to control a series of activities from your Work Portal.
With Plans you decide the activities that need to be done, the order in which they are executed (sequential or in parallel), establish due dates and the responsible person for each of them.
Users who have been allocated to Plan activities, can in turn create additional Plans for themselves.
http://help.bizagi.com/bpmsuite/en/My-Plans.htm - Automatic data injection
-
Avoid creating business rules to inject information to new cases or forms. Bizagi now injects data for you, understanding who the Stakeholder logged in is, and the data that is involved.
http://help.bizagi.com/bpmsuite/en/Studio_ContextActions.htm#MappingfeaturesandHints - Relevant to me
-
Enable Stakeholders to launch their most used processes with just one click. A new section called Relevant presents a list of the most used processes, and with just one click starts a new case instance, injecting the information of the Stakeholder.
http://help.bizagi.com/bpmsuite/en/Studio_RelevantActions.htm - Triggers
-
Triggers are automatic actions that react to any change in data and run immediately after that, when a condition is met. For example, a trigger can be used to upgrade a Customer to VIP when his/her purchases exceed certain limit. There are two types of triggers to choose from: launch a process or execute a Rule.
http://help.bizagi.com/bpmsuite/en/Studio_Triggers.htm - Start form
-
Use Start forms to launch a new case instance temporarily, and allow end users to confirm the process creation when they are certain of this action, or closing the form without confirming to avoid unnecessary case creation.
http://help.bizagi.com/bpmsuite/en/Start_Form.htm - Conditional task
-
The Conditional task is a Bizagi extension of BPM 2.0 standard. When used in a process, this task is enabled or disabled during the course of a case instance depending upon a business condition. It represents a user task, that is, when enabled the task is allocated to an end user.
For example, imagine an Emergency Room. A Patient arrives and a triage is performed. Then, a doctor examines the patient and usually some exams are ordered. Only when all the exams are taken and a result for all of them is received, should the Review exams activity be enabled. Thus, the Review exams task is represented using a Conditional Task. This way, when Bizagi evaluates the condition that that all ordered exams are ready, will a doctor call-in a Patient to review them.
In Bizagi Studio, the authoring environment, a condition must be set to the Conditional Task to enable or disable it, according to the business conditions.
In Runtime, allocated end users will be able to see the task in their pending lists when the condition is met. If the condition is not met, is like the task never existed.
http://help.bizagi.com/bpmsuite/en/ConditionalTask.htm - Inheritance
-
This version allows creating entities that inherit attributes and Actions from parent entities. This facilitates reusing the structure of an entity created, to speed up a solutions construction and creating complex Action trees with the new control called Polymorphic launcher.
http://help.bizagi.com/bpmsuite/en/Studio_Inheritance.htm - New Form controls
-
This version comes with three new controls in the Forms designer to enable using the personalization features:
-
Action launcher: this control presents all Actions defined for a specific entity. The control will only display the available Actions for the Stakeholder.
http://help.bizagi.com/bpmsuite/en/Action_Launcher.htm -
Entity Template: this control displays the Template defined for a specific entity, for the Stakeholder.
http://help.bizagi.com/bpmsuite/en/Entity_Template.htm -
Polymorphic launcher: this control displays all Actions according to the inheritance defined for the parent entity, in a tree-like structure.
http://help.bizagi.com/bpmsuite/en/Polymorphic_Launcher.htm
-
Action launcher: this control presents all Actions defined for a specific entity. The control will only display the available Actions for the Stakeholder.
- Connectors
-
Go beyond the integration features provided out-of-the-box, by plugging in ready-to-use connectors or by creating your own ones. Creating new connectors is made easy with the Bizagi Connector Editor, a browser-accessible SDK walking you through the building steps. Connectors are:
- Portable (platform-independent) and highly scalable by relying on Node.js.
- Completely reusable and easy to configure, by making the most of Bizagi graphical mapping features for inputs and outputs.
- Enhanced with built-in tracing to speed up any troubleshooting.
- Multi-versioned, while allowing you to run these versions simultaneously.
http://help.bizagi.com/bpmsuite/en/Connectors_overview.htm - Case folder
-
Bizagi handles a collaborative strategy that attempts to coordinate knowledge workers, information, correspondence and resources to progress a case to achieve a particular goal.
Bizagi v11 presents a Case folder, individual for each case, designed to integrate its discussions, files and the case’s Timeline.- Stakeholders can rely on Discussions to support one another in the resolution of the case.
- Any users interested in the case can add Files to complete the available information.
http://help.bizagi.com/bpmsuite/en/Case_folder.htm - Timeline
-
Present in each case’s Case folder the Timeline links together all processes and activities that have been launched via Actions, by Stakeholders.
The Timeline features a list of all activities executed in the process with the user allocated and the time of resolution, sorted by when they were created. It also contains a Process map to view the connection between processes (i.e. which processes launched which ones) and an Activity map, presenting which Activities where the ones that launched another.
In the main Timeline view each Activity will present two icons containing the graphic view and the Log of the processes that it belongs to.
http://help.bizagi.com/bpmsuite/en/Case_folder.htm#Timeline - Diagnostics
-
Bizagi Diagnostics is a toolkit featured by Bizagi in order to provide monitoring options for Bizagi Engine operations in a test or production environment.
By relying on Bizagi Diagnostics, a system administrator may run health checks on Bizagi Engine components and overall, while identifying issues that are affecting the adequate operations of the Bizagi project (e.g., performance issues, service downtime), in order to analyse and resolve them promptly.
http://help.bizagi.com/bpmsuite/en/SysAdmin_Diagnostics.htm
Improvements
- Improvements in authentication
-
Several improvements were made to the authentication methods. Very important to read:
http://help.bizagi.com/bpmsuite/en/windows_authentication.htm - Simulation in Process Modeler
-
You can now use the Simulation feature that was available in Bizagi Modeler, from within Bizagi Studio.
http://help.bizagi.com/bpmsuite/en/Simulation.htm - User interface
- Enjoy a modern visual experience with our new and enhanced look & feel in Studio and Engine.
Miscellaneous
- 32 bits no longer supported
- Bizagi 11 will be available in a 64 bits edition exclusively.
- OS and DB no longer supported
- Bizagi 11 will no longer support SQL Server 2005, Oracle 10g, Windows Server 2003, Windows XP and Windows Vista.
- V9 Forms
- Upgraded projects will need to migrate all its forms to v10 forms. V9 will no longer be supported. If a project has V9 forms the project will not upgrade.
- Deprecated functions in rules
-
The following functions are deprecated and will not work in Bizagi 11:
- Me.Case.ProcessDefinition.Id
- CHelper.NewCase(Me, IdWFClass)
- CHelper.NewCaseByUser(idUser, IdWFClass)
- CHelper.getSiblingProcessesId(Me, IdWFClass)
- CHelper.getAttrib(idEntity, oEntityKey, sAttribName)
- CHelper.getEntityAttrib("Entity","ValueToReturn","filter","")
- CHelper.setAttrib(idEntity, oEntityKey, sAttribName, oAttribValue)
- CHelper.GetNextSeqValueInt(idSeq);
We must use the name of the parameter, instead of the ID. The following functions are the ones that must be used:- Me.Case.ProcessDefinition.Name(WFClassName)
- CHelper.NewCase(Me, WFClassName)
- CHelper.NewCaseByUser(idUser, WFClassName)
- CHelper.getSiblingProcessesId(Me, WFClassName)
- CHelper.getAttrib(sEntityName, oEntityKey, sAttribName)
- CHelper.setAttrib(sEntityName, oEntityKey, sAttribName, oAttribValue)
- CHelper.GetNextSeqValueStr(seqName)
- CEntityManager.GetEntity(EntName)
Older versions
Version 10.6.1
Release date:January 19, 2015
New features
- SAP out-of-the-box connector
-
Integrate your processes with your SAP system, in an agile and zero-programming approach.
Through our SAP Connector you can:- Invoke any RFC function in SAP (typically BAPs), either though the user interface (i.e. when clicking a button) or as an asynchronous integration (and enable automatic retries).
- Rely on the graphical mapping features to configure both the inputs and outputs of your SAP BAPIs.
- Configure a special routing for any of the predefined SAP exceptions handled by your BAPIs.
- Rely on an RFC connection to benefit from a secure connection and enhanced performance.
http://help.bizagi.com/bpmsuite/en/index.html?SAP_connector.htm.
Improvements
- Oracle number data type support
-
Bizagi now presents an additional attribute, designed to support really large numbers (those holding more than 19 digits).
This attribute is called Oracle number (supported only for Oracle databases), and it is also supported for Data Virtualization or Data Replication.
Through Data Virtualization / Data Replication, columns in Oracle’s tables that are defined either as NUMBER, or NUMBER (38) are handled by this new data type. - Management forms for Parameter entities and Query forms now supported in the new Forms designer
-
Up to version 10.5,Query Forms and Management Forms for Parameter entities were created in Bizagi’s traditional design environment. From version 10.6.1 all new Query Forms and Management Forms for Parameter entities are now created using our new Forms Designer to deliver a powerful and appealing UI for human Activities, which include: a friendly layout distribution and improved actions and validations.
http://help.bizagi.com/bpmsuite/en/index.html?Query_forms.htm - Improvements in Expression Manager
- Bizagi now controls the number of expressions listed in the Expression Manager. This ensures optimal performance of Bizagi Studio even when the number of expressions defined are very large. If the expression you need is not displayed in the list you can use the search field to easily find it.
- Advanced parameters for Web Service invocations
-
It is now possible to configure specific parameters that are useful when sending large volumes of information via Web Services.
By default and according to best practices (both for security and performance), Bizagi limits the size of information that can be sent to external Web Services.
However, in sophisticated scenarios where it is strictly needed to surpass the limit, you may configure the following advanced parameters: Max Buffer Size, Max Buffer Pool Size, Max String Content Length, Max Array Length, Max Bytes Per Read, Max Name Table Char count.
You may configure these directly in Bizagi Studio or manage their values in other environments through the Management Console.
Does not apply for JEE platforms because these parameters are specific to the Windows Communication Foundation specification files (WCF).
http://help.bizagi.com/bpmsuite/en/index.html?Studio_interfaces.htm - Invoke REST services using JSON
-
Now it is possible to send and receive JSON-structured files when invoking a RESTful service.
http://help.bizagi.com/bpmsuite/en/index.html?InvokingREST.htm - Importing Bizagi Modeler processes from any version
- You can now import any process designed in Bizagi Modeler from the latest version without the need to revert to earlier versions.
- Port definition for Web Services
-
Now it is possible to define a specific port of your external Web service, so that Bizagi may invoke any web method from a Web service providing multiple service ports.
http://help.bizagi.com/bpmsuite/en/index.html?interfaces_administration.htm - Option to generate proxy in design time for Web Services
-
By default, Bizagi generates a proxy definition in runtime (a .cs and .dll file when running on a .NET platform) for any external Web service that is integrated in processes.
Through this option you may override this behavior so that the proxy definition is not generated on runtime but taken from the one already interpreted by Bizagi Studio.
This option is really useful when the setup of your Web Services in a production environment has major security constraints (its definition resources, such as the WSDL or any imported schemas, are strongly restricted and not easily accessed in the runtime).
Please note that this facility does not apply for JEE platforms as the proxy definition interpreted by Bizagi Studio is done by the .NET framework, and this same technology is not compatible nor used in a JEE-based runtime. - Languages selection has been moved to Business Configuration
- Enabling and disabling languages to localize a project is now done through the Language menu found under Business Configuration. Languages are now next to the Localization menu to make it easier to configure the project’s display options.
Bug fixes
- Form´s search has been re-enabled in Bizagi Studio.
- The execution time of dependencies analysis performed when changing the type of an attribute has been reduced.
- Some validations have been introduced when creating attributes and collections in order to ensure compatibility between the different platforms and databases.
- A rich text editor has been included for Help texts of controls.
- A change was introduced to enable setting privileges over graphical queries.
- Errors when using the intellisense feature has been fixed for specific Bizagi functions.
- Creating roles, areas or positions from the Modules view was not possible in Oracle based projects. This has been fixed.
- Under certain scenarios, an unhandled error was display when trying to define an entity as a process entity. This has been fixed.
- When changing the authentication type from Bizagi to Windows or LDAP, the quick login option remained enabled. This has been fixed.
- Some unexpected behaviors related to convert Search controls into Suggest controls have been fixed.
- An unhandled error displayed during the dependencies analysis of virtualization providers has been fixed.
- An error that triggered wrong warnings in dependencies analysis from expressions has been fixed.
- An unexpected behavior when trying to configure the security options for Query Forms has been fixed.
- An unhandled error displayed when creating user properties has been fixed.
- Under certain conditions, an error was displayed when trying to change the case number generation mode from the default to generation using rules. This has been fixed.
- Incorrect analysis of the attributes that compose the collection´s filters within an expression caused an error in the deployment process. This has been fixed.
Older versions
Version 10.7
Release date:November 24, 2015
New features
- Email integration
-
Users are be able to approve/reject requests from an email in Outlook or their mail client of choice. Users receive an email with a pre-configured template created in Bizagi Studio. Users can take action from the email and click on any of the buttons included in the email. Bizagi will then process and complete the task, moving the process forward.
http://help.bizagi.com/bpmsuite/en/index.html?Customizing_a_form_to_be_advan.htm - Mobile app redesign
- Be even more productive on the go with the all-new version of our mobile app. With a great modern look we’re confident you’ll find our re-engineered mobile app even easier and more enjoyable to use.
- Automatic testing
-
Resource kit designed to test Bizagi processes automatically in Development and Testing environments. The Automatic (Auto) Testing tool executes without human intervention any previously recorded scenarios. It validates that the outcome of those scenarios and the process flow/path followed are correct. This greatly reduces the time and resources required to validate that processes are performing well after changes/enhancements have been introduced. This otherwise manual activity is very time consuming in BPM projects.
http://help.bizagi.com/bpmsuite/en/automatic_testing.htm - Search List control
-
The Search List control enables you to select multiple items from a list and relate them together. Want to assign job roles or tasks to multiple locations? Simply tap in the name of the record and Bizagi displays a list of matches.
For example, choose several European countries to visit for your next trip, without using a table. The Search list control displays ALL records for European countries, enabling you to select one or more and associate them to the Countries to visit attribute.
The Search list works similarly to a Suggest control: it displays a text box where the end user types the name of the record to relate and Bizagi displays a list of matches
http://help.bizagi.com/bpmsuite/en/index.html?search_list.htm - Register to Bizagi Community window
-
Frequent Bizagi Studio users will be prompted to join Bizagi Community and Sign in within the product. Once registered, you can enjoy all our free resources such as online forums, e-learning, process templates and interaction with 300,000 members worldwide ensuring that you’ll never be short of advice and ideas.
http://help.bizagi.com/bpmsuite/en/index.html?register.htm
Improvements
- Actions involving collection elements and controls outside the collection
-
You can now create Actions and Validations that include elements (columns) of a table and elements outside of the collection. This was not possible before. Previously, if an Action involved an element of a collection, only elements within the table were available.
http://help.bizagi.com/bpmsuite/en/index.html?performing_actions_on_collecti.htm - Action column in tables
-
Bizagi presents an additional property in the Tables’ configuration that enables a new column containing the actions - Edit, Delete and/or View for each record of the table. This column allows users to manage records with just one click.
http://help.bizagi.com/bpmsuite/en/index.html?table.htm - Filter tables using Expressions
-
You can now use Expressions to filter records within a table. This improvement permits creating complex filters according to your Business needs.
http://help.bizagi.com/bpmsuite/en/index.html?filter_with_expressions.htm - Exclusive checkboxes in Tables
-
You can now set a column of a table containing checkboxes to automatically control the selection of single records. If one checkbox is selected and the user clicks on another one, the previous one will be automatically unselected.
http://help.bizagi.com/bpmsuite/en/index.html?yes_no.htm - Editing button positions in Tables
-
Bizagi now lets you define whether to locate the Editing buttons at the top or the bottom of the table.
http://help.bizagi.com/bpmsuite/en/index.html?table.htm - Collapse/Expand tables
-
You can now collapse or expand Tables, in the same way as Group containers, to improve the look of your forms, especially for long tables. Tables can be presented as expanded or collapsed as soon as the activity is opened in the Work Portal.
http://help.bizagi.com/bpmsuite/en/index.html?table.htm - Open Links in new tab or window
- You can now define how to open Link controls in a new tab or in a new window. Configuration is performed for each Link in Bizagi Studio’s Form Designer.
- Percentage and thousands separator
-
You can now configure a specific format for number-type attributes to add the percentage symbol or to show the value using a thousand separator.
http://help.bizagi.com/bpmsuite/en/index.html?number.htm - Clean data for all render controls
-
The action Clean data for in Actions and Validations is now extended for all controls. This Action was exclusive for Combo controls in previous versions. Now you can set an empty value in any control in a Form.
http://help.bizagi.com/bpmsuite/en/other_actions.htm#clearthedataforacontrol - Fixed label width in pixels
-
You can now set a fixed value in Pixels, using the Forms designer, for Label widths. This way Labels are not automatically resized when the Work Portal’s browser window changes size.
http://help.bizagi.com/bpmsuite/en/index.html?controls_properties.htm - Independent format for Label and Value
-
You can set an independent format for both Label and Value of a control in order to customize the look and feel of your controls within your Forms.
http://help.bizagi.com/bpmsuite/en/index.html?controls_properties.htm - Date control improvement
-
Improved look and feel makes Date control easier to identify in Bizagi Studio.
http://help.bizagi.com/bpmsuite/en/index.html?date.htm - Show the complete name on expressions
- When you are using Expressions in the Forms Designer, for either Default Values, Filters, Maximum or Minimum Values, etc. the complete name of your Expressions can be fully displayed by hovering over the Expression box.
- Set the maximum number of lines for an Expanded Text Control
-
You can define the number of lines to be displayed in an Expanded Text control. This determines the height of the control displayed in the Work Portal. It is very useful for Extended Texts in tables.
http://help.bizagi.com/bpmsuite/en/index.html?text_box.htm - Visibility Rules for panels
-
Now, you can create Visibility rules to determine whether a Panel is visible or not in the Work Portal.
http://help.bizagi.com/bpmsuite/en/index.html?containers.htm - Rules On enter and On exit of Form links
-
Now, you can define the execution of a rule to be executed as soon as a Form link is opened, and as it is Saved, to perform calculations and validations.
http://help.bizagi.com/bpmsuite/en/index.html?form_link.htm - Column Form link ensures optimal window size
-
There is a new property that determines whether a Column Form Link is opened in a full window, or a small window.
http://help.bizagi.com/bpmsuite/en/index.html?form_link.htm - Form buttons improvement
-
You can now define Actions and Validations over Form buttons in order to change their forecolor, background, editability or to perform a click over any of them.
http://help.bizagi.com/bpmsuite/en/other_actions.htm#performactionsoverformbuttons - Additional options for Actions and Validations
-
Bizagi has increased the number of options to be performed over actions and/or validations. New options let you change the order of the execution list, enable or disable a specific action or validation, and disable or enable all the actions or validations.
http://help.bizagi.com/bpmsuite/en/index.html?perform_actions_over_controls.htm - Label and Column Label control improvements
-
You can now set a dynamic value for labels either by resolving the XPath of an existing attribute and a filter, or by assigning the result of an expression.
http://help.bizagi.com/bpmsuite/en/index.html?label.htm - Perform actions to set a value to a control outside of a table
-
Bizagi now lets you use Actions to define changes over controls outside of a table when a control in a column changes. This allows users to execute the desired actions without refreshing the entire form. Only the controls specified will be updated.
http://help.bizagi.com/bpmsuite/en/performing_actions_on_collecti.htm#usingactionstosetavaluetoacontroloutsideofatable - Forms Modeler Performance Improved
- Bizagi has improved the performance of the process whereby the final user creates, updates, deletes or moves a control in Forms Modeler.
- LDAP Import configuration for each environment
-
Importing users from the LDAP server can be now configured separately for each environment, meaning you can use a sandbox configuration in the development environment that differs from the one used by your production environment.
http://help.bizagi.com/bpmsuite/en/index.html?importing_users.htm
Bug fixes
- When using SOA’s Abort cases, all cases with the same case number, or radNumber (i.e. Processes and sub-processes), will now be aborted at the same time.
- An error was preventing the execution of ReType in a table with inline editing.
- An error related to QueryForms using controls with range parameter (since-to) has been corrected.
- Whilst editing Document Templates, an issue was causing some defined templates to be deleted.
- QueryForms was not listing the processes shown in a category.
- An error when a Suggest type render was added to the user preferences form has been fixed.
- A visual problem in the SLA's administration window was preventing save changes in some activities.
- Signoff was not being registered in the authentication's log using windows/mixed authentication.
- The numbers were being sent as strings in the JSON sent to the interfaces.
- The specified format was not being taken into account for the currency render type in QueryForms.
- An error was produced when some metadata had a null value, in the integration of ECM with SharePoint 2013.
- Some fixes have been made to support 'Credential' in the rules (BAS, Portal).
- When using generate a rule copy feature over a Library Rule, input parameters were not being copied.
- Missing in re-implementation of administration of entities. With this fix, only the attributes which are not in the replication are now editable. Besides, for replicated entities the form always auto-replicate.
- When using generate a rule copy feature over a Library Rule, input parameters were not being copied.
- Family and specific rule name are now being shown in errors over library rules are logged.
- When executing CHelper.RaiseErrorIntermediateEvent to advance through an error transition attached to a task, it was working only when said task was in the parent process.
- A Dependencies error in location resources using Chelper.GetStringExtended was fixed.
- "Allow Full Search" is now implemented in Search type renders.
- Editing workflow properties was disabling all versions.
- An issue evaluating some Excel formulas in a Document Template has been fixed.
- Data was being duplicated when exporting process BAM results to Excel.
- An issue applying a numeric format to numbers in Document Templates was fixed.
- The execution of PerformActivity failed when being invoked with the case number.
- The localization of old form renders was not being shown.
- Date-hour editable renders from activities were fixed.
- QueryCaseAsString now receives the searchAllUsers parameter.
- User's circular delegation is validated when users are modified via SOA.
- Radio Button’s default value is now being saved.
- The configuration is now validated for Services’ undefined NameSpaces.
- REST services timeout is now being taken in milliseconds.
- Compiling rules has been fixed for expressions with ‘*’ or ‘/’ within line commentaries.
- Users were being omitted in activity allocation when both their FullNamea were the same.
- The QueryCasesAsString method was filtering with current user if any idQueryForm was specified.
- Table actions were not fully working.
- When updating from 9.1.7 to 10.6.1 an error was being thrown. “Invalid service instance”.
- When editing a name of an Expression, the “Object Reference” error was being thrown.
- Setting “ThrowValidationError” within a rule in a button was not rolling back.
- Time was running out within an activity when creating an HTML for email template.
- An unhandled error in BAS was being thrown when locating a UserProperty.
- JSON interface exceptions with Xpath error handling has been fixed.
- Email validation with some Russian characters was causing some issues.
- Deleting rows of a table was generating problems on its Actions execution.
- Some values of Real control-type were not being rounded correctly.
- An issue when editing attributes of the data model was causing visual bugs.
Older versions
Version 10.5
Release date:August 11, 2014
New features
- New product image
- Enjoy a modern visual experience with our new and enhanced look & feel.
- One single product, no editions
-
With this new release we will offer one single product suite, namely Bizagi BPM Suite, what we currently known as Enterprise Edition. We will no longer offer Xpress edition.
If you are a Xpress user please refer to Edition upgrade from Xpress to Enterprise. - BPM Suite: One platform, three products
-
- Bizagi Modeler: Downloaded and used for free. This is our powerful BPMN modeling environment to design, document, simulate and evolve process maps.
- Bizagi Studio: Downloaded and used for free. Used to transform process maps into real, running applications and workflows. Bizagi Studio presents an integrated runtime environment where you can login to test your automation process. By default IIS is used. JBoss can also be used installing a plug-in.
- Bizagi Engine: Paid for part of the Suite. Used to deploy the application, to Testing or Production environments, on JEE or .NET to fit whatever architecture is in place.
- Encryption of data model attributes
-
Attributes can now be encrypted with one of the following algorithms: Triple DES (1, 2), AES (128, 192, 256), DES.
http://help.bizagi.com/bpmsuite/en/index.html?Encryption.htm - IBM Service Bus integration support
-
Bizagi now supports integration with IBM Service Bus. The integration is based in SOAP Web services exposed by IBM.
http://help.bizagi.com/bpmsuite/en/index.html?Invoking_IBM_ESB.htm - “Copy from” in Expressions
-
Bizagi now provides the “Copy from” feature to speed up the development of expressions.
This functionality allows you to easily and quickly create a new expression by duplicating an existing one. The “Copy From” functionality will insert the code from the original expression (source expression) to the target expression.
http://help.bizagi.com/bpmsuite/en/index.html?Copy_rules.htm
Improvements
- Specify the IIS port for the Work Portal
-
By default Bizagi creates the Web application to display the Work Portal in 8080 port. If a project needs to change the port a new option is available in the Web server configuration, to adjust it to match the default IIS port configured in the Web Server.
http://help.bizagi.com/bpmsuite/en/index.html?Web_Server_configuration.htm - Sysadmin rights in SQL Server account no longer required to work with Bizagi Studio
-
Security policies within companies may restrict the use of the sa login (used by default in Bizagi) or a login account having the sysadmin server role, for SQL Server database configuration.
Furthermore, on cloud database services (i.e Amazon), a login account with such characteristics may even not be available to use.
For the above scenarios, you may now create different SQL Server login accounts for their use in Bizagi Studio’s connection. Through the hierarchical definitions of these SQL Server login accounts, process analysts may use a login that does not involve the sysadmin server role in order to work in a Bizagi project, and a process administrator may use a login with higher rights but which doesn’t involve the sysadmin server role, in order to create, upgrade or deploy a project.
http://help.bizagi.com/bpmsuite/en/index.html?Prerequisites_sqllogins.htm - JEE Console commands improvements
-
2 major improvements were introduced into the JEE Console and its parameters to manage JEE projects:
- The createproject command now uses a standard –f (-file) parameter to specify the path of the file used by this command (the project’s xml configuration file).
- A new command to stop or start the JBoss service, especially useful for the development environment. When you wish to restart JBoss, use: startappserver or stopappserver commands.
Bug fixes
- In previous versions when an attribute had a default value it was not contemplated in the deployment structure. From this version, default values are always updated with every deployment.
- When a Form was checked-out and Bizagi Studio was closed with an opened Form, the check-out remained. This has been fixed, if Bizagi Studio is closed, all forms are checked-in.
- When designing forms, wrong validations related to editable duplicated controls in tables with filters were displayed. This has been fixed.
- When designing forms, wrong validations related to empty Containers were displayed. This has been fixed.
- In previous versions, editing display names of customized columns was not possible when these had already be sent to production environments. This has been fixed.
- An error that inhibited the creation of JEE projects on Oracle has been fixed.
- Errors were displayed when saving or executing expressions that contained XPaths in commented lines. This has been fixed.
- In a specific scenario, an unhandled exception was displayed when creating a dimension in Bizagi Studio. This has been fixed.
- Some problems related to the interfaces mapping wizard have been fixed.
Older versions
Scroll to Top