"Lazy loading" in IBM BPM is not one feature but a set of techniques to avoid doing work at coach load: render sections when shown, fetch data when needed, and page big lists. The concrete options, all covered in more detail in other answers on this site:
- Tab Section / Collapsible Panel lazy rendering and Hidden visibility - the UI Toolkit only builds a view when it becomes visible (question 2439).
- Service Call / Data controls on demand - load details when a row is selected or a section opens, not with the coach (question 2527).
- Table pagination - render 15 rows, keep the rest in memory or fetch pages from a service.
- Custom coach views that defer - IntersectionObserver / staged rendering of children (question 709).
- Ajax lazy tabs in heritage / custom pages (question 56).
- Server side: services called before the coach in the CSHS instead of in its load event, parallel service calls (question 3122), and keeping tw.local small (identifiers instead of full objects) so that the coach payload stays small.
Decide with a measurement: open the coach with the browser's Network and Performance tabs; if the HTML response is big, shrink the data; if the load is CPU-bound after the response, reduce or defer views; if a service dominates, move it or run it in parallel.
References