It is now possible to filter which source entities you want to initiate a reprocess action for. The reprocess action is used when an update to one source entity should also trigger the processing of a schema that isn't directly triggered by that source entity.Until now, it has been possible to reprocess by schema or source entity origin ID. With the introduction of the .filteroption, reprocessing can be done very specifically, yet flexibly and dynamically.

An example of using the filter for the reprocess action is when a product source entity type should trigger the processing of one or more category pages. Using the filter option is similar to the filter method when using references. Below is a simple example:

Read more about actions in the documentation.

Here's a bonus tip for all you eager beavers who can't wait to dive in without even glancing at the manual: Reprocess actions only kick into gear during ingest, not when you're flinging schemas around - because let's face it, schemas don't rearrange the data the reprocess actions are designed to tinker with. So, take a breather, grab a cuppa, and maybe give that documentation a cheeky little peek, eh?