Troubleshooting and Debugging15% of the exam
Debug Console, Action Debugger and error logs
How to find a failure with each designer's debugging tools: the Omniscript Data JSON and Action Debugger, Action Message for chained Integration Procedures, the Flexcard action debugger's data source and action logs, Integration Procedure and Data Mapper Debug Log panels, and error logging to OmniComponentErrorLog records.
Use the Debug Console to identify failures and implement resolutions.
~6 min read · 5 practice questions ·
What the exam expects
- Use the Omniscript preview Debug panel: read the Data JSON, search the Action Debugger, copy nodes and repopulate the console.
- Show a chained Integration Procedure's progress in the calling Omniscript with Action Message.
- Read the Flexcard action debugger: data source status and response, pubsub event logs (channel, event, inputMap) and set values logs (fields, response).
- Read Integration Procedure and Data Mapper Debug Log output in Preview.
- Keep a record of production Integration Procedure failures with error logging to OmniComponentErrorLog.
Key terms:
- Data JSON: the live JSON a component holds in Preview.
- Action Debugger: the console that lists each action's request and response in Preview.
- Action Message: step property whose text the calling Omniscript's Debug pane shows during chaining.
- Debug Log: the Preview output of an Integration Procedure's steps or a Data Mapper's queries.
- OmniComponentErrorLog: sObject that stores Integration Procedure errors when error logging is on.
Key facts
Find one action among many
- Detail
- Search field in the Action Debugger
Copy one node
- Detail
- Clipboard icon next to the node, such as Remote Options
Chained IP progress in an Omniscript
- Detail
- Action Message on the chained steps, shown in the Debug pane
Pubsub event action log
- Detail
- channel, event, inputMap
Set values action log
- Detail
- fields, response
Flexcard data JSON reset
- Detail
- Doesn't reset changes made on the action debugger
Data Mapper Debug Log panel
- Detail
- Results of the Salesforce queries the Data Mapper issued
Load preview
- Detail
- Objects created are saved permanently
Integration Procedure error logging
- Detail
- Errors written to OmniComponentErrorLog records
Sources for this section (5)
- Preview and Test an Omniscripthelp.salesforce.com (opens in a new tab)
- Long-Running IP Settingshelp.salesforce.com (opens in a new tab)
- Preview and Debug a Flexcardhelp.salesforce.com (opens in a new tab)
- Preview and Test Data Mappershelp.salesforce.com (opens in a new tab)
- Handle Errors in IPshelp.salesforce.com (opens in a new tab)
- Why set Action Message on chained Integration Procedure steps?
- Which three items does a Flexcard pubsub event action log include?
- When should you enable error logging for Integration Procedures?
- Why should you take care previewing a Data Mapper Load?
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 (5 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams