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

[junners]

Heya!!! Thanks for your wonderful contribution!! And yeah, promoting usage of transform element would be wonderful, it’s efficient and it does wonders! I’ll definitely look into it~

…

On Thu, Apr 24, 2025 at 3:28 AM Tom Kitt ***@***.***> wrote: *tomkittlabs* created an issue (Lightning-Flow-Scanner/lightning-flow-scanner-core#203) <#203> 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 — Reply to this email directly, view it on GitHub <#203>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOY7M7G42GLPSUHPGDRLKD23C4GNAVCNFSM6AAAAAB3YUC5V6VHI2DSMVQWIX3LMV43ASLTON2WKOZTGAYTMNZYGM3TEOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>