Skip to content
This repository was archived by the owner on Oct 7, 2025. It is now read-only.

Releases: Flow-Scanner/lightning-flow-scanner-vsce

3.31.0 | Community Release

20 Jan 03:35

Choose a tag to compare

What's Changed

Fixed persistent issue on #134

Full Changelog: v3.30.0...v3.31.0

3.30.0 | Community Release

19 Jan 01:44

Choose a tag to compare

3.29.0 | Community Release

16 Nov 12:20

Choose a tag to compare

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): udpate core to 4.7.0 by @junners in #140
  • chore(log): add log manager for tracing purposes by @junners in #141
  • chore(core): update core to 4.8.0 trigger order rule by @junners in #142

Full Changelog: v3.27.0...v3.29.0

3.28.0 | Community Release

16 Nov 10:35

Choose a tag to compare

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.
  • feat(core): udpate core to 4.7.0 by @junners in #140
  • chore(log): add log manager for tracing purposes by @junners in #141

Full Changelog: v3.27.0...v3.28.0

3.27.0 | Community Release

12 Oct 22:05

Choose a tag to compare

What's Changed

Full Changelog: v3.25.0...v3.27.0

3.26.0 | Community Release

12 Oct 21:49

Choose a tag to compare

What's Changed

Full Changelog: v3.25.0...v3.26.0

3.25.0 | Community Release

25 Aug 03:24

Choose a tag to compare

What's Changed

Full Changelog: v3.24.0...v3.25.0

3.24.0 | Community Release

04 Aug 22:02

Choose a tag to compare

What's Changed

Full Changelog: v3.23.0...v3.24.0

3.23.0 | Community Release

02 Aug 05:05

Choose a tag to compare

What's Changed

Housekeeping release and keep our application up-to-date with latest industry standards!

Full Changelog: v3.22.0...v3.23.0

3.22.0 | Community Release

25 Jul 03:24

Choose a tag to compare

What's Changed

We're back again with another release! This time we're adding a new rule that was launched for summer 24 orgs

Rule (Configuration ID) Description
Unsafe Running Context (UnsafeRunningContext) This flow is configured to run in System Mode without Sharing. This system context grants all running users the permission to view and edit all data in your org. Running a flow in System Mode without Sharing can lead to unsafe data access.

Full Changelog: v3.21.0...v3.22.0