Navigation: » No topics above this level«
Using Bizagi Studio
Bizagi is a digital business platform which enables customers to develop their own business applications.
Customers are completely in charge of designing how these applications work overall, and this includes how user interfaces are presented, the logic behind, or which information is stored.
All of this is done with Bizagi Studio and by working on a Bizagi Studio project.
Recall that in your Bizagi Studio project, you may include as many processes as needed, and classify them into business applications and categories while having those processes share the same data model.
Opening your project
Once you have accessed Bizagi Studio, click on the listed project which appears under Recent projects:
At this point and when the project finishes loading up, you will be set to start designing your applications.
Setting e-mail notifications
It is important that you explicitly enable and set up the SMTP service you are entitled to, if applicable to your subscription.
In order to do this, note that from the Bizagi Studio you may click on Environment.
Then, ensure you tick the Enable Email checkbox, and input [SENDGRID] for the following SMTP Server field.
Additionally, make sure you define a mailbox address on whose behalf you wish to send out the e-mail notifications at the SMTP Server Account field.
Note that such mailbox does not necessarily need to be real, nor monitored, given that it will not support having users reply to such e-mails.
Optionally, you may add recipients for the Send Email Copy To and Send Email BCC To fields, and click Ok when done.
Live processes configuration
It is important that you are aware that your cloud environments feature by default, the possibility to create and manage non-complex processes directly in the Production Environment and through the end user's Work Portal.
This means that without performing a process deployment from the development environment, you may start using your production environment through this possibility referred to as Live processes.
Whether or not you will be using Live processes, the important thing to consider is that you will need to make sure that the menu option to access this feature is aligned with your expectations and consistent for a future process deployment.
This means ensuring either:
•That you block access to this feature, both from your Bizagi Studio and in your testing or production environments (via Bizagi Management Console), before performing a process deployment and only if you decide not to admin Live processes.
•That you allow access to this feature, both from your Bizagi Studio and in your testing or production environments (via Bizagi Management Console), before performing a process deployment, if you decide that certain users will be able to admin Live processes.
Blocking this feature is done through the Security module, by including those authorized or denied roles or user groups, as shown below:
Using the WorkFolder access
When modeling your processes with Bizagi Studio and for certain features, you may need to upload files for configuration or for validation purposes.
Through this secure access, you will be able to transfer files from your work station and into a local path of the Studio.
By clicking on the WorkFolder access, you will open up an explorer to that local path:
In the above image, you will notice the following 8 helpful possibilities:
1.Trace folder: Provides access to a folder where you can view trace files, as recorded from business rules as defined and enabled by you.
2.DeleteTemp: Executes a series of steps aimed at restarting the development environment services when wanting to dispose the current cache and force a reload.
3..Bex files: For process deployment purposes, you may save export packages in this path to then be moved to a different environment.
4.Images and general files: Files allowing you to test the processes in at runtime in terms of using and viewing case attachments.
5.Template files such as .doc or .xls: Template documents allowing you to configure the automatic generation of PDFs, Word documents, or Excel spreadsheet.
6.Widgets: Files allowing you to configure the use of your own Widgets.
7.Bizagi Connectors: Files allowing you to configure the use of your own Bizagi Connectors.
8.Temporary: Provides access to a folder where you can view log files regarding execution of logic in integration points (e.g, execution of connectors, web services, SAP connector, etc).
At any time, you may validate or test the applications you have designed so far in the development environment, by using the Run button in Bizagi Studio.
Through this button, you execute the Bizagi Work portal directly in a browser, and this is specially useful to present/demo or for quick prototyping purposes.
It is important to use this button to ensure that major changes you have made in your applications are reflected (not just merely refreshing the browser if already open).
For a complete user guide about all Bizagi Studio features and its UI explained, refer to http://help.bizagi.com/bpm-suite/en/index.html?process_automation.htm.