Skip to content

Allow "Reduce Knowledge" component to filter on any entities in the bundle, not just the triggering entities #13264

@romain-filigran

Description

@romain-filigran

Use case

The "Reduce Knowledge" component currently only works if the filtering result matches the entity that triggered the playbook. This creates a significant limitation that prevents useful playbook implementations.

The reduce step fails (takes "unmatched" route) whenever the filtered entities don't include the original triggering entity, even if the bundle contains valid entities matching the filter criteria.

Current Workaround

N/A

Proposed Solution

The "Reduce Knowledge" component should be able to filter and reduce on any entities present in the bundle, regardless of which entity triggered the playbook.

Sub-issues

Metadata

Metadata

Labels

enterprise editionuse to identify feature part of the Enterprise Edition licencefeatureuse for describing a new feature to developplaybookLinked to automation enginesolveduse to identify issue that has been solved (must be linked to the solving PR)

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions