Introduction
In the previous module, you learned how pages act as the front-end of your workflow; the screens your users see as they click through an experience.
But as your page-based apps grow more powerful, the work happening behind the scenes grows, too.
Sometimes a page triggers logic that must process:
A list of results returned from an API.
A list of items a user selected.
A large dataset requiring enrichment.
Multiple objects that each need their own request.
A list of options that must be validated or transformed.
If you try to process all of these items inside a single event, you quickly run into the limitations of a single “all-in-one” step.
That’s why Tines provides explode and implode through the Event Transform action. These features are not exclusive to just pages:
Explode lets you break an array into individual events.
Implode lets you bring related item events back together into one consolidated result.
Together, they give you the power to scale your backend logic just like a real application would; processing each item independently, in parallel, and then recombining them for display on the next page.
This module teaches you what explode and implode actually mean, when to use them, and examples of how they integrate with page-driven experiences.
Learning objectives
By the end of this module, you'll be able to:
Explain what explode and implode do and when to use them in your workflows.
Configure explode and implode actions correctly to process arrays of data.
Use explode/implode patterns to build enriched, multi-item page experiences.