A consultant is building an agent console for an insurance company using FlexCards to provide...

A parent FlexCard with multiple child FlexCards and Card Actions provides the most appropriate architecture because the console must present several logically distinct data groups while also supporting user interaction.

The parent FlexCard can represent the overall customer context and display high-level Account information. Separate child FlexCards can then present active Opportunities and active insurance policies. This modular design keeps the information organized while allowing each child card to focus on its own data subset.

The requirement to view and renew policies makes Card Actions important. OmniStudio FlexCard actions can navigate users to Salesforce records, launch OmniScripts, update data sources, invoke processes, or perform other record-oriented operations. A policy card can therefore provide an action to open the selected policy and another action to launch a guided renewal process.

Card States are useful when the visual presentation of a card must change according to conditions, but they do not replace separate child components where different collections such as opportunities and policies must be displayed simultaneously.

An Integration Procedure can retrieve the required Account, Opportunity, and Contract data and return a consolidated JSON structure to the FlexCard architecture. The parent and child FlexCards render their respective portions while Card Actions supply the policy-view and renewal functionality.