Vlocity Facts #22| Pass dynamic value to Look-up element from Typeahead block element

Scenario: We need to update contact details based on Account. If user select one account record from Typeahead block, related contact records should be displayed in another drop-down.

For this scenario we can Typeahead block and lookup element. 

  • Typeahead block -- User can select the record by typing the name. 
  • Lookup -- The associated records related to the selected record will be displayed in Lookup.
Creation of Typeahead block 
While configuring Typeahead block in Typeahead Key mention the Json node based on your requirement [Name, Phone, Email ...,] which need to be displayed as a drop down for user to select.
I have given Name in Typeahead Key to display Account names.
Image  Image

Creating DataRaptor Extract 
We are passing SelectAccount as data source [Typeahead block element name]. After creating DR drag on drop into the typeahead block.
Image Image

Configuring Look-up Element
After selecting one name from the typeahead block the Id of the selected account we are passing to the look-up element as a Data Source.

Syntax : TypeAhead Block element name:Blockname:JsonNode
                                      Data Source: ChooseAccount:SelectAccount-Block:ACCId
                                      Filter Name: AId
Image  Image
Image

Populate Lookup Element with Query Results:
  • JSON Path Use As The Value In Lookup -- It will help to pass the value to the JSON sfter selecting the value from drop down in lookup.
  • JSON Path Use As The Label In Lookup -- It will help to display the value from drop down in lookup. 
Conditional View for Lookup Element
Lookup element should be displayed only when account is selected from typeahead block.
Image

Output
Image  Image
Image


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