Optimizing Salesforce Industries Solutions on the Vlocity OmniStudio Platform Implementing OmniStudio Best Practices for Achieving Maximum Performance
Design highly customized solutions using the Vlocity OmniStudio platform tailored to your business Key Features Understand the critical gotchas and essential best practices for every OmniStudio implementation Discover a proven system for achieving next-level performance and scalability using Salesfo...
| Otros Autores: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Birmingham, England :
Packt Publishing
[2024]
|
| Edición: | First edition |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009815726206719 |
Tabla de Contenidos:
- Cover
- Title Page
- Copyright and Credits
- Contributors
- Table of Contents
- Preface
- Part 1: The Platform Overview
- Chapter 1: Understanding the OmniStudio Vlocity Platform
- Technical requirements
- What is OmniStudio?
- Digital Interaction Platform
- The Salesforce Industries Process Library
- Digital Experience Layer
- Service Management Layer
- Developer Experience Layer
- Summary
- Chapter 2: A Sample Application
- Technical requirements
- Hands-on lab - creating an OmniScript
- Creating an OmniScript
- Adding steps
- Creating a DataRaptor
- OmniScript preview
- Adding a FlexCard
- Adding a FlexCard to an OmniScript
- Summary
- Part 2: Getting to Know the Tools
- Chapter 3: Evaluating the Performance of an OmniStudio Implementation
- Technical requirements
- Measuring execution times in OmniStudio
- Execution times in DataRaptors
- Execution times in Integration Procedures
- Execution times in OmniScripts
- Exploring the OmniStudio Tracking Service
- Enabling tracking for OmniStudio
- Adding custom fields to event tracking
- Collecting stats and errors
- Salesforce debug logs
- Collecting debug logs in production
- Process Profiler in IDX Workbench
- Vlocity Error Log
- Summary
- Chapter 4: An Introduction to Load Testing
- Technical requirements
- Why and how to do load testing
- General considerations
- Salesforce Performance Assistant
- Running your load test
- Using Selenium for load testing
- Load testing with JMeter
- Summary
- Chapter 5: Tracking Code Changes and Deployment
- Technical requirements
- Using the out-of-the-box export and import tools
- Exporting Integration Procedures and OmniScripts
- Extracting metadata with the Vlocity Build tool
- Downloading the Vlocity Build tool
- Running the Vlocity Build tool
- Exporting Vlocity metadata.
- Deploying Vlocity metadata
- Generating a Vlocity Manifest
- Using Salesforce's SFDX tool
- Other OmniStudio configuration management tools
- Salesforce Vlocity Integration VS Code extension
- IDX Workbench
- CI tools
- Summary
- Part 3: Best Practices for Improving Performance
- Chapter 6: Options for Async Execution
- Technical requirements
- Why to consider async code execution
- Async configuration options for Integration Procedures
- Chainable
- Queueable Chainable setting
- Chain On Step
- How to call long-running Integration Procedures from the code
- Calling from Apex
- Calling from an LWC
- Async execution options in Apex
- Apex @future annotation
- Queueable Apex
- Batch Apex
- Scheduled Apex
- Summary
- Chapter 7: Understanding Caching
- Technical requirements
- What's with all the caching?
- Manual caching options
- Caching in the Salesforce platform
- Caching options in DataRaptors
- Cache blocks in Integration Procedures
- Caching the response of the entire Integration Procedure
- Caching with the Lightning Wire service
- Custom caching on the client side
- Summary
- Chapter 8: Non-Selective Queries and Data Skew
- Technical requirements
- Case study - when an indexed field performs slower than a non-indexed one
- Selective and non-selective queries
- Optimizing queries with the Query Plan tool
- Understanding data skew
- Summary
- Chapter 9: Improving the Performance of the Service Layer
- Technical requirements
- Client or server side?
- DataRaptors or an Integration Procedure?
- Integration Procedure or server calls
- Comparing relationship notation and multiple extract steps
- Using multiple extract steps
- Using relationship notation
- Boosting performance by trimming the response JSON
- DataRaptors
- Integration Procedures
- How fast the Turbo Extract DataRaptor really is.
- Summary
- Chapter 10: Improving the Performance of the Presentation Layer
- Technical requirements
- Performance impact of OmniScript best practices
- Performance impact of formulas on OmniScripts
- Performance impact of conditional views in OmniScripts
- Performance impact of merge fields in OmniScripts
- Measuring the performance of the Presentation Layer
- Measuring load times with LWC Debug Mode
- Measuring performance with Selenium
- Consider LWC lifecycle events
- Document generation options
- Summary
- Chapter 11: DataRaptor Formula Performance Considerations
- Technical requirements
- How fast are DataRaptor formulas?
- The QUERY function or another Extract?
- Limiting custom function payload size
- Summary
- Chapter 12: OmniStudio Performance Anti-Patterns
- Technical requirements
- DML, API, and Remote Action calls from Loop Block
- Better solutions
- Integration Procedure running after an error
- Better solutions
- Non-selective queries in DataRaptors
- Wildcards in Filter criteria
- Use of NULL values
- Use of EXCLUDES and NOT LIKE operators
- Summary
- Index
- Other Books You May Enjoy.
