The following section provides recommendations and guidance regarding the configuration of the Sensai platform and its components. This section is intended to detail any specific functionality within Sensai that Administrators need to be aware of prior to deploying Sensai within their organisation.

The Sensai components that are available within Salesforce orgs can only be deployed in Lightning Experience; they are not available in Salesforce Classic. Therefore, only web browsers supported by the Salesforce.com Lightning Experience User Interface are supported. For all supported web browsers, JavaScript, cookies (including third-party cookies) and SSL 3.0 must each be enabled. For further details on Salesforce.com supported browsers, please see: https://help.salesforce.com/articleView?id=getstart_browser_overview.htm

For the Sensai web application and Sensai Salesforce component, only the latest version of the Google Chrome web browser is currently supported. Therefore, all permitted web application users and Salesforce users must access the app and component using the latest version of Chrome for Windows or Mac OS.

Note: Cloudapps recommends a minimum screen resolution of 1024 x 768 for end users, for the best possible user experience.

Salesforce users are able to log into their organisation's Sensai web application environment using their Salesforce credentials. Currently, there are no restrictions as to which Salesforce users are able to log into the web application. Providing that the Post-Installation steps have been completed, all active Salesforce users within the org can federate login to the web application.

Sensai supports the use of Salesforce and Sumo for Salesforce data to create and train models. Currently, Salesforce Opportunity and Account data can be upload or imported into Sensai and used as entities in Schema definitions. Using this data, Opportunity Predictions can be made on open Opportunities in connected Salesforce environments.

Supported Salesforce data can be supplemented with Behaviour Observation data that is generated in the Sumo for Salesforce application. Using this data, models can be created and trained that will provide the Next Best Actions functionality in the Sensai for Sumo Salesforce package.

Related Opportunity data from external systems can also be used to create and train models. This may be in the form of supplementary Account or Billing data which can be defined as part of a Schema definition.

Note: When Salesforce Account data is to be used for model training, the Account columns and values must be combined into the Opportunity entity within the Schema in order for Opportunity Predictions to be shown in the connected Salesforce environment; i.e. the Account cannot be a separate entity within the Schema definition, it must be contained within the related Opportunity entity.

CSV Files that are uploaded into the Sensai webapp must use comma separation and use UTF8 encoding in order for the file preview to work correctly.