Revision as of 09:54, May 10, 2019 by Umamaheswari.85 (talk | contribs) (→‎Gplus Adapter for Salesforce Configuration Options)
Jump to: navigation, search

Automatic_Number_Identification

Also known as ANI. A feature that passes a caller’s telephone number over the network to the receiving location, so that the caller can be identified. Sometimes referred to as a “Caller ID.” ANI is a North American term, and Calling Line Identification (CLI) is an alternative term that is used elsewhere.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Gplus Adapter for Salesforce Configuration Options

Important
The options on this page are primarily for use with Gplus Adapter for Salesforce. A few of the adapter-specific options also apply if you're using the WWE — see Workspace Web Edition options for detailed options or Web Services and application configuration guide for detailed information.

The Gplus Adapter for Salesforce has its own configuration options that you set in the [crm-adapter] section and it also takes advantage of some of the Workspace Web Edition options, set in the [interaction-workspace] section. As with Workspace Web Edition, you can apply configuration options to the Web Services Cluster Application, Agent Group, Person, and so on — see Configuration and Administration by Using Options and Annexes for details about the option override order.

Gplus Adapter for Salesforce options


click-to-dial.preprocessing-rules

  • Default Value: default
  • Valid Values: default, none, or a comma-separated list of pre-processing rule section names
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the pre-processing rules to apply to the phone number before making a dial request. If the option is not defined, the default rule is applied. The possible values are:
    • default — applies the default rules:
      • If the phone number is 10 digits, add +1.
      • If the phone number is 11 digits, add +.
      • If the phone is greater than 11 digits and doesn't start with 011, add 011.
    • none — turns off pre-processing.
    • <pre-processing-rule-section-name(s)> — name of the pre-processing rule section(s). Within a rule section, you must set the following key/value pairs:
      • expression — A regex that defines the condition to be matched.
      • prefix — The prefix to be added to the phone number if the expression is matched.
      • description — A short description of the rule.

Here's how the default rules would be configured: 

[crm-adapter]
click-to-dial.preprocessing-rules: preprocessing-rule-10-digit-US-numbers, 
preprocessing-rule-11-digit-US-numbers, preprocessing-rule-international-numbers

[preprocessing-rule-10-digit-US-numbers]
expression: ^[0-9]{10}$
prefix: +1
description: "If it is 10 digits add +1"

[preprocessing-rule-11-digit-US-numbers]
expression: ^[0-9]{11}$
prefix: +
description: "If it is 11 digits, add +"

[preprocessing-rule-international-numbers]
expression: ^(?!011)[0-9]{8,}$
prefix: 011
description: "If it is greater than 11 digits and doesn't start with 011, add 011"
Important
The adapter runs each rule in sequence until it finds a match and adds the prefix. No further rules are executed.

feedback.submit-after-disconnect

  • Default Value: never
  • Valid Values: always, prompt, never
  • Changes Take Effect: When the session is started or restarted.
  • Description: This option controls how the adapter handles the submission of feedback logs after the adapter is disconnected from GWS. When set to always, the adapter always submits feedback logs without asking the user. When set to prompt, the user is prompted to allow the Adapter to submit feedback logs. When set to never, no feedback logs are submitted.

salesforce.activity-log.enabled-call-types

  • Default Value: Inbound, Outbound, Internal
  • Value Values: A comma-separated list of call types (Inbound, Outbound, Internal) or an empty value to disable all.
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the call types the adapter should create activity history entries for in Salesforce.

salesforce.activity-log.enabled-chat-types

  • Default Value: Inbound
  • Value Values: A comma-separated list of chat types (Inbound, Consult) or an empty value to disable all.
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the chat types the adapter should create activity history entries for in Salesforce.

salesforce.activity-log.field-mapping

  • Default Value: None
  • Valid Values: The name of a configuration section that contains the mapping.
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the name of the configuration section where the mapping is defined. In that section, each key must correspond to a UserData key the adapter should look for and each value must correspond to the name of the custom activity field in Salesforce. If this option is not defined or has a blank value, no custom values are added when the adapter creates the activity history. Also, if a given key is not present in the UserData or does not have a value, the adapter doesn't include it in the activity creation request.

Here's an example of how to configure the mapping: 

[crm-adapter]
salesforce.activity-log.field-mapping=my-field-mappings

[my-field-mappings]
firstName=first_name__c
lastName=last_name__c

salesforce.chat.include-transcript-in-desc

  • Default Value: true
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies whether the adapter saves the chat transcript as part of the activity description in Salesforce.

salesforce.chat.transcript-custom-field-name

  • Default Value:
  • Valid Values: Name of a custom field in Salesforce
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the name of a custom activity field in Salesforce. If set, the adapter saves the chat transcript to this field in Salesforce. Note: Salesforce Lightning Experience supports only 255 characters for Text fields. If you configure the Text fields to store the chat transcripts and set the length of characters as 255, only the first 255 characters of the chat transcript will be saved in the Activity History and the remaining transcript will be truncated. However, you can still view the Details and Case Data of the chat interaction in the My History tab in Agent Desktop. Whereas, if you configure the Text field's character length with a value less than 255, then, an activity might not get created in Salesforce if the chat transcript exceeds the configured character length.

salesforce.email.include-body-in-desc

  • Default Value: false
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: When set to true, includes the text version of the email body in the activity description in Salesforce. The email body is saved only for inbound emails and outbound replies.

salesforce.enable-in-focus-page-transfer

  • Default Value: false
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies whether to update the call data with the ID of the object the agent is looking at in Salesforce when performing a voice or chat conference or transfer. If set to true, the agent receiving the voice or chat conference or transfer gets a screen pop for the most relevant object.

salesforce.keep-session-alive

  • Default Value: false
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies whether to prevent the adapter from logging out of Salesforce when there is no activity in Salesforce beyond a configurable time period. If set to true, the adapter refreshes the Salesforce session at short intervals and keeps the adapter-Salesforce session alive.

salesforce.user-data.object-id-key

  • Default Value:
  • Valid Values: A valid user key name to store the Salesforce object id. For example: sf_object_key
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the key the adapter uses when saving the ID of the focused Salesforce object to attached data.

salesforce.user-data.object-name-key

  • Default Value:
  • Valid Values: A valid user key name to store the Salesforce object name. For example: sf_object_name
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the key the adapter uses when saving the name of the focused Salesforce object to attached data.

salesforce.user-data.object-type-key

  • Default Value:
  • Valid Values: A valid user key name to store the Salesforce object type name. For example: sf_object_type
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the key the adapter uses when saving the type of the focused Salesforce object to attached data.

screenpop.enable-for-internal-calls

  • Default Value: true
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies whether the adapter initiates screen pops for internal calls.

screenpop.enable-for-consult

  • Default Value: false
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies whether the adapter initiates screen pops for consultation calls regardless of screenpop.enable-for-internal-calls option configuration.

screenpop.id-key-regex

  • Default Value:
  • Valid Values: A regular expression that matches a UserData key.
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies a regular expression pattern used to match a UserData key. This key's value should contain the ID of an object to screen pop in Salesforce. As with the existing screen pop behavior using the "id_" prefix, if multiple matching keys are present, the adapter only uses the first one. If this option isn't defined, the adapter uses the existing "id_" prefix logic.

screenpop.include-ani-in-search

  • Default Value: true
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies whether the ANI is used in the screen pop search.

screenpop.on-ringing

  • Default Value: false
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies whether the adapter initiates a screen pop in Salesforce when the call is ringing. If not set or false, the adapter initiates a screen pop when the call is established.

screenpop.chat.on-invite

  • Default Value: false
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies whether the adapter initiates a screen pop in Salesforce immediately after displaying the chat invite notification. If the option is not set or false, the adapter initiates a screen pop only when the agent accepts the chat invite.

screenpop.email.on-invite

  • Default Value: false
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies whether the adapter initiates a screen pop in Salesforce immediately after displaying the email invite notification. If the option is not set or false, the adapter initiates a screen pop only when the agent accepts the email invite.

screenpop.openmedia.on-invite

  • Default Value: false
  • Valid Values: true, false
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies whether the adapter initiates a screen pop in Salesforce immediately after displaying the open media invite notification. If the option is not set or false, the adapter initiates a screen pop only when the agent accepts the open media invite. This option supports the open media items configured in the openmedia.workitem-channels option.

screenpop.preprocessing-rule

  • Default Value: default
  • Valid Values: default, none, or a pre-processing rule section name.
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the pre-processing rule to apply to the ANI before showing the screen pop. If the option is not defined, the default rule is applied. The possible values are:
    • default — applies the default rule, which removes +1 from the beginning of the ANI.
    • none — turns off pre-processing.
    • <pre-processing-rule-section-name> — name of the pre-processing rule section. Within this rule section, you must set the following key/value pairs:
      • expression — A regex that defines the condition to be matched.
      • replacement — The string to replace the matched substring. If you set this value to empty, this removes the matched section.
      • description — A short description of the rule.

Here's how the default rule would be configured: 

[crm-adapter]
screenpop.preprocessing-rule: preprocessing-rule-remove-prefix

[preprocessing-rule-remove-prefix]
expression: ^\\+1
replacement: 
description: "Remove +1 from the beginning of the number"

screenpop.search-key-regex

  • Default Value:
  • Valid Values: A regular expression that matches one or more UserData keys.
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies a regular expression pattern used to match one or more UserData keys. The values for these keys are used to build the search and screen pop expression in Salesforce. If this option is not defined, the adapter uses the existing "cti_" prefix logic.

screenpop.transfer-object-key

  • Default Value: id_transfer_object
  • Valid Values: A valid key
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the custom UserData key the adapter should use for the object ID of the focused page in Salesforce.

templates.salesforce.<interaction type>.subject

  • Default Value: {interaction.callType} call to {interaction.dnis}
  • Valid Values: A string with custom template variables wrapped in "{" and "}"
  • Changes Take Effect: When the session is started or restarted.
  • Description: Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity. You can specify the value for <interaction type> argument in the option name. <interaction type> is either inbound-voice, outbound-voice, transfer-voice, chat, or email.

Set the value of this option to a string that contains custom template variables wrapped in "{" and "}". For details, see Custom templates.

Comments or questions about this documentation? Contact us for support!