You're reading from Optimizing Salesforce Industries Solutions on the Vlocity OmniStudio Platform Implementing OmniStudio best practices for achieving maximum performance

Product type Paperback

Published in Apr 2024

Publisher Packt

ISBN-13 9781835468470

Length 278 pages

Edition 1st Edition

Tools

Salesforce

Concepts

Business Management

Author (1):

Dmitri Khanine

View More author details

Table of Contents (18) Chapters

Preface

1. Part 1:The Platform Overview FREE CHAPTER

2. Chapter 1: Understanding the Vlocity OmniStudio Platform

3. Chapter 2: A Sample Application

4. Part 2: Getting to Know the Tools

5. Chapter 3: Evaluating the Performance of an OmniStudio Implementation

6. Chapter 4: An Introduction to Load Testing

7. Chapter 5: Tracking Code Changes and Deployment

8. Part 3: Best Practices for Improving Performance

9. Chapter 6: Options for Async Execution

10. Chapter 7: Understanding Caching

11. Chapter 8: Non-Selective Queries and Data Skew

12. Chapter 9: Improving the Performance of the Service Layer

13. Chapter 10: Improving the Performance of the Presentation Layer

14. Chapter 11: DataRaptor Formula Performance Considerations

15. Chapter 12: OmniStudio Performance Anti-Patterns

16. Index

Why subscribe?

17. Other Books You May Enjoy

Async configuration options for Integration Procedures

As with almost everything on the Salesforce platform, an Integration Procedure, including all its actions, by default is running in a single transaction. And every transaction must stay within governor limits. Because all the code running on the Salesforce platform needs to play well in a multitenant environment, the platform strictly enforces governor limits to make sure that no shared resources are monopolized or abused—intentionally or unintentionally.

So, if an Integration Procedure hits any of the governor limits by, say, running more than 100 SOQL queries or taking longer than 10 seconds of CPU time (at the time of this writing), Salesforce terminates the transaction, and the Integration Procedure fails.

The good news, though, is that we can configure an Integration Procedure to start a new transaction each time it is about to hit a governor limit. This feature is called chaining, and when this happens, the OmniStudio...