Strato 2025-13
The 2025-13 release brings new features and enhancements across Strato, continuing our focus on flexibility, control, and a smoother user experience.
In Strato Document Management, the updated Trash V2 interface makes it easier to view, restore, or permanently delete files, while file replacement streamlines content updates. Authorized users can now set or remove Legal Hold directly in the People Hub, further extending authorization capabilities introduced in earlier releases. Workflows also gain more flexibility with customizable output filenames in Call External Services steps, giving you greater control over how generated files are named.
See all of these new features and enhancements documented in detail below:
New Features
Strato Document Management
Trash V2
Users can now access the Trash feature in Strato V2, with a refreshed and responsive interface.
The Trash feature retains the existing functionalities from Strato V1, enabling users to:
- View File Information about a deleted file, including its Deletion History
- Restore delete files to their original folder, or to a new folder if the original folder has been deleted
- Permanently delete files, which is only available if the current reviewer is not the same user who deleted the file
To learn more about the Trash feature, read Trash.
Legal Hold in People Hub
Authorized users can now set or remove Legal Hold on users directly in People Hub. Once a user is placed on Legal Hold, actions such as editing and deleting their files are disabled across People Hub and All Files. A lock icon and tooltip indicate when a user is under Legal Hold.
Access to the Set Legal Hold action is controlled through the Authorization Framework and is only available when the People Hub integration is enabled in the Upgrade Center. This builds on the Authorization Framework update from the 2025-06 release.
To learn about Legal Hold in People Hub, read Legal Hold.
Strato Document Generation
New Feature - File Name Customization in Call External Services Step (Alpha Version)
Workflows with the File Output setting toggled on in a Call External Services Step can now customize the Output Filename, providing more control and consistency across a Workflow. The new Output Filename input parameter allows a user to customize the file name of the file output by mapping it to Static Text, a Container or Step Export Parameter, or a Datasource Field.
Learn more about the New Feature - File Name Customization in Call External Services Output.
Enhancements
Strato Document Management
File Replacement Functionality
Users with the proper permissions and Policies applied can now replace a file with another file. Clicking the Replace file button in the Edit File side panel allows users to upload a file that will replace the existing file. When a file is replaced, only the file itself and its name (including the extension, if applicable) are changed.
This functionality is not available for batch edit functions.
This functionality is not available for batch edit functions.
Other Updates and Corrections Delivered
Strato Platform
Fields in a Catalog Sometimes Incorrectly Shows Pending Data from Another Catalog
[Component: Field Settings]
Previously, fields from the User Catalog would sometimes incorrectly fetch and display pending data from fields in the Employee Catalog instead of the User Catalog if they share identical field names in SuccessFactors. This issue was caused by the system checking for the field name without also checking for its source entity or Catalog. The system now checks for the source entity or Catalog before values are assigned to target fields.
Invalid MDF Storage Settings in Strato UAT Provisioning
[Component: Strato Platform]
The Admin Tool now saves MDF storage settings correctly by filtering out invalid field group data from previous configurations. The system now validates field groups to include only active and enabled mappings, preventing errors caused by invalid data during configuration.
Error in Generating Document
[Component: Field Settings]
An issue was identified when generating documents using a formula field with the Date Difference function and the default Show result in: Days setting. This issue occurred when a custom field in the Customer Catalog was initially created as a template parameter, then later updated to a formula field.
In these cases, the Show result in setting was not saved correctly, which caused problems during document generation. Additionally, the Show result in setting remained visible even after changing the function type, creating confusion during field setup.
This has been resolved by:
- Automatically applying Days as the default value when the Show result in setting is applicable
- Ensuring the Show result in setting only appears when the field type is Formula and the function is Date Difference
These improvements make formula field configuration and document generation more consistent and reliable.
Strato Document Management
Incorrect German Translation of Confirmation Message in Trash
[Component: Trash V1]
The German translation of the confirmation message when permanently deleting a file in Trash was incorrectly translated. The translation of the confirmation message has now been updated to be more accurate.
User Sync Job Partially using API User and Partially Logged-In User
[Component: Strato Storage]
Previously, the initial user sync processes in Storage Management correctly used the configured API user, but subsequent processes incorrectly used the logged-in user. The logic dictating this behavior has been corrected, and every API call now logs the configured API user.
Strato Document Generation
Long Text Fields Display Incorrectly in PDF
[Component: Strato Document Generation]
Sections containing fields with long text were displayed inconsistently when downloaded as PDF. Because of this, text in the downloaded PDF would wrap or shift unexpectedly. The logic has been updated so that only ESignature fields use inline‑block, while all other fields are set to inline. This ensures that long text fields now flow correctly and appear as expected in converted PDFs.
Email Attachment Lost Password Protection After Step Re-execution
[Component: Workflow]
Password-protected attachments were being sent without password protection when the Send Email step was re-executed after an error. This was due to the email being rebuilt without applying the password to the attachment. This issue has been fixed in this release.
Font Size Changes When Applying Group Protect
[Component: Strato Document Generation]
Applying Group Protect to a Section in a Document Template no longer causes unexpected font size or style changes. The system now restores the default font settings automatically, ensuring consistent formatting throughout the document.
Translations Not Displaying in Document Templates
[Component: Document Template]
An issue was identified in Document Templates where users were unable to view or edit translations for sections in languages other than English. The problem was caused by how the system handled the translation popup during template processing, which led to inconsistent behavior and prevented other languages from being displayed or edited properly.
This has been fixed by improving how the translation popup is triggered and closed, ensuring it only opens once the template is fully loaded. With this fix, users can now reliably view and edit translated sections as expected.
Workflow Executes Sub-Workflow Steps Even With Missing Required Parameters
[Component: Workflow]
Workflows now correctly prevent the execution of Sub-Workflows when required parameters are not provided. This update ensures that Workflows stop early when inputs are incomplete.
Workflows Getting Stuck During Processing
[Component: Workflow]
An issue was identified where certain Workflows would occasionally get stuck in processing and fail to complete. The root cause was that Workflows would sometimes be assigned to job runner instances that were being shut down, resulting in incomplete execution.
This has been resolved by introducing a more controlled shutdown process. Now, job runner instances will complete any active jobs before shutting down, ensuring Workflows are not interrupted and background tasks are completed as expected.