Preface
This document provides deployment details of the product as a standalone or when deploying for CRM like (Microsoft, ServiceNow, and SAPC4C)
...
- The user must have administrative rights
| Anchor | ||||
|---|---|---|---|---|
|
...
4)
This javascript_cti_toolbar can be deployed on any window server in any application server of the user's choice (IIS, Tomcat, etc). The following section lists the steps to deploy the application on an IIS server.
...
Open the new_config.js file located on `c:\inetpub\wwwroot\JavaScript-CTI\config.js` path. Set the properties as per the below table.
Warning title Warning Please use these properties for stand-alone and mobile agent deployment. If CTI is being used inside the CRM, please follow the respective CRM Configurations
S.No Property Name Value Description 1 adminUserName admin The Finesse Admin Username, This username is used to call the different Finesse APIs 2 adminPassword ******* The Finesse Admin Password. (You'll first need to encrypt the password and then use the encrypted string here as adminPassword) 3 domain https://<finesseFQDN>:8445/ The domain name for finesse with which we are integrating 4 subDomain https://<subscriberfinesseFQDN>:8445/ The domain name for subscriber finesse with which we are integrating 5 boshURL https://<finesseFQDN>:7443/http-bind / The boshbaURL variable basically append the same Finesse Domain with a predefined URL
6 subBoshUrl https://<subscriberfinesseFQDN>:7443/http-bind/ The sub bosh URL variable basically appends the same subscriber Finesse Domain with a predefined URL 7 finesseFlavor UCCE/UCCX This property can have 2 values
- UCCE
- UCCX
Note: In the case of PCCE, we need to provide value UCCE.
8 callVariable callVariable1 Our Connector required an empty one variable which it needs to use for some internal mechanism. That variable can be any callVariable like callVariable1,callVariable2, callVariable3....callVariable10, or any ECC variable as well.
In the case of the ECC variable, we need to provide names like ECC.variableName
9 powered_by True System variable should always remain True 10 disableEndCallBtn false This should always remain false 11 getQueuesDelay 6000 This is only applicable for UCCE/PCCE deployment. This is the time by which CTI Toolbar queries the UCCE Database to display the Queue Stats 12 logoutFlag True Used in Team Performance gadget, to get the logout agents' detail as well. 13 ssoBackendURL https://192.168.*.*:8084 Javascript CTI Toolbar supports Finesse SSO login as well, and for that EF has developed its own Utility which needs to be deployed First. The Deployment Guide for SSO is available here. Once you deploy that Utility, you can then provide the link here. If Finesse is not SSO enabled, please ignore this property 14 isGadget False A System property should remain false always. 15 makeNotReadyOutboundCall false This property is used for making outbound calls in a Ready state, for CCE 12.5+ we can make calls in Ready state without any issues, but for below versions we need to set this property to true in order to make calls in ready state.
Note: The agent will be in Not Ready state after the call ends if the property is set to true.
16 defaultNotReadyReasonCode 27 This property is used for changing the agent state to Not ready for the outbound calls if made in Ready state and the makeNotReadyOutboundCall property is set to true. 17 callVariablesList {"callVariable1": "Language"} The call variables list is the config where you can decide which variables you want to display on the UI and with what name they should appear on the UI. In the list, you mention the call variable name followed by the value that will appear on the UI. So for example, if you want only call variable 1 to be displayed with the key 'language' then your config should be {"callVariable1": "Language"}. 18 newWindowAutoLogin true This property needs to be set true if we want to auto-login on the new tab/window. Else we can keep it to false. 19 tabIconChange true This property needs to be set true if we want to change the tab Icon on login, call ringing, etc. Else we can keep it to false. - Update the configurations and save the file.
Browse the configured FQDN and the application should be accessible as shown below.
