|
Section 1:
Omnistudio Fundamentals
|
Weight:
16% |
- Describe the Omnistudio solution and common customer use case scenarios in different industries (telco, energy, healthcare, public sector, etc.).
- Determine a projects needs by evaluating a customer's requirements, assumptions, risks, and constraints.
- Explain the purpose of Flexcards, Omniscript, Integration procedures, and Data Mapper.
- Explain Managed Package Runtime vs. Standard Runtime, Automatic Upgrades, and Manual Intervention Upgrade.
- Explain Omnistudio license requirements, Permission Set Licenses and Permission Sets.
|
|
Section 2:
Flexcards
|
Weight:
18% |
- Recommend the selection of the most efficient data source method for a FlexCard based on performance requirements and data complexity - be able to explain the functionality of the Flexcard setup properties.
- Guide in designing Flexcards to display relevant information from multiple data sources using existing or available elements (inputs, menu, data tables, charts, etc.) ensuring the data is presented clearly and logically based on the user's role and context.
- Recommend the implementation of necessary actions (e.g., links, modals, launching Omniscripts, calling Integration Procedures, Child Flexcards) on Flexcards to drive user workflows and business processes.
- Advise on utilizing conditional rendering and state variables to dynamically adjust card appearance or content based on the underlying data or user interaction.
- Prescribe the optimal placement and methods for embedding Flexcards within Salesforce (e.g., component, tab, console view) to meet strategic user enablement goals.
- Discuss best practices for Flexcards.
|
|
Section 3:
Omniscripts
|
Weight:
17% |
- Recommend effective multi-step, conditional, and branched Omniscript designs that align with defined business processes and user journeys, including multi-language support.
- Provide guidance on the appropriate Data Mappers and Integration Procedures to use within an Omniscript to efficiently fetch, transform, and save data to meet specific business outcomes.
- Recommend the proper components to be used to respond to business needs (Steps, Blocks, Inputs, Display Functions, Formulas, etc.).
- Advise on leveraging LWC (Lightning Web Component) Embeds and Custom/Standard Components within Omniscripts, including Child Omniscripts for reuse, or Flexcards to enhance the user experience and maintain corporate branding.
- Prescribe the implementation of robust validation rules, error messages, and conditional steps to guide users and manage unexpected outcomes or data inconsistencies.
- Discuss best practices for Omniscripts.
|
|
Section 4:
Integration Procedures
|
Weight:
17% |
- Provide guidance at a high level on the configuration and management of HTTP Actions within an IP to securely connect to and process data from external REST/SOAP endpoints, including authentication and request/response mapping.
- Explain, dependent upon customer use case, the configuration and management of HTTP Actions within an integration procedure to securely connect to and process data from external REST/SOAP endpoints, including authentication and request/response mapping.
- Recommend approaches for strategically utilizing Data Mapper Transform, Set Values, and Response actions within an integration procedure to transform, filter, and structure data before sending it to the client-side component.
- Discuss best practices for Integration Procedures.
|
|
Section 5:
Data Mappers
|
Weight:
17% |
- Differentiate and recommend the correct Data Mapper type (Extract, Turbo Extract, Load, Transform) based on the specific business need.
- Explain the possibilities of complex mapping, filtering, and data manipulation rules, utilizing functions and formulas to ensure data accuracy and standardization.
- Describe the techniques to optimize Data Mapper performance, such as reducing the number of queries, efficient filtering, relationship queries, caching, and avoiding unnecessary data mapping.
- Explain how Data Mapper Loads handle Salesforce ID mapping, upsert logic, and error management during data creation or updates.
- Discuss best practices for Data Mappers.
|
|
Section 6:
Best Fit Solutions
|
Weight:
15% |
- Justify and recommend architectural choices, demonstrating how Omnistudio components fit into the overall Salesforce and enterprise system landscape.
- Recommend strategies for performance optimization strategies across all components (Omniscript load time, IP execution, Data Mapper queries) to ensure scalable and efficient solutions.
- Provide guidance on the appropriate Data Mappers and Integration Procedures to use within an Omniscript to efficiently fetch, transform, and save data to meet specific business outcomes.
- Recommend practices for establishing an effective governance model for development, testing, and deployment processes, including change management and documentation standards for Omnistudio artifacts.
- Guide in the creation of a Conceptual Model, Logical Model, and Physical Model to support the business solution, including recommending optimal object design (standard vs. custom) to support Omnistudio artifacts.
|
|
Info
|
|