v4.19.5 - Fixed NullPointerException on Flow Logging Actions

[jongpie]

Core Unlocked Package Changes

Fixed #997 in PR #1021 - NullPointerException on Flow inputs have been occuring because Salesforce no longer showing the per-parameter include toggles

• There is recent-ish change in Salesforce Flow Builder that removed the per-input "include this parameter?" toggles (see Summer '26 release notes), which now causes Flow to always send every optional input. Boolean inputs now come across as null, instead of using the default values assigned in the Flow classes. The 3 Flow logging actions (listed below) have been updated to expect & handle null for Boolean values.
  1. FlowLogEntry
  2. FlowRecordLogEntry
  3. FlowCollectionLogEntry

Installation Info

Core Unlocked Package - no namespace

Full Changelog: v4.19.4...v4.19.5

• SF CLI: sf package install --wait 20 --security-type AdminsOnly --package 04tg7000000IzRdAAK
• Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04tg7000000IzRdAAK
• Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tg7000000IzRdAAK

---

This discussion was created from the release v4.19.5 - Fixed NullPointerException on Flow Logging Actions.