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 Environment 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.





The parameters to be configured are:





Email Configuration

Enable Email

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

SMTP Server

To use notifications in Test or Production environments please contact our Cloud Operations team to receive the configuration required to enable the service

SMTP Server Account

Defines the SMTP account (or address) used to send emails. It must be a valid e-mail address on the SMTP server.

Also provided by Bizagi Cloud Operations team.

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

Skip Recipients


Email Recipient


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

Currently the available option is Exchange


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.


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


The previously mentioned user's password.

Test Connection

Allows you to validate directly in the web management console if your email integration set up has all parameters correctly configured. This button verifies connectivity to your mailbox service, as used in runtime to complete tasks via email.

Web Services

Enable legacy web services (asmx)

This option enables or disables legacy web services.



It's strongly recommended setting the SMTP Server to ensure your emails are sent correctly.

Email integration is currently supported for Microsoft Exchange accounts. If you wish to integrate with another type of account, contact us and we'll provide what you'd need for this feature.



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




The parameters that can be configured are:






Configures the interval (in hours, minutes and seconds) of how often the Scheduler service will check whether there are pending jobs.


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

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 Job Logging

Enables the logging of information on every job execution

Enable Entity Logs

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

Enable M-M relations logs

When enabled Bizagi will create a log in the database (Attriblog) of when there are any changes (related or un-related) in M-M (multiple-to-multiple) relationships


(1) Attributes Length Maximum Threshold AND (2) Parameter Entities Instances Cache Threshold

Parameter entities in the Work Portal are handled in Cache if the number of attributes in the entity is less than the first parameter AND the number of records is less than the second parameter.


Parameter entities that have more attributes or more records than the thresholds will be loaded by demand (accessing the DB).


These parameters are used to refine the application's performance when there is a big volume of data.



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.

Logging Threshold

Threshold time in seconds to log interfaces that last more than this time.


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 properties for your environment.




To add new parameters, hover over the add icon (add_icon) that will transform into the Add Property icon and click on it. A new window will appear. Define the name, value and description for the parameter.





The edit button (edit_icon) will display the field Value to be edited.




Clicking on the trash icon (trash_icon) will remove the property.




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"); 


Custom Parameters in Production

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