Set Up Omni-Channel Developer Guide - Salesforce

1y ago
72 Views
5 Downloads
810.59 KB
98 Pages
Last View : 1d ago
Last Download : 11d ago
Upload by : Eli Jorgenson
Transcription

Set Up Omni-ChannelDeveloper GuideVersion 56.0, Winter ’23@salesforcedocsLast updated: October 14, 2022

Copyright 2000–2022 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of salesforce.com, inc.,as are other names and marks. Other marks appearing herein may be trademarks of their respective owners.

CONTENTSChapter 1: Omni-Channel Developer Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Set Up Omni-Channel Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2AgentWork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3AgentWorkSkill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11OmniSupervisorConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12OmniSupervisorConfigGroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14OmniSupervisorConfigProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15OmniSupervisorConfigQueue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16OmniSupervisorConfigSkill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18OmniSupervisorConfigUser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19PendingServiceRouting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20PresenceConfigDeclineReason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26PresenceDeclineReason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26PresenceUserConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28PresenceUserConfigProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31PresenceUserConfigUser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32QueueRoutingConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33QueueSobject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36ServiceChannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37ServiceChannelFieldPriority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42ServiceChannelStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43ServicePresenceStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44ServiceResource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45SkillRequirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49UserServicePresence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Omni-Channel Metadata API Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Omni-Channel Objects for the Salesforce Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Omni-Channel Objects for the Salesforce Console Integration Toolkit . . . . . . . . . . . . . . . 55Omni-Channel Objects for the Lightning Console JavaScript API . . . . . . . . . . . . . . . . . . 70External Routing for Omni-Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Technical Architecture and Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Integrate External Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Expected Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92INDEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

CHAPTER 1In this chapter . Set UpOmni-ChannelObjects Omni-ChannelMetadata API Types Omni-ChannelObjects for theSalesforce Console External Routing forOmni-ChannelOmni-Channel Developer GuideCustomize your Omni-Channel records and console integration with Omni-Channel API objects andconsole methods.1

Omni-Channel Developer GuideSet Up Omni-Channel ObjectsSet Up Omni-Channel ObjectsUse an API to create, retrieve, update or delete records, such as accounts, leads, and custom objects. The Salesforce data model includesseveral objects that let you control and customize your Set Up Omni-Channel records, including Set Up Omni-Channel users, routingconfigurations, and statuses.For more information on Salesforce APIs, see Which API Do I Use? in Salesforce Help.AgentWorkRepresents a work assignment that’s been routed to an agent. This object is available in API version 32.0 and later.AgentWorkSkillRepresents a skill used to route a work assignment to an agent. AgentWorkSkill is used for reporting and represents the result of arouting decision. This object is available in API version 42.0 and later.OmniSupervisorConfigRepresents the Omni-Channel supervisor configuration for an assigned group of supervisors. This object is available in API version41.0 and later.OmniSupervisorConfigGroupRepresents the group of agents who are visible to the supervisors of an Omni-Channel supervisor configuration. The group, if visible,appears in the Agents tab of Omni Supervisor. This object is available in API version 41.0 and later.OmniSupervisorConfigProfileRepresents the supervisor profiles to which an Omni-Channel supervisor configuration applies. User-level configurations overrideprofile-level configurations. This object is available in API version 41.0 and later.OmniSupervisorConfigQueueRepresents the queues that are visible to the supervisors of an Omni-Channel supervisor configuration. The queue, if visible, appearsin the Queues Backlog and Assigned Work tabs of Omni Supervisor. This object is available in API version 53.0 and later.OmniSupervisorConfigSkillRepresents the skills that are visible to the supervisors of an Omni-Channel supervisor configuration. These skills, if visible, appear inthe Skills Backlog tab of Omni Supervisor. This object is available in API version 53.0 and later.OmniSupervisorConfigUserRepresents the users to which an Omni-Channel supervisor configuration applies. User-level configurations override profile-levelconfigurations. This object is available in API version 41.0 and later.PendingServiceRoutingRepresents the routing details of a work item that’s waiting to be routed or assigned. This object is available in API version 40.0 andlater.PresenceConfigDeclineReasonRepresents the settings for a decline reason that a presence user provides when declining work. This object is available in API version37.0 and later.PresenceDeclineReasonRepresents an Omni-Channel decline reason that agents can select when declining work requests. This object is available in APIversion 37.0 and later.PresenceUserConfigRepresents a configuration that determines a presence user’s settings. This object is available in API version 32.0 and later.2

Omni-Channel Developer GuideAgentWorkPresenceUserConfigProfileRepresents a configuration that determines the settings that are assigned to presence users who are assigned to a specific profile.User-level configurations override profile-level configurations. This object is available in API version 32.0 and later.PresenceUserConfigUserRepresents a configuration that determines the settings that are assigned to a presence user. These user-level configurations overrideprofile-level configurations. This object is available in API version 32.0 and later.QueueRoutingConfigRepresents the settings that determine how work items are routed to agents. This object is available in API version 32.0 and later.QueueSobjectRepresents the mapping between a queue Group and the sObject types associated with the queue, including custom objects.ServiceChannelRepresents a channel of work items that are received from your organization—for example, cases, chats, or leads. This object isavailable in API version 32.0 and later.ServiceChannelFieldPriorityRepresents a secondary routing priority field-value mapping. This object is available in API version 47.0 and later.ServiceChannelStatusRepresents the status that’s associated with a specific service channel. This object is available in API version 32.0 and later.ServicePresenceStatusRepresents a presence status that can be assigned to a service channel. This object is available in API version 32.0 and later.ServiceResourceRepresents a service technician or service crew in Field Service and Salesforce Scheduler, or an agent in Workforce Engagement. Thisobject is available in API version 38.0 and later.SkillRequirementRepresents a skill that is required to complete a particular task in Field Service, Omni-Channel, Salesforce Scheduler, or WorkforceEngagement. Skill requirements can be added to pending service routing objects in Omni-Channel. They can be added to worktypes, work orders, and work order line items in Field Service and Lightning Scheduler. And they can be added to job profiles inWorkforce Engagement. This object is available in API version 38.0 and later. You also can add skill requirements to work items inOmni-Channel skills-based routing using API version 42.0 and later.UserServicePresenceRepresents a presence user’s real-time presence status. This object is available in API version 32.0 and later.AgentWorkRepresents a work assignment that’s been routed to an agent. This object is available in API version 32.0 and later.Supported Callscreate(), delete(), describeSObjects(), getDeleted(), getUpdated(), query(), retrieve(),undelete(), update(), upsert()Special Access RulesTo access this object, Omni-Channel must be enabled.3

Omni-Channel Developer dateTimePropertiesFilter, Nillable, SortDescriptionIndicates when the work item was accepted.ActiveTimeTypeintPropertiesFilter, Group, Nillable, SortDescriptionThe amount of time an agent actively worked on the work item. Tracks when the item isopen and in focus in the agent’s console. If After Conversation Work (beta) is in use, ActiveTimeends when the AfterConversationActualTime period ends or the agent closes the work item,whichever occurs first.Note: ActiveTime is tracked only for work that is routed using the tab-based capacitymodel.AfterConversationActualTime TypeintPropertiesFilter, Group, Nillable, SortDescription(Beta) The number of seconds an agent spent on After Conversation Work (ACW) aftercustomer contact ended. This field is available in API version 52.0 and later.AgentCapacityWhenDeclined TypedoublePropertiesFilter, Nillable, SortDescriptionThe agent’s capacity when declining work, either explicitly or through push er, Nillable, SortDescriptionIndicates when the work item was assigned to an agent,4

Omni-Channel Developer mePropertiesFilter, Nillable, SortDescriptionIndicates when the work item was , Group, Nillable, Restricted picklist, SortDescriptionIndicates the capacity model used to determine agent capacity. Valid values are StatusBasedand TabBased. This field is available in API version 50.0 and later.Note: A work item consumes agent capacity only if it was first assigned to the agent byOmni-Channel using queues or te, Filter, Nillable, SortDescriptionThe percentage of an agent’s capacity for work items that’s consumed by a specific type ofwork item from this service channel.When an agent’s combined work items reach 100%, the agent won’t receive new work itemsuntil there is enough open capacity for more work. For example, if you give phone calls acapacity percentage of 100, an agent on a call doesn’t receive new work items until thecall ends.CapacityWeightTypedoublePropertiesCreate, Filter, Nillable, SortDescriptionThe amount of an agent’s capacity for work items that’s consumed by a work item from thisservice channel.For example, if cases are assigned a capacity weight of 2, an agent with a capacity of 6 canaccept up to 3 cases before the agent is at capacity and can’t receive new work items.CloseDateTimeTypedateTime5

Omni-Channel Developer GuideFieldAgentWorkDetailsPropertiesFilter, Nillable, SortDescriptionIndicates when the work item was , Nillable, SortDescriptionDate and time when the agent declined this record.DeclineReasonTypestringPropertiesFilter, Group, Nillable, SortDescriptionThe provided reason for why an agent declined the work request.HandleTimeTypeintPropertiesFilter, Group, Nillable, SortDescriptionThe amount of time an agent had the work item open. Calculated by Close Time –Accepted Time. If After Conversation Work (beta) is in use, HandleTime ends when theAfterConversationActualTime period ends or the agent closes the work item, whicheveroccurs efaulted on create, Filter, Group, SortDescriptionIndicates whether a work item owner change triggered the direct assignment of the workitem to the agent. The default value is false. Status-Based Capacity Model has to be turnedon to use this field. This field is available in API version 50.0 and later.IsPreferredUserRequired TypebooleanPropertiesDefaulted on create, Filter, Group, Sort6

Omni-Channel Developer GuideFieldAgentWorkDetailsDescriptionIndicates whether a work item should stay with the preferred user even when the user is notavailable. The default value is false. This field is available in API version 50.0 and later.IsStatusChangeInitiated TypebooleanPropertiesDefaulted on create, Filter, Group, SortDescriptionIndicates whether a work item status change triggered the direct assignment of the workitem to the agent. The default value is false. Status-Based Capacity Model has to be turnedon to use this field. This field is available in API version 50.0 and later.NameTypestringPropertiesAutonumber, Defaulted on create, Filter, idLookup, SortDescriptionAn automatically generated ID number that identifies the r, Group, Nillable, SortDescriptionThe ID of the queue that the work assignment was originally routed to.OriginalQueueIdTypereferencePropertiesFilter, Group, Nillable, SortDescriptionThe ID of the queue that the work assignment was originally routed to. Due to API changes,OriginalQueueId is no longer recommended. Use OriginalGroupId instead.OwnerIdTypereferencePropertiesCreate, Defaulted on create, Filter, Group, Sort, UpdateDescriptionThe ID of the owner of the AgentWork. This field is available in API version 50.0 and later.7

Omni-Channel Developer GuideFieldAgentWorkDetailsPendingServiceRoutingId TypereferencePropertiesCreate, Filter, Group, Nillable, SortDescriptionThe ID of the PendingServiceRouting on page 20 from which the AgentWork was created.This field is available in API version 50.0 and , Group, Nillable, SortDescriptionThe ID of the preferred user to handle the work. This field is available in API v46.0 and later.PushTimeoutTypeintPropertiesFilter, Group, Nillable, SortDescriptionThe number of seconds set for push timeout. 0 is returned when push timeout isn’t enabled.Available in API version 36.0 and ter, Nillable, SortDescriptionIndicates when the push timeout event occurred. Available in API version 36.0 and later.RequestDateTimeTypedateTimePropertiesFilter, Nillable, SortDescriptionIndicates when the work was requested.RoutingModelFor internal use only.RoutingPriorityFor internal use only.RoutingTypeFor internal use only.8

Omni-Channel Developer GuideFieldAgentWorkDetailsSecondaryRoutingPriority TypeintPropertiesFilter, Group, Nillable, SortDescriptionIndicates the secondary routing eate, Filter, Group, SortDescriptionThe ID of the service channel that’s associated with the work assignment.ShouldSkipCapacityCheck TypebooleanPropertiesCreate, Defaulted on create, Filter, Group, SortDescriptionIndicates whether to skip checking an agent’s available capacity (true) or not (false)when an externally routed work item is created. This field is used when agents cansimultaneously handle work from both Omni-Channel queues and queues using externalrouting.When true, the receiving agent can exceed their set capacity to accept the item, but theydon’t receive more Omni-Channel routed work. When false, the receiving agent can’texceed their set capacity and must have enough open capacity to accept the item.SpeedToAnswerTypeintPropertiesFilter, Group, Nillable, SortDescriptionThe amount of time between when the work was requested and when an agent acceptedit.StatusTypepicklistPropertiesFilter, Group, Restricted picklist, SortDescriptionThe working status of the work item. Valid values are: Assigned – The item is assigned to the agent but hasn’t been opened.9

Omni-Channel Developer GuideFieldAgentWorkDetails Opened – The agent opened the item. Unavailable – The item was assigned to the agent but the agent became unavailable(went offline or lost connection). Declined – The item was assigned to the agent but the agent explicitly declined it. DeclinedOnPushTimeout – The item was declined because push time-out is enabledand the item request timed out with the agent. Closed – The item is closed. Canceled – The item no longer needs to be routed. For example: a chat visitor cancelstheir Omni-Channel routed chat request before it reaches an agent. Transferred–The item was transferred from an agent to another agent, queue, or skill.UserIdTypereferencePropertiesCreate, Filter, Group, SortDescriptionThe ID of the user that the work item was assigned to.WorkItemIdTypereferencePropertiesCreate, Filter, Group, SortDescriptionThe ID of the object that’s routed to the agent through Omni-Channel.UsageAgentWork records can only be deleted if they have the status Closed, Declined, or Unavailable. They can’t be deleted if their statusis Assigned or Opened because they’re active in Omni-Channel.AgentWork records have the status Assigned when they’re created. Once created, the record is automatically pushed to the assignedagent.While the metadata for AgentWork indicates support for upsert() and update(), these calls aren’t used with AgentWorkbecause none of its fields can be updated.Apex triggers are supported with AgentWork.Associated ObjectsThis object has the following associated objects. Unless noted, they are available in the same API version as this object.AgentWorkOwnerSharingRuleSharing rules are available for the object.10

Omni-Channel Developer GuideAgentWorkSkillAgentWorkShareSharing is available for the object.AgentWorkSkillRepresents a skill used to route a work assignment to an agent. AgentWorkSkill is used for reporting and represents the result of a routingdecision. This object is available in API version 42.0 and later.Supported Callsdelete(), describeSObjects(), getDeleted(), getUpdated(), query(), retrieve(), undelete()Special Access RulesTo access this object, Omni-Channel must be PropertiesFilter, Group, SortDescriptionThe AgentWork object associated with this ted on create, Filter, Group, SortDescriptionAfter a designated timeout period, a skill marked as additional is dropped from Omni-Channelrouting. The case is then routed to the best-matched agent, even if the agent doesn’t haveall the skills. The default value is false. Available in API version 48.0 and later.NameTypestringPropertiesAutonumber, Defaulted on create, Filter, idLookup, SortDescriptionAn automatically generated ID number that identifies the record.SkillIdTypereference11

Omni-Channel Developer ter, Group, SortDescriptionThe skill that is required or additional.SkillLevelTypedoublePropertiesFilter, SortDescriptionThe level of the required or additional skill. Skill levels can range from 1 to 10. Depending onyour business needs, you might want the skill level to reflect years of experience, certificationlevels, or license , Filter, Group, Nillable, SortDescriptionFor additional skills, specifies the order in which skills are dropped if after the specified timeoutno agent with that skill is available. Higher priority-value skills are dropped first. Lowerpriority-value skills, for example 0, are dropped last. Skills with the same priority value aredropped as a group. You can set skill priority using attribute setup for skills-based routing orApex code.WasDroppedTypebooleanPropertiesFilter, Group, SortDescriptionFor skills marked as additional, indicates if the skill was dropped from Omni-Channel routingbecause an agent with this skill was not available. The default value is false. Available in APIversion 48.0 and later.OmniSupervisorConfigRepresents the Omni-Channel supervisor configuration for an assigned group of supervisors. This object is available in API version 41.0and later.Important: Where possible, we changed noninclusive terms to align with our company value of Equality. Because changingterms in our code can break current implementations, we maintained this object’s name.12

Omni-Channel Developer GuideOmniSupervisorConfigSupported Callscreate(), delete(), query(), update(), retrieve()Special Access RulesTo access this object, Omni-Channel must be enabled.As of Spring ’20 and later, only authenticated internal and external users can access this opertiesCreate, Filter, Group, SortDescriptionThe unique name of the object in the API. This name can contain only underscores andalphanumeric characters, and must be unique in your org. It must begin with a letter, notinclude spaces, not end with an underscore, and not contain two consecutive underscores.In managed packages, this field prevents naming conflicts on package installations. Withthis field, a developer can change the object’s name in a managed package and the changesare reflected in a subscriber’s organization.Note: When creating large sets of data, always specify a unique DeveloperNamefor each record. If no DeveloperName is specified, performance slows down whileSalesforce generates one for each , Defaulted on create, Filter, Group, Sort, UpdateDescriptionIf set to true, hides the agent timeline from the supervisors assigned to this supervisorconfiguration. The default value is false.This field is available in API version 53.0 and later.LanguageTypepicklistPropertiesCreate, Defaulted on create, Filter, Group, Nillable, Restricted picklist, SortDescriptionThe language of this supervisor configuration.13

Omni-Channel Developer belTypestringPropertiesCreate, Filter, Group, SortDescriptionA unique label name for this supervisor configuration. The name must begin with a letter.The name can contain alphanumeric characters and underscores. The name can’t containspaces, two consecutive underscores, or end with an underscore. The name appears as OmniSupervisor Configuration Name in the UI.SkillVisibilityTypepicklistPropertiesCreate, Filter, Group, Nillable, Restricted picklist, Sort, UpdateDescriptionDetermines which work items based on skills are visible to the supervisors assigned to thissupervisor configuration. Possible values are: AllSkills — Show work items with all skill requirements selected in this supervisorconfiguration. AnySkill — Show work items with at least one skill requirement selected in thissupervisor configuration.This field is available in API version 53.0 and later.OmniSupervisorConfigGroupRepresents the group of agents who are visible to the supervisors of an Omni-Channel supervisor configuration. The group, if visible,appears in the Agents tab of Omni Supervisor. This object is available in API version 41.0 and later.Supported Callscreate(), delete(), query(), update(), retrieve()Special Access RulesTo access this object, Omni-Channel must be enabled.As of Spring ’20 and later, only authenticated internal and external users can access this object.14

Omni-Channel Developer GroupIdTypereferencePropertiesCreate, Filter, Group, Nillable, SortDescriptionA unique identifier for the group of agents that’s made visible to the supervisors who areassigned to the Omni-Channel supervisor configuration.This is a relationship field.Relationship NameGroupRelationship TypeLookupRefers esCreate, Filter, Group, SortDescriptionA unique identifier for the Omni-Channel supervisor configuration.This is a relationship field.Relationship NameOmniSupervisorConfigRelationship TypeLookupRefers epresents the supervisor profiles to which an Omni-Channel supervisor configuration applies. User-level configurations overrideprofile-level configurations. This object is available in API version 41.0 and later.Supported Callscreate(), delete(), query(), update(), retrieve()15

Omni-Channel Developer GuideOmniSupervisorConfigQueueSpecial Access RulesTo access this object, Omni-Channel must be enabled.As of Spring ’20 and later, only authenticated internal and external users can access this ereferencePropertiesCreate, Filter, Group, SortDescriptionA unique identifier for the Omni-Channel supervisor configuration.This is a relationship field.Relationship NameOmniSupervisorConfigRelationship TypeLookupRefers tiesCreate, Filter, Group, Nillable, SortDescriptionA unique identifier for the profile that’s associated with this Omni-Channel supervisorconfiguration. A profile can be associated with only one Omni-Channel supervisorconfiguration. This field is unique within your org.This is a relationship field.Relationship NameProfileRelationship TypeLookupRefers ToProfileOmniSupervisorConfigQueueRepresents the queues that are visible to the supervisors of an Omni-Channel supervisor configuration. The queue, if visible, appears inthe Queues Backlog and Assigned Work tabs of Omni Supervisor. This object is available in API version 53.0 and later.16

Omni-Channel Developer GuideOmniSupervisorConfigQueueSupported Callscreate(), delete(), describeSObjects(), query(), retrieve(), update(), upsert()Special Access RulesTo access this object, Omni-Channel must be enabled.Only authenticated internal and external users can access this ereferencePropertiesCreate, Filter, Group, SortDescriptionomA unique identifier for the Omni-Channel supervisor configuration.This is a relationship field.Relationship NameOmniSupervisorConfigRelationship TypeLookupRefers esCreate, Filter, Group, Nillable, SortDescriptionA unique identifier for the queue that’s made visible to the supervisors who are assigned tothe Omni-Channel supervisor configuration.This is a relationship field.Relationship NameQueueRelationship TypeLookupRefers ToGroup17

Omni-Channel Developer SkillRepresents the skills that are visible to the supervisors of an Omni-Channel supervisor configuration. These skills, if visible, appear in theSkills Backlog tab of Omni Supervisor. This object is available in API version 53.0 and later.Supported Callscreate(), delete(), describeSObjects(), query(), retrieve(), update(), upsert()Special Access RulesTo access this object, Omni-Channel must be enabled.Only authenticated internal and external users can access this ereferencePropertiesCreate, Filter, Group, SortDescriptionA unique identifier for the Omni-Channel supervisor configuration.This is a relationship field.Relationship NameOmniSupervisorConfigRelationship TypeLookupRefers esCreate, Filter, Group, Nillable, SortDescriptionA unique identifier for the skill that’s made visible to the supervisors who are assigned to theOmni-Channel supervisor configuration.This is a relationship field.Relationship NameSkillRelationship TypeLookup18

Omni-Channel Developer GuideFieldOmniSupervisorConfigUserDetailsRefers ToSkillOmniSupervisorConfigUserRepresents the users to which an Omni-Channel supervisor configuration applies. User-level configurations override profile-levelconfigurations. This object is available in API version 41.0 and later.Supported Callscreate(), delete(), query(), update(), retrieve()Special Access RulesTo access this object, Omni-Channel must be enabled.As of Spring ’20 and later, only authenticated internal and external users can access this ereferencePropertiesCreate, Filter, Group, SortDescriptionA unique identifier for the Omni-Channel supervisor configuration.This is a relationship field.Relationship NameOmniSupervisorConfigRelationship TypeLookupRefers ToOmniSupervisorConfigUserIdTypereference

Set Up Omni-Channel Objects Use an API to create, retrieve, update or delete records, such as accounts, leads, and custom objects. The Salesforce data model includes several objects that let you control and customize your Set Up Omni-Channel records, including Set Up Omni-Channel users, routing configurations, and statuses.

Related Documents:

over processes. And all of these examples clearly show that omni-channel is not simply an evolution of multi-channel. Omni-channel is a completely different approach, a different mind-set for commerce processes. A multi-channel strategy focuses on optimizing sales activities within each channel; an omni-channel strategy concentrates on customers'

Set Up Omni-Channel SOAP API Objects Use SOAP API to create, retrieve, update or delete records, such as accounts, leads, and custom objects. The SOAP API includes several objects that let you control and customize your Set Up Omni-Channel records, including Set Up Omni-Channel users, routing configurations, and statuses.

the mistake of assuming this is omni-channel, and they don't go any further. It is at this phase of the omni-channel maturity model that customer engagement begins to get interesting. Unfortunately, many enterprises make the mistake of assuming this is omni-channel, and they don't go any further. LEGACY UNIVERSAL QUEUE CHANNEL AWARE CROSS .

Omni Hotel-Capital Ballroom A Deputy / Assistant Directors Omni Hotel-Austin Room South Arts Education Omni Hotel-Capital Ballroom B Communications / Public Information Omni Hotel-Rotunda Community Development Omni Hotel-Senate Room Folk / Traditional Arts Omni Hotel-Liberty Boardroom Grants and Fiscal Office

Omni-Channel is a flexible, customizable feature, and you can configure it declaratively—that is, without writing code. . The first step towards getting your Omni-Channel implementation up and running is to create the necessary objects in Salesforce. 3. Add the Omni-Channel Utility to the Service Console

Omni-Channel- Management Framework A BearingPoint Accelerator The Omni-Channel-Management-Framework (OCM Framework) consists of seven components and serves as a basis for the strategy development as well as the operationalization of a firm-wide Omni-Channel-Management. Therefore, it enables, especially insurance companies, to build and

the dream of genuine omni-channel banking into a reality. In this whitepaper, I introduce the Omni-Channel Wheel of Fortune, a representation of the six key areas where— based on my past experience with NCR's retail banking customers—I believe banks should be focusing their efforts in order to make a holistic transition to omni-channel.

I am My Brother’s Keeper (2004) As our New Year’s celebration draws near, I once again find myself pondering the enigmatic story that our tradition places before us at this time—the story of the Binding of Isaac. Once again, I walk for those three long days with father Abraham and ponder the meaning of his journey with his son to the mountain. And once again, I find fresh meaning in the .