Using Actions with Cards (Managed Package)

For the managed package runtime, cards use Vlocity Actions, OS Actions, and Custom Actions to launch procedures. For example, a card can launch an Omniscript, run an Apex class, redirect to a URL endpoint, and so on.

This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

For LWC enabled cards, see Using Actions with LWC Cards (Managed Package).

• Vlocity Actions: Adds preconfigured actions created in the Vlocity Actions tool in your org. Vlocity Actions are reusable on multiple cards. See Vlocity Actions (Managed Package).

• Custom Actions: Create an action unique to the card state. A custom action is not reusable on other cards. See Adding a Custom Action to a Card (Managed Package).

• OS Actions: Launch an Omniscript from your card state. See Launching an Omniscript from an OS Action on a Card (Managed Package).

  

  Note

  Beginning with the Vlocity Summer '19 release, launch an LWC Omniscript from an OS Action. See Launching an LWC Omniscript from an OS Action on a Card (Managed Package).

• Adding a Custom Action to a Card (Managed Package)
  For the managed package runtime, add actions directly on a card with Custom Actions. Custom Actions perform faster than standard Vlocity Actions but have fewer configuration options.
• Adding a Vlocity Action to a Card (Managed Package)
  For the managed package runtime, add reusable actions to a card with Vlocity Actions to launch Vlocity Omniscripts, Vlocity Cards components, web pages, or external applications.
• Configuring Action Options (Managed Package)
  For the managed package runtime, configure additional options for Vlocity Actions, Omniscript Actions, and Custom Actions on a card state by enabling the Action Options feature.
• Displaying Conditional Actions on a Card (Managed Package)
  For the managed package runtime, you can use conditions to show or hide actions on a card based on the card data. For example, you can have a card display one set of actions for a Policy card when the Status is New, and a different set when the Status is not New. To do this, clone a state on the card, modify the actions, and use conditions to determine when to display each state.
• Launching an Omniscript from an OS Action on a Card (Managed Package)
  For the managed package runtime, beginning with Vlocity Insurance and Vlocity Health Winter '18, Vlocity Cards contains a configurable Omniscript Action (OS Action). The OS Action simplifies the process to navigate to an Omniscript from a card action.
• Launching an LWC Omniscript from an OS Action on a Card (Managed Package)
  For the managed package runtime, beginning with Vlocity Insurance and Vlocity Health Winter '18, Vlocity Cards contains a configurable Omniscript Action (OS Action). The OS Action simplifies the process to navigate to an Omniscript from a card action.
• Launching an LWC Omniscript from a Vlocity or Custom Action on a Card (Managed Package)
  For the managed package runtime, launch an LWC Omniscript from a card on a Community or Lightning page by configuring the URL of a Vlocity Action or Custom Action. Add a generated LWC OS component to a Community page when you do not need to pass custom parameters to the component, or add the component to a Lightning page with or without custom parameters. Add the Vlocity LWC Omniscript Wrapper component to a Community page when you need to pass parameters to the LWC Omniscript.