New in phaf 26.11.1: Windows installer, CSV, Email and REST connectors. Release notes → A Spectro Web Solutions product ↗ EN PL
phaf DATA CONNECTOR
Let's talk

Resources · Release notes

What's new in phaf.

phaf was first released in 2024. These notes list every version of the current platform, newest first, and what is planned next.

26.11.226.11.126.10 Roadmap

26.11.2 · In preparation Next

Alerts you can schedule, workspace settings and data cleanup

New

  • Error report delivery: immediately, once an hour or once a day at a time you choose. Errors are grouped by connector, and a report that fails to send is carried into the next one.
  • Send now: send the errors collected so far without waiting for the schedule.
  • Status report at the time and, for the weekly report, on the day you choose.
  • Workspace settings: email override, performance limits and users per workspace.
  • Data cleanup: remove old transactions and files by retention period, from the interface.

Improved

  • Clear SMTP error messages, for example when implicit TLS is used on a plain-text port or the server certificate is refused, with the setting to change.
  • Each connector picks up at most 20 files per run by default, so one large batch does not hold up the others.

26.11.1 · 6 November 2026 Current

Windows installer, CSV, Email and REST connectors

New

  • Windows installer (setup.exe) with a silent mode for scripted installs. It installs phaf as a Windows service and keeps the previous version for roll back. The data folder is never changed by an upgrade.
  • CSV, TSV and PSV connectors.
  • Email Send and Email Receive (IMAP) connectors.
  • REST connector to call web APIs from a flow.
  • UN/EDIFACT D00B directory, in addition to D95B and D96B.

Changed

  • The interface, logs and messages are now in English.
  • Version numbers follow the format year.month.number.

26.10 · October 2026

The current phaf platform

Flows and transfer

  • Visual flow designer with success and error paths, the connector panel and the connector catalog.
  • File, SFTP and FTP transfer on a schedule, with retries.
  • Built-in SFTP and FTP servers, so partners can send files straight to phaf.
  • Visual XML mapping and delivery to SQL Server, including stored procedures.
  • Transactions with the status, file and log of every message, and resend in one click.

EDI

  • UN/EDIFACT reading and writing with the D95B and D96B directories, generated from the official UN/EDIFACT directories.
  • Strict validation: envelope, message pairs and segment positions checked against the message schema.
  • CONTRL acknowledgements: generated, read and matched to the original message, with a deadline for pending acknowledgements.
  • Duplicate interchange detection.
  • EDI partners and documents pages, with the last activity of each partner.

Security and administration

  • Roles and permissions per workspace, two-factor sign-in, encrypted credentials and an activity log.
  • Vault: shared connections and values stored encrypted and reused across flows.
  • Single sign-on with OpenID Connect, and OAuth 2.0 client credentials for systems that call the phaf API.
  • Profiles page for the identity phaf uses with partners.

Monitoring and integration

  • Email alerts when a flow fails, and SLAs with an alert when expected volumes or times are missed.
  • Reports by period, connector and partner, with a schedule and CSV by email.
  • Flow APIs: call a flow over HTTP and get its result in the same response.

Operation

  • Runs as a Windows service, with HTTPS, an IIS application and a health check address for monitoring.

Roadmap

What is coming.

Plans, not promises: no dates are given, and the order can change with what customers need. Ask us if something matters for your project.

Next

Already planned for the coming versions.

  • Checks of the UNT segment count, the UNZ message count and the control references when phaf reads EDIFACT.
  • EDIFACT batching per transaction, the test indicator and partial acknowledgements.
  • Flow import and export, notes on the canvas, saved views and automatic layout.
  • Rename and move connectors with every reference updated.
  • Application and PDF reports, and reports shared by role.
  • SAML 2.0 sign-in, and OAuth 2.0 for the Email and REST connectors.
  • OpenAPI (Swagger) import in the REST connector, to list the endpoints and fields of an API.

New connectors — in development

Built one by one, with the same transactions, alerts and permissions. Each one moves to the release notes when it ships; the connector catalog marks them 'Coming soon' until then.

  • B2B protocols: AS2 with the AS2 partner profile, then AS3, AS4, OFTP, Peppol and OpenPGP.
  • File transfer and cloud storage: SCP, WebDAV, Amazon S3, Azure Blob, Google Cloud Storage, Google Drive, OneDrive, Dropbox, Box and SharePoint.
  • APIs and messaging: SOAP, Webhook, Kafka, AMQP, MQTT and IBM MQ.
  • ERP, commerce and CRM: Sage, Dynamics 365, NetSuite, Odoo, SAP IDoc, Shopify, WooCommerce, Stripe, Salesforce and others in the catalog.

EDI tools — in development

Built on the validation phaf already does.

  • Correction and repair: safe automatic fixes for formatting problems and a proposed repair when a stray apostrophe splits a segment, always on a corrected copy and reviewed by a person.
  • Batch verification: validate a whole folder of EDI files in one run, with a pass or fail per file and a summary.

Future: phaf server in Go

A longer-term plan, started only once the current version covers every planned function.

  • Security: a single signed executable, with no runtime or readable source code on the server and fewer third-party packages to keep up to date.
  • Performance: lower memory use and faster start-up, aimed at high-volume flows.
  • Simpler installation and upgrades, with a much smaller installer.
  • Nothing changes for customers: the same interface, the same data folder and the same flows, opened without migration.
Suggest a feature Connector catalog