Vlocity Facts By Gowtham

In previous post we have used Integration procedure as REST API. In salesforce we use Assignment rules to assign cases to particular queues. In this post we will assign case to queues by using decision matrix. For this example I'm going to use below mentioned json. {      "accountDetails" : {          "FirstName" :  "Community" ,          "LastName" :  "User6" ,          "Email" :  "@gmail.com" ,          "DateOfBirth" :  "1999-12-12" ,          "Premium" :  "Yes" ,          "Partner" :  "Gold"     },      "caseDetails" : {          "Subject" :  "Performance Issue" ,       ...

In Salesforce OmniStudio, we can fetch the data, create records or perform update operations by exposing an Integration Procedure to third-party applications. Instead of relying on Apex classes or methods, the Integration Procedure handles the data processing and record creation, allowing us to seamlessly create, fetch, update records in Salesforce from external systems. In this post will show how to create, update a Account, Case and user records by using Integration Procedure as REST API. Follow these Steps to implement the use case. To create records we need to get all the required the fields. In Integration procedure by using set values we can identify whether we got all required fields to create, update the records. For this example I'm going to use below mentioned json. {      "accountDetails" : {          "FirstName" :  "Community" ,          "LastName" :  "User6" , ...

1. How many levels of sobject relationships we can query in omnistudio? We can query up to five levels in DataMappers where we can extract the field values of the related objects. Consider below screen shots as example.  If we try to query more than 5 levels we will get this error ERROR at Row:X:Column:XX cannot query foreign key relationships more than 5 levels away from the root SObject 2. What is chain on step in Integration Procedure? When an OmniScript calls an Integration Procedure Action with Chain on Step enabled, the next step of the action always runs in its own transaction. 3. How to solve uncommitted work pending error. When we have Data Mapper post action followed by Http Action in integration procedure. When executing, it will give us an error. Reason for this error: Data Manipulation Language (DML) actions prior to HTTP external callouts are prohibited by the Salesforce platform. To solve th...

In Previous post we have seen about  Edit Block - Default Actions. An Edit Block  element in Omniscript allows the user to create, edit, and delete multiple records. To accomplish this, the edit blocks are repeatable blocks by default. In 3Ways, we can configure the Edit Block. Adding Default Actions Adding Custom Actions Adding Global Actions Adding Custom Actions  In Previous example we are trying to update the case description and we followed Default Action [Remote Action - Edit], if there is a requirement when case description is updated we need to update a description field with time on contact object which is related to case and Email should be triggered to the contact owner. In this scenario generally default actions will not work where we need to update other object fields and to trigger email, we can over come this by using Custom actions in edit block. We can create custom actions by using Http Action Integration Procedure Remote Action For this requirement I w...