|
<< Click to Display Table of Contents >> Platform considerations |
Although certain features can be configured with Bizagi Studio, not all of them will be brought to Automation Service according to the defined configuration. This is because you use the same Bizagi Studio to build business applications for both on-premises use and for the cloud.
For example, features like the Bizagi database encryption make sense for on-premises setups, where the customer is fully in charge of the technological stack. The customer can manage the database server and its access, operating systems and redundancy options, and may rely on this feature to choose to encrypt sensitive or confidential information.
This configuration is not targeted for, nor taken to Automation Service, since for the cloud Bizagi already manages encryption for data at rest.
Encryption for data at rest is in place with Automation Service, and this is taken care of by our expert Platform Operations team personnel, rendering customer data secure in terms of integrity, privacy and availability.
The following options are not applicable for Automation Service, because it offers another measure which covers the same objective:
•On-premises Operational Data Store.
•Archiving toolkit.
•Analytics data store toolkit.
•Options to manage or configure the Scheduler service.
•Options to manage servers and clusters, and their licensing.
•Any other very specific options oriented to IT-related aspects, such as the path to store attachments.
•In Automation Service, you may not run processes that were:
oDownloaded from the Bizagi Process Xchange.
oCreated in a project using Oracle as the database engine.
oCreated in a project using a JEE platform.
The following table lists the features to be considered, and the adjustments required to comply with the cloud's technologies:
CATEGORY |
FEATURE |
OPTIONS & PARAMETERS |
ACTIONS REQUIRED |
|---|---|---|---|
Identity and access Management and Authentication |
Runtime authentication |
SAML 2.0 |
Supported. No action required. |
Bizagi |
Supported. No action required. |
||
OAuth |
Supported. No action required. |
||
LDAP |
Supported. Single Sign-On (SSO) is not available. Action required: setup a VPN. |
||
Multiple |
Using SAML Bizagi, OAuth or LDAP (with VPN). |
||
WS-Federation |
Not supported. |
||
Windows |
Not supported. |
||
Mixed: Windows + Bizagi |
Not supported. |
||
Custom |
Not supported. |
||
Mixed: Custom + Bizagi |
Not supported. |
||
Importing users from LDAP |
Via LDAP protocol |
Supported. Action required: setup a VPN. Performance considerations. |
|
Data integration |
Replication |
MS SQL Server |
Supported (same on-premises SQL Server versions supported). Action required: setup a VPN. Performance considerations. |
Oracle |
Not supported. |
||
Custom (other DBs) |
Not supported. |
||
Virtualization |
MS SQL Server |
Supported (same on-premises SQL Server versions supported) and SQL Azure databases. Action required: setup a VPN. Performance considerations. |
|
Oracle |
Not supported. |
||
Custom (other DBs) |
Not supported. |
||
Application integration |
Service-based |
WS Connector |
•Supported - if cloud-ready. No action required. •If not cloud-ready requires VPN setup |
Bizagi Connectors |
•Supported - if cloud-ready. No action required. •If not cloud-ready requires VPN setup |
||
ECM integration
|
•Supported - if cloud-ready. No action required. (same on-premises ECM products supported). •If not cloud-ready requires VPN setup Performance considerations |
||
Point-to-point |
SAP embedded Connector |
Supported. Action required: setup a VPN. |
|
Component library |
Supported for self-contained components. |
||
Custom Jobs |
Supported. No action required. |
||
Others |
Widgets |
Supported. No action required. |
|
Using Bizagi from external applications |
OData |
OData |
Supported. |
Bizagi SOAP Web services API |
Legacy Web services |
Not supported. |
|
WS-Security Web services |
Supported. |
||
Bizagi Web parts |
SharePoint Web parts |
Supported for SharePoint on-premises. No action required. |
|
Web parts for any portal |
Not supported. |
||
Email services |
Email server |
Via SMTP protocol |
•Supported. •You are entitled to use Bizagi's emailing service. This module is configured for all the environments of your subscription. When using this service, your process applications will send out email notifications from a SendGrid cloud service. •If you do not plan to use Bizagi's emailing service and wish to use your own email service, submit a Support ticket stating so. Refer to Email services to obtain details about this choice. |
Email integration in forms |
Exchange |
You are entitled to use Bizagi's email integration service. This module is configured for all the environments of your subscription. When using this service, your process applications will send a response to a specific mailbox service in which Bizagi uses a dedicated account. |
|
POP3 |
Not supported. |
||
IMAP |
Not supported. |
||
Others |
Database configuration |
ODS |
Not supported. |
Column level encryption |
Not supported. |
||
Utilities and resource kits |
Management Console |
Supported via Web UI. Certain options which handle servers and clusters are not applicable, as well as others regarding configuration of underlying infrastructure. |
|
Automatic Testing |
Supported. |
||
Diagnostics |
Not supported. |
||
Deployment |
One-click Deployment |
Not applicable due to infrastructure differences. |
|
Advanced Deployment (Exporting Bex) |
Supported. |
||
Time zones |
Time zones and working time schema |
By default the time zone of the server is ALWAYS UTC + 0, and cannot be changed. If you perform calculations based on the server's time zone, these need to be adjusted. For more information, refer to How to manage your Time zones configuration. |
|
Work Portal customization |
Overrides |
Performing customizations that modify files as shipped in with Bizagi (such as JS, HTML or CSS overrides and modifications) are not supported. |
Review other important considerations.
Last Updated 9/1/2023 9:20:55 AM