Authentication Upgrade

v3.0.0 Authentication Upgrade

To upgrade to Flow Scanner v3.0.0, you must follow the new post-installation instructions provided below after uninstalling any previous versions. This release introduces a new package name and namespace, requiring a clean setup to ensure compatibility and avoid conflicts.

Authentication Upgrade

• Replaced Visualforce page and token-based authentication with a Connected App using JWT Bearer Flow for server-to-server Tooling API access.
• Leverages a self-signed certificate (Flow_Scanner) and Consumer Key stored in Custom Metadata (Flow_Scanner_OAuth_Config__mdt).
• New Apex class ToolingAPI handles JWT generation, token caching, and Tooling API queries with enhanced error handling.

Post-Installation Setup

• Manual Connected App creation required due to Salesforce 2GP packaging limitations (ghost metadata errors prevented reliable packaging).
• Steps include:
  • Creating a Connected App (Flow_Scanner_JWT) with specific OAuth settings (scopes: api, refresh_token, offline_access).
  • Generating and uploading a self-signed certificate (Flow_Scanner).
  • Copying the Consumer Key to Custom Metadata.
  • Pre-authorizing via Profiles (optional) and assigning the Flow Scanner User permission set.
• Process takes ~3–5 minutes; detailed instructions provided in README.

New Package Name and Namespace

• Package name changed to flow-scanner (ID: 0HogK0000000ZFVSA2) to avoid conflicts with prior lightning-flow-scanner installations.
• Namespace changed to lfscanner for the same reason.
• Recommendation: Uninstall previous versions before installing v3.0.0 to prevent namespace or metadata conflicts.

UI Makeover

• Adds all results by navigation
• Adds overall styling improvements
• Adds sorting capabitlities to tables

Adds namespace for isolated development

• Adds Flow_Scanner namespace
• Changes deploy button to deploy managed solution

Admin Rule Overrides

V2.8.0, Admin Rule Overrides
Introduces ScanRuleConfiguration__mdt Custom Metadata Type for org-wide configuration of rule severities (Error, Warning, Info, Note), custom expressions (e.g., regex for FlowName), and disabled states. Overrides load automatically on app startup, enabling centralized governance while preserving user session-only customizations.

Setup: Navigate to Setup > Custom Metadata Types > ScanRuleConfiguration > Manage Records > New.
Fields: Rule Name (e.g., FlowName), Severity, Expression (optional), Disabled (checkbox).
Example: Override FlowName regex to [A-Za-z]+_[0-9]+ for stricter naming conventions.

See the full readme documentation for an example

Flow Overview Filters

• Adds Filters for flow type and activation status
• The toolbar rows now use scoped css

Rule Configurations

This release fixes a previous bug in flow selection and enables users to view and toggle rules for flow analysis.

New Features

1. Configuration Tab - Added a new tab (Configuration) to the main Flow Scanner interface.

The MissingFaultPath rule now correctly ignores "Wait for Amount of Time" and "Wait Until Date" nodes

Upgraded to lightning-flow-scanner-core v5.9.0. This release fixes the MissingFaultPath rule to correctly ignore "Wait for Amount of Time" and "Wait Until Date" nodes, checking fault paths only for relevant nodes like "Wait for Conditions". Resolves Issue #272 (contributed by @chazwatkins). See v5.9.0 release notes for full details.