Creating a new case in Bizagi means creating a new instance of a specific process. By default, the number of the case/instance, also known as the CASE NUMBER, is maintained by the application using an internal sequence. Having this in place avoids any duplicity or any kind of errors.
During the development phase of the project, and sometimes in the Production environment, you find yourself in a situation when errors need to be traced. Or as I call it, you need to debug the application.
In Bizagi, the easiest way to debug is to use the Trace functionality. Now, this is a simple CHelper method where you have to pass 2 arguments:
CHelper.trace(string sFileName, string sText)
…where the sFileName is the name of the .txt file where the traces will be stored and the sText is the information to trace. It can be an attribute selected by a navigational XPath expression, a function, or a variable.
Create New Business Intelligence Project
Open SQL Server Data Tools and create a new Business Intelligence Project. Navigate to File > New > Project and select Integration Services Project from Template > Business Intelligence > Integration Service. Name the project ExportCSV and choose the location where to save it.
Sometimes while working with databases, it is necessary to import or export large amounts of data.
Those operations are called Bulk Import/Export operations and are an efficient way to copy data between a SQL Server and a data file.
Export large amount of data to CSV
This article explains how to export large amounts of data from one table to a CSV file using MsSQL Server Export Wizard.
Have you ever wonder what is the proper way to cancel a case in Bizagi? When I first started working as a technical BPM consultant, I’ve learned to cancel the case using the following workflow pattern:
At the beginning of the process, you add a parallel gateway. One path takes the normal flow, while the other one goes into this cancel logic: an Intermediate event followed by a Terminate event.