Releases: Flow-Scanner/lightning-flow-scanner-core
Releases · Flow-Scanner/lightning-flow-scanner-core
4.11.0 | Community Release
4.10.0 | Community Release
What's Changed
Taking a step towards lowering the barrier to entry for contributing on lfs; I've decided to migrate the tests all to jest. This key move would hopefully a lower the barrier to entry from transitioning from salesforce (lwc)
Also, one thing funny that I found out whilst providing continuous updates to lfs. Mocha and chai doesn't mix well on cjs targetted projects.
Full Changelog: v4.9.0...v4.10.0
4.9.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 |
4.8.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. |
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. |
Trigger Order (TriggerOrder ) |
Guarantee your flow execution order with the Trigger Order property introduced in Spring '22 |
- chore: add tests for exceptions by @junners in #133
- add tests for core.fix by @k-capehart in #135
- fix(RuleEngine): missing fault path rule modification resolved #134 by @junners in #139
- feat(RuleEngine): same record field update new rule fixes #134 by @junners in #140
- feat(RuleEngine): make rule imports for non default rule store rules by @junners in #141
- tests(RuleEngine): add unit tests for same record field updates by @junners in #142
- feat(RuleEngine): trigger order on record triggered flows by @junners in #143
Full Changelog: v4.5.0...v4.8.0
4.7.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. |
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. |
- chore: add tests for exceptions by @junners in #133
- add tests for core.fix by @k-capehart in #135
- fix(RuleEngine): missing fault path rule modification resolved #134 by @junners in #139
- feat(RuleEngine): same record field update new rule fixes #134 by @junners in #140
Full Changelog: v4.5.0...v4.6.0
4.6.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. |
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. |
- chore: add tests for exceptions by @junners in #133
- add tests for core.fix by @k-capehart in #135
- fix(RuleEngine): missing fault path rule modification resolved #134 by @junners in #139
- feat(RuleEngine): same record field update new rule fixes #134 by @junners in #140
Full Changelog: v4.5.0...v4.6.0
4.5.0 | Community Release
What's Changed
- chore: bump npm deps to resolve cve by @junners in #131
- chore: remove eol node 18 by @junners in #132
Full Changelog: v4.3.0...v4.5.0
4.4.0 | Community Release
What's Changed
Full Changelog: v4.3.0...v4.4.0
4.3.0 | Community Release
4.2.0 | Community Release
What's Changed
Full Changelog: v4.1.0...v4.2.0