Record Triggered Without Filters

[RubenHalman]

Proposed New Rule for lightning-flow-scanner-core

Rule Name: RecordTriggeredWithoutFilters
Description: Detects record-triggered flows that lack filters on changed fields or entry conditions, leading to unnecessary executions on every record change. This can degrade system performance, hit governor limits faster, and increase resource consumption in high-volume orgs.

Recommendation: Add specific field-change filters or conditions to scope the flow's trigger.
Severity: warning
Implementation Notes: Scan flow metadata for "triggerType" set to "RecordAfterSave" or similar, then check if "filterLogic" or "entryCriteria" nodes are absent or empty. If triggered without filters, flag the issue with a message suggesting targeted conditions for efficiency.