Bizagi parameters configuration

<< Click to Display Table of Contents >>

Navigation:  » No topics above this level«

Bizagi parameters configuration



The Environment Configuration determines the way in which the email sending, scheduler, uploads and logging options are configured.

These options are found in the Configuration Tab in the Bizagi Management Console.




The Environment Configuration has three main options:









Before the first deployment, the configuration for ALL environments is performed in Development in Bizagi Studio. The first deployment will take the configuration to each of the environments. From then on changes to Environment Configuration are local to each environment from the Management Console.

If you want those changes to be permanent, and become part of the process design, please make them in the development environment as well.




From this option, you can configure the parameters of email sending for your environment, let it be Development, Test or Production.





The parameters to be configured are:




Notifications options

Enable Email

Allows or restricts Bizagi to send emails. If checked, emails will be sent. If not checked, emails will be ignored.

SMTP Server

Bizagi PaaS includes its own email service. Please type in the server details that were provided from Bizagi Cloud Operations team.

SMTP Server Account

Your Bizagi PaaS email service account must be inserted here.

Send Email Copy to

Defines an email account to where a copy of all mails sent by the application will be sent

Send Email BCC to

Defines an email account to where a BLIND copy of all mails sent by the application will be sent

Email integration

Enable lookup email

Enables you to retrieve emails from the configured account to be able to complete tasks via email, without entering the Work Portal.

Connection type

Depending on your company's requirements the available options are Exchange, POP3 and IMAP.

Enable SSL

Defines whether Bizagi will use SSL to connect to your server or not. This option depends on your Mail Server configuration, and it is available when the connection type is POP3 or IMAP.


Defines the connection Port to your Mail Server. This option is available when the connection type is POP3 or IMAP.


Defines the account that will receive the email replies sent by end users.

Mailbox Service / Host

When Exchange is selected, the Mailbox service receives the Exchange Web Service URL, which is an .asmx URL, the default URL for this service is https://[MailServer]/EWS/Exchange.asmx. Click here for more information about EWS and how to determine it.

When POP3 or IMAP are enabled, defines the server's name or IP of your Mail Server


Defines a valid username within your Mail server in order to perform the connection.


The previously mentioned user's password.



From this option, you can configure the parameters of Advanced features for each environment (Development, Test, Production).




The parameters that can be configured are:





Upload Max File Size

Defines the maximum file size allowed in bytes of files to be uploaded.


Consider the next table in order to convert to bytes the most common units of measurement for data storage



1 KB (Kilobyte)


1 MB  (Megabyte)


1 GB (Gigabyte)



SOA Business Key Enforcement

The option to unmark this checkbox, is available for Bizagi .NET.

If checked, using the SOA layer Bizagi will display an exception if you attempt to register a business key pointing to a parameter entity that does not exist in Bizagi.

If not checked the business key will be saved as null.


Enable Entity Logs

Enables the logging of information on the entities, and the logs of changes in user's configuration



This parameter is used to configure a Timeout for synchronous Web Services. If the value specified is less than or equal to zero, it will be ignored. Therefore, Bizagi will wait for a reply of success or failure, no matter how long it takes. Since this can cause blockages we suggest setting a value.


Disable Abort Notifications

When selected, Abort notifications will not be sent. Abort notifications are sent to all users who have pending tasks in a case that is aborted in the Work Portal.




From this option, you can add, edit and delete different project parameters for each environment (Development, Test, Production).




To add new parameters, click the plus sign (green_plus_add). A new window will appear. Define the name, value and description for the parameter.

The edit button will display the same window, but with information about the selected parameter.

Selecting a parameter and clicking the cross icon (red-cross-icon) will remove the parameter.


Custom parameters can then be used in a Scripting Expression in the following way:


CHelper.getParameterValue("PARAMETER_NAME") ;


If you create a custom parameter named LOGOSPATH, you can use it in an expression in the following way:

var tmp = CHelper.getParameterValue("LOGOSPATH"); 



If you want to set a different address for the User Portal, the web.config file of the Work Portal needs to be modified (more specifically, the value associated with the SERVER_NAME key). Please note that it is not recommended to change the configuration values directly in the web.config file unless it is strictly necessary. Instead, use the Environment Configuration functionality whenever possible.


Custom Parameters in Production

To guarantee the correct performance of all environments, once deployed Custom Parameters cannot be edited or deleted.