Flexcard build and maintenance best practices
The Flexcard practices a developer applies while building and maintaining cards: moving cards to the standard designer through a new version, the 15-20 minute update delay and the Template API setting, parent data nodes that bypass the child's source, safe custom CSS, performance settings and Design Assistant recommended limits.
Describe best practices for Flexcards.
~6 min read · 4 practice questions ·
What the exam expects
- Move managed-package-designer cards to the standard designer without losing the ability to edit them in the old designer.
- Explain why an updated card still shows the old version and what to do about it.
- Make sure a child card that receives a parent data node gets every field it displays.
- Keep custom CSS maintainable, and apply the performance settings and recommended limits the designer checks.
Key terms: standard designer (the Flexcard designer in Omnistudio Standard Runtime), Template API (a setting Salesforce Support enables so updates appear faster), data node (the parent data passed to a child card, such as {records[0]}), Design Assistant (real-time health feedback in the designer), recommended limit (a threshold that triggers an informational or warning message).
Key facts
- Detail
- Create a new version in the managed package designer first
- Detail
- Opened in the standard designer, a component can't be edited in the managed package designer
- Detail
- Allow 15–20 minutes, even after clearing cache
- Detail
- Ask Salesforce Support to enable the Template API setting
- Detail
- Child uses the parent's data; fields must exist in the parent's source
- Detail
- Salesforce Support can't assist with custom CSS issues
- Detail
- Recommended at most 7 per parent
- Detail
- Recommended at most 750
Sources for this section (5)
- Standard Designer Best Practiceshelp.salesforce.com (opens in a new tab)
- Configure Flexcard Settingshelp.salesforce.com (opens in a new tab)
- Embed Flexcard in a Flexcardhelp.salesforce.com (opens in a new tab)
- Style a Flexcardhelp.salesforce.com (opens in a new tab)
- Recommended Limitshelp.salesforce.com (opens in a new tab)
- Why create a new version before opening an active card in the standard designer?
- When should you contact Salesforce Support about a Flexcard update?
- Why deselect Preload Conditional Component on a conditional element?
- What is the recommended maximum number of child Flexcards in a parent?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 46 lessons of the Omnistudio Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (4 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams