2.37.0 | Community Release

Activation of New Rule! 🌟

Rule Id	Description	Reference
SameRecordFieldUpdates	Before-save same-record field updates allows you to update the record using variable assignments to $Record. This is significantly faster than doing another DML on the same-record that triggered the flow	As seen on architects.salesforce.com

New Command (beta)

Command	Description
flow fix	Invokes core engine's fix functionality. Rules that can be automatically fixed or identified by the property AutoFixable will be applied to flows on either directory or path

Usage

sf flow fix --rules UnusedVariable UnconnectedElement --dir <app-directory1> <app-directory2> <app-directory3>
sf flow fix --rules UnusedVariable UnconnectedElement --file <file-one> <file-two> <file-three>

v2.36.1

chore(release): 2.36.1 [skip ci]

2.36.0 | Community Release

What's Changed

New & Changed Rules:

Rule (Configuration ID)	Description
Same Record Field Updates (SameRecordFieldUpdates)	Much like triggers, before contexts can update the same record by accessing the trigger variables $Record without needing to invoke a DML.
Trigger Order (TriggerOrder)	Guarantee your flow execution order with the Trigger Order property introduced in Spring '22
Missing Fault Path (MissingFaultPath)	At times, a flow may fail to execute a configured operation as intended. By default, the flow displays an error message to the user and notifies the admin who created the flow via email. However, you can customize this behavior by incorporating a Fault Path.

• feat(core): update dependencies and update sfdx commands to sf cli by @junners in #131
• chore: bump node to node 22 by @junners in #132
• chore(core): update core to 4.8.0 trigger order rule by @junners in #133

Full Changelog: v2.34.0...v2.36.0

v2.35.1

chore(release): 2.35.1 [skip ci]

2.35.0 | Community Release

What's Changed

Rule (Configuration ID)	Description
Same Record Field Updates (SameRecordFieldUpdates)	Much like triggers, before contexts can update the same record by accessing the trigger variables $Record without needing to invoke a DML.
Missing Fault Path (MissingFaultPath)	At times, a flow may fail to execute a configured operation as intended. By default, the flow displays an error message to the user and notifies the admin who created the flow via email. However, you can customize this behavior by incorporating a Fault Path.

• feat(core): update dependencies and update sfdx commands to sf cli by @junners in #131
• chore: bump node to node 22 by @junners in #132

Full Changelog: v2.34.0...v2.35.0

v2.34.2

chore(release): 2.34.2 [skip ci]

v2.34.1

chore(release): 2.34.1 [skip ci]

2.34.0 | Community Release

What's Changed

• chore(deps): bump npm dependencies by @junners in #114

Full Changelog: v2.33.0...v2.34.0

v2.33.1

chore(release): 2.33.1 [skip ci]

2.33.0 | Community Release

What's Changed

• chore: update core to 4 by @junners in #113

Full Changelog: v2.32.0...v2.33.0