Skip to content

v3.3 — External Client App Support & In-App Setup

Choose a tag to compare

View all tags
@RubenHalman RubenHalman released this 05 Jul 10:03
· 6 commits to main since this release
v3.3.0
2588e3c

External Client App support (new default setup)

Salesforce is phasing out the creation of new Connected Apps in favor of External Client Apps. Starting with v3.3, the post-installation setup uses an External Client App for the JWT authentication that powers Flow Scanner's Tooling API access. New installs should follow the updated instructions: create a self-signed certificate, create an External Client App with the JWT Bearer Flow enabled, and save its Consumer Key in the app.

Already using a Connected App? You don't need to change anything. Flow Scanner only stores a Consumer Key, and Salesforce accepts JWT authentication from Connected Apps and External Client Apps identically. Upgrading the package does not touch your existing Connected App, certificate, or stored key — everything keeps working. If you'd like to migrate anyway, a step-by-step guide is in the installation guide.

New in-app Setup tab

Setup no longer requires the Developer Console. The app now includes a Setup tab with a live checklist (permission set, certificate, Consumer Key), a field to save the Consumer Key directly, and a Test Connection button to verify JWT authentication end to end. On first run, the app lands on this tab automatically if authentication isn't configured yet.

Beta rules (opt-in)

Beta rules from the scanner core now appear in the Configuration tab with a Beta badge. They're disabled by default and can be enabled per rule; a toolbar toggle shows or hides them in the list.

Other improvements

  • Cleaner UI: unified toolbars, tables, and footers across the Flows, Results, and Configuration tabs.
  • Clearer error messages when authentication isn't configured
  • Updated bundled scanner core with security patches.
Assets 2
Loading