Release note 1.6
🎯 Business Goals of the Release
This release focuses on strengthening trust, security, and usability across the Communication Platform. The main objectives are:
- Improving the quality and correctness of Peppol documents
- Raising the platform’s security standards
- Increasing operational efficiency for both users and support teams
🚀 Feature Highlights
🔐 Automatic Logout After Inactivity (Session Timeout)
To reinforce platform security, users are now automatically logged out after a period of inactivity. This prevents sessions from staying open indefinitely.
How it works (v1):
- After 30 minutes of inactivity → user is logged out and must sign in again
- After 12 hours of continuous use → session ends even if the user is active
- When the session expires, a clear message appears and the user is redirected to the login page
🟦 Microsoft SSO for Speos Internal Users (Phase 1)
Speos employees can now sign in to the Communication Platform using their Microsoft account, while still keeping the traditional login method available. Centralizing authentication through Microsoft improves security and simplifies identity management. This is a first phase in order to validate the connexion flow for our customers
✨ Improvements
🧩 Pre‑made Variables for Email Templates
When creating email bodies, users can now select variables from a predefined list linked to the unified JSON model. Each variable is automatically mapped to the correct JSON field, reducing errors and making template creation faster and more reliable.
📱 Updated MFA SMS Template
To reduce the risk of SMS messages being flagged as spam, the MFA message now includes the company name.
New template:
“Your verification code for the communication platform is {####}. Speos Belgium”
🔎 Improved Search in Active Sendings
Typing in the search field within Dashboard → Active sendings no longer causes the input to lose focus after the first characters. Users can now search smoothly without interruptions.
🧭 More Accurate Peppol Reachability
Peppol reachability now relies only on the provided identifier (BCE/VAT). Name-based matching from the Peppol directory has been removed to avoid false matches, errors, and potential GDPR issues.
🏷️ Company Labels in Receiver Management
The receiver management table will now display the company name associated with a Peppol endpoint, making it easier to identify the correct receiver during setup and troubleshooting.
🔍 Monitoring API: RawFileLog Lookup
A new “GET by ID” endpoint allows internal teams to quickly retrieve a specific RawFileLog entry, speeding up support investigations.
📄 PDF Splitter — Custom Output Filename Pattern
Customers can now define a custom naming pattern for generated PDF files, including a sequence number. This makes it easier to organize and reconcile multiple output files.
🧾 XML Splitter — Custom Output Filename Pattern
XML split outputs can now include a sequential counter {seq} in the filename, ensuring each generated file has a unique and predictable name.
🐞 Bugfix Bucket
Large XML Processing Stability
Very large XML invoices were sometimes timing out during PDF embedding and being sent to the error queue. Processing has been optimized so large files are handled more efficiently and reliably.