Summary

Well, this is the end of our tour of the OmniStudio performance and scalability anti-patterns and the better solutions we can apply to make our apps more robust on future-proof. We began by defining what an anti-pattern is and then continued to look at the three families of common performance anti-patterns, any of which could produce serious negative effects in our apps.

We began by looking at typical Loop Block configuration errors that often cause sporadic governor limit exceptions in addition to performance degradation. Then, we proceeded to review configurations where the lack of error handling was allowing Integration Procedures to continue running after a failed operation, causing performance and even more serious data corruption issues. Finally, we looked at the risky DataRaptor Extract Filter operators that frequently cause poorly performing and non-selective queries.

With this knowledge under our belt, we are equipped to recognize and stay clear of these commonly...