Releases: Flow-Scanner/lightning-flow-scanner
Releases · Flow-Scanner/lightning-flow-scanner
3.17.0 | Community Release
What's new?
- fix: parsing issue with custom errors element that's introduced in api version 59
Full Changelog: v3.16.0...v3.17.0
3.16.0 | Community Release
What's new?
Refactor and rewrite Loop Rule for SOQL, DML and Action Call rule
Full Changelog: v3.15.0...v3.16.0
3.15.0 | Community Release
New Rule
| Rule (Configuration ID) | Description |
|---|---|
Action Calls In Loop (ActionCallsInLoop) |
To prevent exceeding Apex governor limits, it is advisable to consolidate and bulkify your apex calls, utilize a single action call containing a collection variable at the end of the loop. |
Full Changelog: v3.14.0...v3.15.0
3.14.0 | Community Release
Full Changelog: v3.13.0...v3.14.0
3.13.0 | Community Release
3.12.0 | Community Release
Full Changelog: v3.11.0...v3.12.0
3.11.0 | Community Release
3.9.0 | Community Release
What's Changed
New Rule!
| Rule (Configuration ID) | Description |
|---|---|
Hardcoded Url (HardcodedUrl) |
Avoid hard-coding URLs as they are org-specific. Instead, use a $API formula (preferred) or you can use an environment-specific such as custom labels, custom metadata, or custom settings. |
Full Changelog: v3.8.0...v3.9.0
3.8.0 | Community Release
What's Changed
New Rule in beta!
| Rule (Configuration ID) | Description |
|---|---|
Get Record All Fields (GetRecordAllFields) |
Following the principle of least privilege (PoLP), avoid using Get Records with 'Automatically store all fields' unless necessary. |
Full Changelog: v3.7.0...v3.8.0
3.7.0 | Community Release
Full Changelog: v3.6.0...v3.7.0