-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Feature
1 / 11 of 1 issue completed
Copy link
Labels
enterprise editionuse to identify feature part of the Enterprise Edition licenceuse to identify feature part of the Enterprise Edition licencefeatureuse for describing a new feature to developuse for describing a new feature to developplaybookLinked to automation engineLinked to automation enginesolveduse to identify issue that has been solved (must be linked to the solving PR)use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Description
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.
Reactions are currently unavailable
Sub-issues
Metadata
Metadata
Assignees
Labels
enterprise editionuse to identify feature part of the Enterprise Edition licenceuse to identify feature part of the Enterprise Edition licencefeatureuse for describing a new feature to developuse for describing a new feature to developplaybookLinked to automation engineLinked to automation enginesolveduse to identify issue that has been solved (must be linked to the solving PR)use to identify issue that has been solved (must be linked to the solving PR)