Vlocity - Cards Framework Test

Vlocity - Cards Framework Test What can be done in the XML interface in the card layout? - 1. Set the component name(label) you'll see in the App Builder 2. Enable or disable the component as public or private 3. Set the API version What is the {{payload}} variable? - A temporary variable used by the session variables to access the whole result of a datasource Which context variable is set in the Card Designer and allows access to any property in scope plus the {{payload}} variable? - {{session}} What can the {{session}} variable access? - It can access any property in the scope plus the {{payload}} variable When you need to make a change to a card that multiple layouts use, what is the best way to make sure that all layouts using the card also update? - Create a new version of the card What are Vlocity Cards? - Defined areas that display information and actions. Data can come from multiple sources How are Card layouts arranged? - Based on the priority and frequency of tasks What does the JSON metadata of a Vlocity Card do? - The JSON metadata determines how the card is defined, and what information/actions are available How many cards can be displayed on a layout? - Infinite What does the card state control? - 1. What the user can see and do on the card 2. The card's appearance related to its state If a card has multiple states, what determines which state is shown? - The underlying logical conditions determine which state is displayed Whats the difference between Design Time vs Run Time? - Design Time - all cards are displayed regardless of whether theyre active Run Time - only active cards display What is the difference between these two Loop Settings?: Repeat Cards vs Repeat Records? - Repeat Cards - groups cards by object type (e.g. Account, Contact, Cases) Repeat Records groups cards by the order they appear in the database What are some actions that can be done with LWC cards? - 1. Vlocity Actions - Preconfigured actions created in the Vlocity Actions tool in your org. 2. Custom Actions - create an action unique to the card state. (nonreusable on other cards) 3. OS Actions - launches an OmniScript from your card state 4. Smart Actions - generate and return actions to an LWC card at runtime by using an IP 5. PubSub Actions - fire pubsub events from an action on a LWC card How do you go about naming a card layout? - 1. Must be unique 2. All lowercase 3. Kebab case Ex. "this-is-a-unique-name" Can card titles be reused? - Yes, but card layout titles cannot be reused.