building-omnistudio-flexcard

Generate and validate OmniStudio FlexCard OmniUiCard metadata with Integration Procedure bindings.

803|289|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/forcedotcom/sf-skills --skill building-omnistudio-flexcard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-omnistudio-flexcard
Source: https://github.com/forcedotcom/sf-skills/tree/main/skills/building-omnistudio-flexcard
Command: npx skills add https://github.com/forcedotcom/sf-skills --skill building-omnistudio-flexcard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Eliminates the guesswork in creating OmniStudio FlexCards by guiding you to produce correct, validated OmniUiCard metadata with reliable Integration Procedure data bindings, states, actions, and accessibility.

Core Features & Use Cases

  • OmniUiCard authoring with validation: Generate production-ready FlexCard definitions and validate them against a 130-point scoring rubric across design, binding, actions, styling, accessibility, testing, and performance.
  • Integration Procedure data source binding: Configure DataSourceConfig to call the right active Integration Procedures, map input parameters, and bind response fields to card elements using merge-field syntax.
  • States, actions, and quality guardrails: Design empty/error/multi-record behaviors, configure action buttons (including OmniScript launching), and enforce common anti-pattern protections like accessibility gaps, hardcoded styling, and brittle context.

Quick Start

Use building-omnistudio-flexcard to create and validate an OmniUiCard for an OmniStudio FlexCard UI that displays Integration Procedure results with correct merge-field mappings and action buttons.

Frequently Asked Questions about building-omnistudio-flexcard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bind an Integration Procedure to an OmniStudio FlexCard?

Configure the DataSourceConfig in your OmniUiCard metadata to call the active Integration Procedure, map input parameters, and bind response fields to card elements using merge-field syntax for reliable FlexCard data rendering.

What is the best way to validate OmniStudio FlexCards before deployment?

Validate OmniStudio FlexCards by scoring metadata against a 130-point rubric covering design, data bindings, actions, styling, accessibility, testing, and performance to ensure production-ready deployment and activation.

How do I configure empty and error states for an OmniStudio FlexCard?

Design empty, error, and multi-record behaviors within the FlexCard's PropertySetConfig to manage UI states and configure action buttons, preventing brittle context and hardcoded styling anti-patterns.

Does OmniStudio FlexCard development require specific accessibility compliance?

Yes, OmniStudio FlexCard development requires accessibility compliance. Quality guardrails enforce anti-pattern protections to eliminate accessibility gaps, ensuring generated OmniUiCard metadata meets validation standards.

Can I launch an OmniScript from an OmniStudio FlexCard action button?

Yes, you can launch an OmniScript from an OmniStudio FlexCard action button. Configure the action within the PropertySetConfig structure to trigger the script while maintaining correct data source mappings.