Options

<< Click to Display Table of Contents >>

Navigation:  Automation Service Management > How to manage your environment with Management Console Web > Environment >

Options

The Environment Configuration determines the Web services, SMS, scheduler, uploads and logging options are configured.

 

Web_MC_013

 

Environment options has three main tabs:

Popular: Configure the parameters for Email integration, 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.

 

Web_MC_014

 

Popular

From this option you can configure the parameters for Web Services and SMS for the current environment.

 

Web_MC_015

 

The parameters to be configured are:

 

OPTION

DESCRIPTION

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

Defines the email protocol used when setting Email integration. The available option is Exchange.

If you upload a deployment package using another connection type, you will be requested to change the connection type for the package.

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)

This option grants access to Bizagi legacy services (asmx). For more information, refer to Web Service Security.

Enable WS-Security

This options grants access to Bizagi secure services (svc). For more information, refer to Web Service Security.

User Name

The user name token used for signing.

For authentication purposes of the web services, you must define a user name token (as specified by the WS-Security standard).

Password

Define a password for the above user name token.

X509 Find Value

The common name of the installed X.509 certificate.

X509 Find Type

The value which filters how to use the Find Value parameter.

For the common name, use FindBySubjectName.

X509 Store Name

The name of the store where the X.509 certificate is installed.

You may use the MMC snap-in to verify such information (https://msdn.microsoft.com/en-us/library/ms788967(v=vs.110).aspx).

X509 Store Location

The location of the store where the X.509 certificate is installed.

You may use the MMC snap-in to verify such information (https://msdn.microsoft.com/en-us/library/ms788967(v=vs.110).aspx).

X509 Validation Mode

Choose from the valid options:

ChainTrust: This one validates the certificate using the certification authority. In .NET scenarios, it may be more reliable to use this option.

PeerTrust: This one is validated by the server by checking its trusted store (recommended). PeerTrust implies that the incoming certificate has to be in the Trusted People certificate folder.

PeerOrChainTrust: Any of the previous one.

None: Trust any certificate (not recommended).

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.

 

Advanced

From this option you can configure the parameters of Advanced features for the current environment.

 

Web_MC_016

 

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:

MEASUREMENT

BYTES

1 KB (Kilobyte)

1,024

1 MB (Megabyte)

1,048,576

1 GB (Gigabyte)

1,073,741,824

 

The maximum upload file size allowed by Bizagi is 268435456 bytes (256 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.

SOA options

SOA Business key enforcement

If selected, and you use the SOA layer, Bizagi displays an exception when attempting to register a business key pointing to either a parameter or master entity that does not exist in Bizagi.

If the option is not selected the business key is saved as null.

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.

 

Web_MC_017