Version 156 continues to close the gap between what Flows and apps can do, and gives Appfarm AI’s planning mode a fullscreen experience.
Flows now support multireference and multienum properties, along with deep and reference data bindings — so flow logic can traverse relationships and work with multi-valued data the same way apps already do.
Appfarm AI’s planning mode has been redesigned as a fullscreen experience, giving the agent more room to work through plans.
This release also includes a bug fix for opening URLs from a PWA, plus several fixes in Flows. Most notably, action data sources are now correctly cleared when a read or return mapping with replace receives zero objects, matching the behavior of app and service data sources.
What’s New
- Support for multireference and multienum properties in Flows (#6723)
- Internal: Support deep / reference data bindings in Flows (#6808)
- Return data mapping with “replace” empties the destination data source when the returned object already exists there (#7747)
- Generate Document in Flows: PDF service error body not decoded — shows “Unknown error” instead of actual message (#7764)
- Fullscreen Appfarm AI experience for planning mode (#7767)
Bug Fixes
- Aggregate Data (and other reference/date filters) silently return empty via flow-service (#7763)
- Flow-service: request-context Flow Variables leak into sub-flows when parent is HTTP-endpoint-triggered (#7769)
- Inconsistency: A REPLACE write of zero objects leaves stale data in action data sources (#7770)
- Send Email attachment silently dropped for cardinality-ONE File Objects data source in Flows (#7771)
- Misleading and lossy flow-run logging for user-account action nodes (#7773)
- Binding a User object passed as an action param as Update/Delete target fails at runtime — should be blocked in Appfarm Create (#7774)