Documentation:HTCC:IWWDep:ActivityHistory:9.0.0

Activity History

Activity history entries are created by Gplus Adapter in Salesforce at the end of a call, chat, SMS, email, open media interaction, or an outbound campaign call. You can control which types of interactions are saved to a Salesforce activity history entry by setting the following options:

• salesforce.activity-log.enabled-call-types
• salesforce.activity-log.enabled-chat-types

  Adapter integration of SMS is the same as chat with only minor differences as described in this document. For SMS, the Activity task is created only for an unassigned contact in the Agent Workspace Communication tab. For SMS, the only UserData that can be transferred by SMS are the from and to phone numbers and the text of the SMS.

• salesforce.activity-log.enabled-openmedia-types
• salesforce.activity-log.field-mapping
• salesforce.activity-log.mode
• salesforce.activity-log.on-screenpop
• salesforce.activity-log.status
• salesforce.activity-log.ui-association

Gplus Adapter also allows you to configure the subject of the activity history record with custom templates.

Important

Gplus Adapter records text strings in the language that is specified by Salesforce configuration. Language selection in Agent Workspace has no influence on Activity History.

Activity history is also created for calls established through Genesys Softphone in Connector mode.

Task and activity creation by Gplus Adapter in Salesforce

Gplus Adapter creates activity logs in Salesforce for every interaction handled by an agent. When the agent marks an interaction as Done, Gplus Adapter searches for a corresponding contact in Salesforce and creates a task/activity for the interaction and associates it with the Salesforce object.

The rule that Gplus Adapter uses to select the correct record for activity log creation is the same as for screen pop record. The ANI phone value is used as the search main criterion. Additionally, if the call data contains a key name that is prefixed with cti_ or other optionally defined prefix, it includes those key values in the search request using OR logic.

You must ensure that all the Activity Log fields in Salesforce exist. If one or more fields do not exist in Salesforce, an error will occur when Gplus Adapter tries to update the activity.

Gplus Adapter can also create Activity Tasks in Salesforce when the screen pop is displayed. Gplus Adapter then modifies logged activity when the interaction is completed. Activity on screen pop is created for voice, chat, email, and open media (workitems) interactions. Any changes in Comments field before the interaction is completed are overwritten by Gplus Adapter. Set the value of the salesforce.activity-log.on-screenpop option to true to enable this feature. This feature is overridden by Salesforce Object Search and Salesforce Open Record. When an agent creates an email, Gplus Adapter creates an activity task. If the agent deletes the email without sending it, the activity task is not updated.

Activity Task association by Gplus Adapter in Salesforce

Gplus Adapter provides different ways that Salesforce Activity Tasks can be associated to Salesforce objects:

• Salesforce Search (default behavior)
• Salesforce Open Record

Task Association based on Salesforce Search

By default, when an activity is created, Gplus Adapter searches for records in Salesforce using Genesys interaction data to associate a created Activity Task to a Salesforce object. During object search, the following task association scenarios are possible:

• Salesforce search returns a unique object: Gplus Adapter automatically associates the Activity Task with the Salesforce object.
• Salesforce search returns no objects: Gplus Adapter saves the Activity Task in the Salesforce Task list.
• Salesforce search returns multiple objects:
  • Gplus Adapter saves the Activity Task in the Salesforce Task list if Gplus Adapter is not able to determine which object to associate the Task with because the objects have matching values.
  • Gplus Adapter associates the Activity Task to one of the multiple search results Salesforce objects if that object is opened by the agent and remains open when the interaction is completed.

For Gplus Adapter to automatically associate as many Activity Tasks as possible with a specific Salesforce object during the handling of the interaction, Genesys recommends that you ensure most, if not all, Salesforce object searches return a unique record.

If the Salesforce object is a Case and you want to associate the Activity Task to the Case, the Case must include a searchable phone number. See the following Salesforce Help documents for information about configuring searchable field in a Salesforce Case:

• Searchable fields in the Case object
• Making additional fields searchable

If an agent initiates an outbound call by using Click-To-Dial to dial a phone number from the Salesforce Case, Contact, or other object, the Adapter obtains the Salesforce Object ID then creates and associates an activity log record with the object from which the call was dialed.

By default the salesforce.activity-log.mode option is set to search_query (Salesforce Search).

Task Association based on Salesforce Open Record

You can configure the Salesforce Activity Task association behavior so that Gplus Adapter associates the Activity Task with the active Salesforce record that is open in Salesforce when the agent completes an interaction.

To enable this feature, set the salesforce.activity-log.mode option is set to open_page (Salesforce Open Record).

Gplus Adapter Object Association UI

Gplus Adapter can be configured to display the Object Association table which lists the Salesforce objects that are opened by an agent during the handling of an interaction. While the interaction is active, each time a Salesforce object is opened Gplus Adapter adds the object as a new row in the Object Association table.

To associate an object with the Activity Task, the agent can select a row in the Object Association table before the agent completes the interaction. If the agent does not select a Salesforce object from the table, Gplus Adapter associates the Activity Task to the object search result or to the currently open and active record, depending on configuration.

Important

If you navigate to a Salesforce object with a customized API Name, this object will not be added to the Object Association list.

Use the salesforce.activity-log.ui-association option to specify whether Gplus Adapter displays the Object Association table in the Interaction view in Gplus Adapter.

Activity notifications

You can configure Gplus Adapter to display confirmation messages to agents when the following Salesforce Activity Task events are successful:

• Activity Task is created.
• Activity Task is associated to a Salesforce object on Salesforce Screen pop.
• Activity task is updated.
• Activity Task is associated to a Salesforce object when an interaction is completed.

Configure the salesforce.notifications option to enable this feature.

To troubleshoot saveLog() method errors, see Expanded troubleshooting notifications.

Activity History fields

By default, Adapter updates certain Salesforce activity fields when it saves an activity history entry. Take a look at those fields and its corresponding Adapter field in the Salesforce activity fields table.

You can also create custom activity fields to store additional values as part of activity creation. See Customizing Activity Fields for more details.

Salesforce Activity Field	Genesys
Assigned To	Agent accepting Call
Created By	Agent accepting Call followed by timestamp.
Last Modified By	Agent accepting Call followed by timestamp.
Subject	Text (including the type of call, such as inbound, outbound to #Phonenumber). You can also define the subject by referring Configuring Subject fields.
Email Content	Text from the Email Body field for inbound and outbound replies. Stored as part of Comments block in Salesforce.
Due Date	Current Date
Related To	Record currently in context when an agent clicks Mark Done
Comments	Text with information from the Subject, Case Data (the full set that comes from Adapter), and Note (note data added by the agent) fields.
Status	Values are preset in the Salesforce configuration
Priority	Values are preset in the Salesforce configuration
Call Duration	Duration in seconds
Call Object Identifier	Interaction Id
Call Type	Type of call, such as inbound, outbound, or internal

Customizing activity fields

Gplus Adapter also allows you to create your own custom activity fields, and populate those fields with data specific to your organization. For example, you can create custom activity fields that can populate call, chat, SMS, or email related data in your Salesforce reports. You can also create a custom field for storing chat (and SMS) transcripts.

The first step is to create a custom activity field in Salesforce by referring Salesforce documentation.

Once you create a custom activity field in Salesforce, ensure that you define a mapping between the custom activity field and Genesys UserData keys so that the new custom field is populated with relevant data when Adapter saves an activity history.

UserData is structured as a list of data items described as key-value pairs, where the key stands for a parameter name and the value represents the current value of that parameter. Each key-value pair may contain information about only one parameter, whose value data type can be an integer, character string, binary, or unicode. User data is delivered to Gplus Adapter with the interaction and it can be accessed during mapping.

You must ensure that all the fields in the UserData you want to map exist in Salesforce and that the UserData types match the data types of the corresponding fields in Salesforce. If one or more fields do not exist in Salesforce or data types are mismatched, an error will occur when Adapter tries to update the activity.

Mapping custom activity fields

Once you create a custom activity field, ensure that you define a mapping between the custom activity field and Genesys UserData keys so that the new custom field is populated with relevant data when Adapter saves an activity history.

Define the mapping in the salesforce.activity-log.field-mapping option.

Here's an example of how to configure the mapping. In this example, "Firstname" and "Lastname" represent key names from the interaction UserData (replace these with key names from interaction UserData in your environment), and "Firstname__c" and "Lastname__c" represent the custom field names in Salesforce to which you want to map the UserData value (replace these with custom field names in your environment):

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

[custom-field-mappings]
Firstname=Firstname__c
Lastname=Lastname__c

This screenshot shows you where to find custom fields in Adapter Activity Log options and Salesforce and how they relate to the fields to which you are mapping Interaction UserData.

Important

If you change the value of Activity Log Field Mapping, make sure to validate the change by confirming that Salesforce tasks are created correctly.

Custom Status

First, you must create custom values for the Status selection drop-down list in Salesforce. Refer to Add Custom Task Types and Customize Tasks in the Salesforce Help.

Next, you can define an activity log custom status to by applied by Gplus Adapter when an interaction is ending, such as Completed, Answered, and others that fit your business needs by specifying custom statuses as values of the salesforce.activity-log.status option.

Configuring Subject field

You can configure what Adapter saves for the Subject field in the Salesforce activity by using custom templates with the templates.salesforce.<interaction type>.subject option, where, <interaction type> is either inbound-voice, outbound-voice, transfer-voice, chat (including SMS), or email.

The value is a string that contains any text, along with templating variables wrapped in the reserved "{" and "}" characters.

You can use as many instances of this option as you need to handle multiple interactions types. For example, your configuration could include options for each of the supported interaction types:

• templates.salesforce.chat.subject
• templates.salesforce.email.subject
• templates.salesforce.inbound-voice.subject
• templates.salesforce.internal-voice.subject
• templates.salesforce.openmedia.subject
• templates.salesforce.outbound-voice.subject
• templates.salesforce.transfer-voice.subject

Gplus Adapter supports only the following templating variables:

Variable	Description
interaction.ani	The number that originated the call. This variable identifies the caller for inbound calls and is best used in inbound templates.
interaction.callType	The type of call (inbound/outbound).
interaction.caseId	The unique ID of the related case.
interaction.contact	The first and last name of contact.
interaction.dnis	The last call dialed (useful for call transfer). This variable identifies the outbound location for outbound calls and is best used in outbound templates.
interaction.endDate	The date and time when interaction ended.
interaction.isConsultation	This is true if the interaction is a consultation.
interaction.startDate	The date and time when the interaction started.
userData.<key>	This can be any UserData key available for the interaction. You might also find some of the following UserData keys useful (they're included by default by Workspace Web Edition on transfers): userData.GCS_TransferringAgentName — The name of the transferring agent. userData.GCS_TransferringDate — The date and time of transfer. userData.GCS_TransferringEmployeeId — The ID of the transferring employee. userData.GCS_TransferringReason — The reason for the transfer. This is an empty string if no reason exists.
contact.EmailAddresses	A list of email addresses associated with the contact.
contact.PhoneNumbers	A list of phone numbers associated with the contact.

For example, you might want the activity for all inbound voice calls to have details about the customer's name and phone number. In this case, here's how you would configure the option:

templates.salesforce.inbound-voice.subject = Customer: {interaction.contact}, Phone Number: {interaction.ani}

If a call comes in from Willard Clinton at 123-456-7890, when the call ends Adapter creates the related activity in Salesforce with following subject field: Customer: Willard Clinton, Phone Number: 123-456-7890

Another common use case might be to include information from UserData for all inbound calls. This could come from your own UserData keys or from UserData provided by Workspace Web Edition (see the table above). For example, you want the activity history's subject to include information from your own UserData key, PurposeOfCall, and the contact's name. Here's how you should configure the option:

templates.salesforce.inbound-voice.subject = Call from {interaction.contact} about {userData.PurposeOfCall}

In this scenario, if Willard Clinton calls into the contact center and chooses the Technical Support option in the IVR, that information is saved in the PurposeOfCall UserData key. When the call ends, Adapter creates the related activity in Salesforce with the following subject field: Call from Willard Clinton about Technical Support

Saving Chat Transcripts

Gplus Adapter can save chat transcript text either as part of the activity description in Salesforce or it can save the text to a custom field name in Salesforce. See Customizing activity fields for more information on how to create a custom chat transcript field.

By default, Adapter saves the transcript as part of the description, but you can turn off this functionality with the salesforce.chat.include-transcript-in-desc option. You might want to do this if the transcript and case data are too large for the description field, which has a maximum size of 32K. In this case, you can set the salesforce.chat.transcript-custom-field-name option to the name of a custom field you defined in Salesforce — Adapter will save chat transcripts to this field instead.

Important

If you change the value of salesforce.chat.transcript-custom-field-name, make sure to validate the change by confirming that Salesforce tasks are created correctly.

Storing email content in Activity History

The body of an email can be stored as a text version in the Email Content field in the Comments block of an Activity History in Salesforce. You can turn on or off this feature by using the salesforce.email.include-body-in-desc option.

Open Media Activity History

Open Media items are documents (for example, faxes or PDFs) that might be directed to agents for handling while they are working on interactions of another type, such as email. For the Open Media interactions, the activity type is updated as inbound in the Subject and the Call Type fields of an Activity History. Other fields are updated as explained in the Salesforce activity fields table.

Use the salesforce.activity-log.enabled-openmedia-types option to specify whether activity histories are created in Salesforce for Inbound open media workitems.

Interaction History in Genesys Universal Contact Server (UCS)

Agents can view and manage their previous interactions with a Genesys UCS contact from the Agent Workspace My History tab.