You are here:
Create an insClaimParticipants Card for Your Org
The Vlocity Claim Participants Lightning web component (LWC) that underlies the Claim Participant UI is wrapped in the insClaimParticipants card. Create a copy of the insClaimParticipants card for use with your org. You can use this version of the card as is, or you can create your own OmniScript to launch from the Claim Participant UI and then associate that OmniScript to the card.
Before You Begin
-
Make sure the insClaimParticipantsCard is imported and activated in your org:
-
From the App Launcher, find and select Vlocity Flex Cards.
-
Verify that insClaimParticipantCard is in the list of cards.
If the insClaimParticipantCard isn't there, you need to install it.
-
-
Create OmniScripts with the following types, subtypes, and purposes:
-
Type: Claim, Subtype: Participant Add, Purpose: Add a new participant to a claim
-
Type: Claim, Subtype: Participant Edit, Purpose: Edit an existing participant on a claim
-
The Vlocity Claim Participant LWC contains all the UI elements claims adjusters see when they're working on participants and involved items on a claim.
The insClaimParticipantsCard flex card contains only one element, which is configured with these properties:
-
Element Name: Custom LWC_0
-
Custom Lwc Name: insClaimParticipants
-
Attribute/Value pair:
-
Attribute:
recordId -
Value:
{recordId}
-
- From the App Launcher, find and select Vlocity Flex Cards.
- Scroll or search for insClaimParticipantsCards, then click the title in the list to see the versions.
- Open the version of insClaimParticipantsCards you want to base your customized card on.
-
Click Clone to clone this card.
- Give the cloned card a new Card Name.
- (Optional but Recommended) Give the cloned card a new Card Title.
- (Optional) Enter a description of this card that lets other administrators know what this card is and how to use it.
- (Optional) If you're using OmniScripts with different types and subtypes than the ones already mapped to the event listeners on the card, enter your OmniScripts into the Event Listener section.
