Add New Rule - TransformInsteadOfLoop

[tomkittlabs]

I would like to suggest a new rule to suggest using Transform instead of Loop > Assignment where possible

Current Behaviour:
The scanner does not currently identify the specific pattern where a Loop element immediately leads to an Assignment element that could be replaced by Transform

Proposed Enhancement:
I propose adding a new rule named TransformInsteadOfLoop

• Description: Detects the specific sequence where a Loop element's path connects directly to an Assignment element.
  -Expected Behaviour: The scanner flags this pattern with a note severity.
• Justification: While the Loop -> Assignment pattern is valid, it can often be replaced by the Transform element which is on average 10x more performant according to docs
• Implementation Notes: Rule needs to analyse element connectors to identify the Loop -> Assignment sequence specifically on the iterative path (e.g., checking the nextValueConnector or similar property).

Purpose:
This rule encourages better Flow Performance by highlighting areas where the Transform element might be a more suitable choice than a simple Loop/Assignment combination

Docs:

• https://trailhead.salesforce.com/content/learn/modules/multirecord-elements-and-transforms-in-flows/transform-multiple-records

[vBritt0]

@tomkittlabs Thanks for the suggestion. We'll keep it in mind for when it aligns with priorities.

[RubenHalman]

This is now available in beta: https://github.com/Flow-Scanner/lightning-flow-scanner/releases/tag/action-v2.5.0

[tillaffolter]

As far as I know, the Transform flow element is currently only supported in record-triggered after-save flows (idea to support before-save flows is here https://ideas.salesforce.com/s/idea/a0BHp000016LuaaMAC/allow-transform-element-in-before-save-flow). Consequently, in my opinion, this should be taken into account by the new TransformInsteadOfLoop rule.
Currently, a violation of the TransformInsteadOfLoop rule is also reported to me in a record-triggered flow with triggerType “RecordBeforeSave.”

[RubenHalman]

@tillaffolter Thanks for raising this, and for your public support in this journey.

You’re absolutely right about Transform only being supported in record-triggered after-save flows. I’ve pushed a patch to the core module to exclude RecordBeforeSave from the rule. Depending on how dependencies are resolved, this may already apply on reload; otherwise it will be included in the next release shortly.

Really appreciate your continued feedback and involvement.

[tillaffolter]

@RubenHalman Wow, that was fast! Appreciate your responsiveness and your overall investments into this project!