Cloud Version Limitations

SEI can be used in the Cloud or On Premise (locally). The Cloud version has more limitations since its architecture is different than the On Premise version.

  • Distribution module: Distribution on a network folder is not possible.

  • Environment and data sources: You can only access the SEI data warehouse from the SEI cloud. Therefore, you must always synchronize data with the data warehouse in the cloud using DataSync.

    User ADMCA and users with administration rights can now add new environments:

    • You can add new environments in addition to the Production environment;

    • You can copy and paste details from a data source to another;

    • You can set a data source as Data Warehouse.

  • Security: Active Directory cannot be used to manage user access. You must use OAuth2, SAML2, or standard users.

  • Central Point Configurator: You cannot access the Central Point Configurator. If you need to change some of these parameters, you need to contact us in order to:

    • Disable Product Notifications (feature available since version 2022 R1.5);

    • Enable SQL Execution Logging or View Usage Logging.

    • Edit dashboard resolutions when exporting to PDF (to reduce the size of the generated file in exception cases).

  • Cloud DataSync: Since the SEI Cloud version uses DataSync in our cloud, you cannot synchronize data using these connectors: Excel, Access, and ODBC. If you need to use one of these connectors, you must install and use DataSync on another server (On Premise, Cloud Sage or a partner), and upload the data in the SEI Cloud.

    • The ODBC limitation will remain because the SEI Cloud version is in a multi-tenant environment and SEI will not allow the external ODBC connector to be installed directly in our Cloud.

  • Cloud environment: Since the SEI Cloud is a closed and multi-tenant environment, you cannot connect to a machine using Remote Desktop. This means that you cannot look at internal logs to investigate issues.

  • Web Client: Previously, Send Comment and Email were sending an email with the email address of the user. In Cloud, it was causing an issue because of a new security behavior. Now, the sender email address follows the format "FirstName LastName" noreply@sageenterpriseintelligence.com