Vlocity Facts #32 || Edit Block for Default Actions in OmniScript

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. We can configure Edit Block in 3 Ways

  • Adding Default Actions
  • Adding Custom Actions
  • Adding Global Actions

Adding Default Actions  Let us see an example to use an Edit Block in Omniscript to handle multiple records.

In our example, we will use an Edit Block to display the existing Cases linked to an Account and Contact also edit cases directly from the Edit Block.

In the Omniscript, a new DataRaptor Extract Action is added.

Here, 'ExtractCases' is the DataRaptor Extract that retrieves 3 Cases, Limit is 3.
Now a Step element is added to the Omniscript, and an Edit Block is added inside the step.
You can select the actions you need to perform from edit block by enabling those check boxes near to the actions. In this scenario I'm choosing Allow Edit check box to perform edit operations.
From the ‘Properties’ section of the Id and ContactId elements, click Edit Properties As JSON and set the hide property to true. This ensures that the elements don’t show up in the Edit block UI. They will only be used for backend field mapping.
"hide": true,  

‘Edit’ Remote Action: This updates an existing record from the Edit Block. 

Name: Cases-Edit

Field Label: Edit
Remote Class: DefaultOmniscriptEditBlock 
Remote Method: edit. This points to the ‘edit’ method in the ‘DefaultOmniscriptEditBlock’ apex class to update an existing record from the Edit Block.

In the ‘SObject Field Mapping’ section, select the object in which you want to perform the DML operations. In our example, ‘Case’ is the SObject.

Now click ‘Add SObject Field Mapping’ and map the edit block elements to the corresponding field in the SObject.

OutPut:

Same way we can configure other 2 actions New and delete. For New Action follow these steps.Drag one more Remote Action into edit block and name it according to your requirement.

  • Name: Cases-New

  • Field Label: New

  • Remote Class: DefaultOmniscriptNewBlock 

  • Remote Method: new. This points to the ‘new’ method in the ‘DefaultOmniscriptNewBlock’ apex class to update an existing record from the Edit Block.

For Delete Action follow these steps.Drag one more Remote Action into edit block and name it according to your requirement.

  • Name: Cases-Delete

  • Field Label: Delete

  • Remote Class: DefaultOmniscriptDeleteBlock 

  • Remote Method: delete. This points to the ‘delete’ method in the ‘DefaultOmniscripDeleteBlock’ apex class to update an existing record from the Edit Block.

Comments

Post a Comment

Popular posts from this blog

Vlocity Facts #01 | OmniStudio DataRaptors

DataRaptor is a mapping tool that  you can use to read, transform, and write Salesforce data. For Example. In each interaction with a digital customer  or business process, the system needs to extract the data in order to display it. If the user modifies this data or enters new data, they also need to be saved. This is where we use OmniStudio DataRaptors.  Where to use DataRaptors? Retrieving Data:   OmniScript calls  DataRaptor Extract (via the integration procedure) to read the data from Salesforce. For example, OmniScript editing an account should display data such as account name, phone number, website, and so on. Manipulating data: OmniScript captures modified and new data based on user input. For example, an agent changes the  phone number of an account. Save Data:   OmniScript calls DataRaptor Load (via the integration procedure) to write the data back to Salesforce. For example, the updated account phone number is saved back to the Account rec...
Read more

Vlocity Facts #34 || Getting the details from the URL in a FlexCard and an Omniscript

Image
 1.The parameters in the URL must be in the format c__Node, followed by their values, in order to extract the parameters from the URL. For example: If you need to show different layout or different set of actions for community users and salesforces users you can pass different parameters in URL. For Community Portal Pass Community or any other reference value in ' c__Type '. https://salesforce.lightning.force.com/lightning/cmp/ omnistudio__vlocityLWCOmniWrapper?c__target=c%3ApHXTestFlexCard&c__tabIcon=custom%3Acustom18& c__Type =Community  For Salesforce Users Pass Salesforce or any other reference value in ' c__Type '. https://salesforce.lightning.force.com/lightning/cmp/ omnistudio__vlocityLWCOmniWrapper?c__target=c%3ApHXTestFlexCard&c__tabIcon=custom%3Acustom18& c__Type =Salesforce  2. We can get the value as {Params.c__Parameter} from the FlexCard and we can execute different actions based on the input. 3. From the omniscript,  we can retrieve ...
Read more

Vlocity Facts #44 || Communication between Omniscript and Flexcard [Pub/Sub]

Image
Flexcards have the ability to trigger and listen to two kinds of events: Custom and Pubsub events . Custom Events: Facilitate the transmission of information between a child and its parent. This can occur between a child Flexcard and its parent Flexcard, or between an element and the Flexcard to which it belongs. Pubsub Events: Allows communication between two separate components. This could occur between two separate Flexcards on the same Lightning page, known as sibling Flexcards, or between a Flexcard and an Omniscript.  In this post I will discuss about Pub/Sub event. Consider we have omniscript and flexcard individually on home page when an update happens we need to show those details in flexcard. To achieve this we can use pub/sub event. Step 1: Create a omniscript according to your requirement. I'm trying to create Contact record by using Step element and data raptor post action. Now to trigger the flexcard we need to configure the messaging frame work when an update happen...
Read more