QuestionQ85

VerifiedOmniStudio User Interface

A business is building an agent console with FlexCards to provide a 360° customer view. The business wants the following information displayed:

  • Account information, including account name, phone, and website
  • Active opportunities related to the account
  • Active contracts related to the account
  • The ability to view and renew contracts

An Integration Procedure will retrieve the Account, Opportunity, and Contract data.

How should the consultant design the FlexCards to satisfy these requirements?

Explanation

A parent FlexCard can display the account-level fields and embed reusable child FlexCards for the separate active-opportunity and active-contract data nodes. FlexCard actions support operations such as navigation, launching an OmniScript, or displaying a flyout, which enables users to view and renew contracts. Card states are for condition-based layouts and interactions, rather than simultaneously presenting separate related-data sections.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!