Skip to content

Salesforce Lightning Console JavaScript API

The Lightning Console JavaScript API and the Salesforce Console Integration Toolkit both interact with Salesforce console apps. We will use these API’s to check status of Omni-Channel Utility bar item. Example Lightning Component is used to check Omni-Channel Utility once agent has accepted the work. lightning:utilityBarAPI: The public API for the Utility Bar. lightning:omniToolkitAPI: This component provides access to the API for the Omni-channel toolkit. lightning:backgroundUtilityItem: This interface is used to indicate that the component is available to be instantiated at the app level without rendering any UI. Salesforce Console Developer Guide Omni-Channel Developer Guide Utility Bar API Omni Channel Work Accepted Background Utility Item Response object that is returned by utilityBarAPI.getAllUtilityInfo(). We can use and modify various attributes of utility bar item using this approach

Salesforce IOT for better customer experience and product support

IoT (Internet of Things). Today we live in the world of connected electronic devices. These devices can be individual devices, machines, sensors etc. All these devices generate lot of data. Companies are constantly looking to use this data and improve customer experience and products. In CRM world companies are constantly using data to improve end customer experience and support process. In our regular day to day we come across may connected devices, from mobile phones to cars. In following example we will use car and see how can we use… Read more Salesforce IOT for better customer experience and product support

Filtered related list using lightning:datatable

We can use a lightning:datatable component or aura:iteration to display data in tabular format. In this example we will use lightning:datatable component. Note: lightning:datatable components are not supported on mobile devices. For detail features supported please read At the time of writing of this blog, resizing of columns was not working. Tables can be populated during initialization using the data, columns, and keyField attributes. The keyField attribute is required for correct table behavior. It associates each row with a unique identifier. In this example we creates a table whose… Read more Filtered related list using lightning:datatable

Salesforce Change Data Capture

Change Data Capture is a design pattern to determine and records changes to a record and take some action of changed data and keep your external data store current with Salesforce data. Data integration to keep two systems synchronized in one of the following ways Have a data replication process to export data from source system and upload the data to the destination. Usually this type of process is run nightly as volume of data can be large. Changes are not reflected in near real time. Implement Change Data Capture… Read more Salesforce Change Data Capture

Propagating server side exceptions to Lightning Components.

An exception is a error condition or unexpected behavior that is encountered by an executing block of code. Exceptions can be thrown because of a error in executing code or in code that is being called by your code. Exception handling strategy is to gracefully handle error condition. Apex provides try, catch, and finally statements to gracefully recover from exceptions and throw statements to generate exception. If an end user runs into an exception that occurred in apex code, an error message appears on user interface with description of error.… Read more Propagating server side exceptions to Lightning Components.

Event Driven Architecture (EDA) within Salesforce paradigm

In this post we will discuss Event Driven Architecture (EDA) overview and its implementation within Salesforce paradigm. Event Driven Architecture (EDA) is a asynchronous software design pattern where a system A produces certain event notifications and interested consumer systems consume those event notifications, both producers and consumers systems are decoupled. Event processing takes in near real time and there are no point to point integration. Communication revolves around a publisher-subscriber model ,a sender publishes a message that one or more subscribers receivers that message. Much like morning commute time traffic… Read more Event Driven Architecture (EDA) within Salesforce paradigm

Proxy Pattern

Use Case: Proxy Service transforms and enriches payload before creating record in Salesforce. We have system A where our support agents are working are not in Salesforce(system B). These support agents need to create case in system B . System A can invoke SOAP API’s. We do not want System A to directly make calls to System B. We want mediator to proxy System B. In our case we will use MuleSoft as mediator. Initiator: System A where support agents are working. Proxy: MuleSoft is acting as a web service… Read more Proxy Pattern

Relate Salesforce records using external id in related objects.

Salesforce provides convenient way to related records when creating or upserting records for lookup relations. Using external id of related records avoids use of performing lookup SOQL queries when integrating records using create or upsert operations. Import Salesforce WSDL into SOAP UI, use create request and format message to use external id, example when creating Case to an Account(Customer) we can use external id of Account object and modify request message to replace accountId fields with following snippet. This will relate to Case to Account where external id is specified.… Read more Relate Salesforce records using external id in related objects.