<< Click to Display Table of Contents >> Options |
The Environment Configuration determines the Email server authentication configuration and Integration, Web services, SMS, Scheduler, uploads, and logging options are configured.
Environment options has three main tabs:
•Popular: Configure the parameters for your Email server authentication, Web Services and SMS for the current environment.
•Advanced: Configure the parameters for Advanced features for the current environment.
•Custom: Set the project parameters for the current environment.
Popular
From this option you can configure the parameters for your Email server authentication, Web Services and SMS for the current environment.
The parameters to be configured are:
OPTION |
DESCRIPTION |
---|---|
Email Configuration You can configure the email that sends the notifications that were automated and defined Bizagi Studio processes. These notifications play a vital role in the execution of various tasks within a business process. The different ways in which these configurations are performed depend on the email server authentication method. The idea behind each configuration is to establish the email connection parameters within the Management Console. This feature is available for all three environments such as Development, Test and Production.
To configure your Email server authentication visit the Email configuration section. |
|
Email Integration You can configure your own Email account for Email Integration. The account must be Exchange and cannot use Multifactor authentication. If your don't have an account that meets these requirements, Bizagi can provide the account, just request it by creating a ticket in our support platform. |
|
Enable lookup email |
Enables the possibility to retrieve emails from the configured account to be able to Complete tasks via email, without entering the Work Portal. |
Enable SSL |
As Exchange type does not support SSL. This option is always turned off and cannot be changed. |
Connection type |
Only Exchange is supported, POP3 and IMAP are not supported |
Port |
As Exchange type does not support SSL. This option is not editable. |
Account |
Defines the account that will receive the email replies sent by end users. |
Host |
The URL for your EWS virtual directory. In other words, the Mailbox service receives the Exchange Web Service URL, which is an .asmx URL, the default URL for Office 365, the URL is https://outlook.office365.com/EWS/Exchange.ASMX. |
User name |
Defines a valid user name within your Mail server in order to perform the connection. |
Password |
The previously mentioned user's password. |
Web Services |
|
Enable legacy web services (asmx) |
Not available |
Enable WS-Security |
This options grants access to Bizagi secure services (svc). You must request a ticket to activate the WS-Security option, and the Bizagi operations team configures this. |
User Name |
You must request a ticket to activate the WS-Security option, and the Bizagi operations team configures this. |
Password |
You must request a ticket to activate the WS-Security option, and the Bizagi operations team configures this. |
X509 Find Value |
You must request a ticket to activate the WS-Security option, and the Bizagi operations team configures this. |
X509 Find Type |
You must request a ticket to activate the WS-Security option, and the Bizagi operations team configures this. |
X509 Store Name |
You must request a ticket to activate the WS-Security option, and the Bizagi operations team configures this. |
X509 Store Location |
You must request a ticket to activate the WS-Security option, and the Bizagi operations team configures this. |
X509 Validation Mode |
You must request a ticket to activate the WS-Security option, and the Bizagi operations team configures this. |
SMS configuration |
|
Default country code |
This code will be used if a user's phone number doesn't have one. |
Code validity period |
The time in minutes in which the sent code will be valid. |
Number of codes allowed |
The number of times a user can request a code. Bizagi will not send any more codes if the number of requests reaches this number. Codes can be requested again when the time-out to between requests expires. |
Time-out between code requests |
The time in minutes that Bizagi will wait before sending new codes after reaching the maximum number of codes allowed. |
Provider |
Your SMS provider. Currently, our supported provider is Twilio. |
Account SID |
The security identifier that acts as a user name. |
Auth token |
The security identifier that acts as a password. |
From numbers |
The numbers used to send the code according to the end user's location. The default number is used when there is no match for the user's country code. To add a new number, just enter the number and their country codes associated and click pluc icon. |
For your email server authentication configuration there are three different options: Default email settings, OAuth Authentication and Basic Authentication. Depending on the email server you have and the authentication settings the server was provisioned with, you can use any of these three options.
Email Configuration with Default Authentication.
Email Configuration with OAuth Authentication.
Email Configuration with Basic Authentication.
Please note that Default email settings uses the Bizagi email server and its authentication is done through Bizagi Account's protocol. If you have an external email server, you can use OAuth Authentication or Basic Authentication and you need to know the parameters according to the provisioning the information that is described there.
To enable the sending of emails you can do it from Bizagi Studio or from the MC. From the MC you must select the Enable Email toggle switch in the Email Configuration section. If you want to know about email configuration from Bizagi Studio refer to the Completing tasks via Email article. We strongly recommend to do the email configuration on the MC.
The changes and configurations made for the email server authentication, will be reflected both in Bizagi Studio and in the Management Console if done from a Development environment. When changes are made from a Test or Production environment, it is necessary to make a deployment so that they are reflected from Bizagi Studio to the Web Management Console. |
Advanced
From this option you can configure the parameters of Advanced features for the current environment.
The parameters that can be configured are:
OPTION |
DESCRIPTION |
||||||||
---|---|---|---|---|---|---|---|---|---|
Scheduler option |
|||||||||
Interval |
Configures the interval (in hours, minutes and seconds) for how often the Scheduler service will monitor to see if there are jobs pending. |
||||||||
Web services interface options |
|||||||||
Web Services timeout |
Configures a timeout for synchronous Web Services. If the value specified is less than or equal to zero, Bizagi ignores it and waits for a reply with success or failure, no matter how long it takes. Since this can cause blockages we suggest setting a value. |
||||||||
Logging Threshold |
Bizagi logs interfaces that last more than this time. |
||||||||
Entity options |
|||||||||
Attributes length maximum 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 on demand (accessing the DB).
These parameters refine the application's performance when there is a large volume of data. |
||||||||
Parameter entities instances cache threshold |
|||||||||
Upload Options |
|||||||||
Upload max file size (Bytes) |
Defines the maximum allowed size in bytes of files to be uploaded.
Use this table to convert to bytes the most common units of measurement for data storage:
The maximum upload file size allowed by Bizagi is 25 MB. |
||||||||
Security |
|||||||||
Trusted domains (CORS) |
Cross-origin Resource Sharing. Define the domains that can interact with Bizagi. If you have not defined a domain, all the domains are enabled. Domains should be comma separated. |
||||||||
Cancel Notifications options |
|||||||||
Disable cancel notifications |
When this option is selected, cancel notifications will not be sent. Cancel notifications are sent to all users who have pending tasks in a case that is canceled in the Work Portal. |
||||||||
Include events on notifications |
When enabled, the canceled case notifications are sent to all users allocated to the case events. |
||||||||
Log options |
|||||||||
Enable job logging |
Enables the logging of information on every job execution |
||||||||
Enable M-M relationship log |
When this is selected Bizagi creates a log (Attriblog) in the database when there are any changes (relating or un-relating) in M-M (multiple-to-multiple) relationships |
||||||||
Enable entity logs |
Enables the logging of information on entities, and the logs of changes in user configurations. |
Custom
Sets the project's parameters for the current environment.
Last Updated 12/19/2024 9:42:53 AM