The 1.20 version is the latest release of Strato. This release contains enhancements to Strato Forms, Strato Documents, and Strato Storage, including performance and technical upgrades. More details on these enhancements are listed in the succeeding sections and individually documented in the Help Center.
For troubleshooting, see: Having an Error when trying to Log-in to Strato?
For the best performance of Strato, refer to these articles:
What are the browsers that are compatible with Strato?
How to clear your browser's cache to refresh Strato
(Click sections below to see contents.)
Enhancements and New Features
As we continue to improve Strato Forms, one of the important fields we have added is the File Upload field. This form field enables users to upload/attach a file via Document Generation. This feature can be used for form templates that require documents to be attached or routed to the user or approver (i.e. School Records, Working Visa, etc).
By adding dropdown lists to your forms, this provides an option to display a range of predefined values that users can choose from. Users just have to click an option from the list to provide an answer and proceed to the next step. For example, you can add a dropdown list where the values are linked to a SuccessFactors picklist.
Related article:Dropdown List Form Field Overview
The Preview Changes feature enables users to see a PDF preview of the document prior to generating the actual PDF document. By using this feature, users can check where the page break will occur in the PDF preview of the document.
Related article: Using Preview Changes for PDF Review
You can use the Section Protection feature to ensure that the contents and formatting of the paragraphs, rows, sections and even a group of sections that have the protection enabled are protected from getting split by a page break when generating the document.
Related article:Using and Setting Section Protection
Strato Storage has added the File Search function to enable HR administrators to search for specific documents using keywords, phrases, and multiple search criteria (folder location, document type, category, properties and so on). With the Advanced Search function, you can further refine searches by using conditions in your search criteria. Improved indexing also ensures faster return of search results. Other features for File Search include the capability to:
- Export the list of search results as a CSV file that includes individual file download links
- Download multiple files from the search results simultaneously in one ZIP file
The following fixes were deployed in the 1.20.100 Version:
In the 1.20.100 version, an issue that caused the line height in tables with the same configured height to appear uneven when in preview mode was addressed. This occurred because the tables were copied and pasted from external documents. The fix implemented to address this includes modifications to the editor. However, users are still encouraged to not copy and paste tables from external documents to avoid similar instances.
An error in workflow execution occurred when a custom field containing a formula in a step type “Call External Service” was used. This issue was addressed by ensuring that the value of the custom field was correctly retrieved and sent to the third party.
A web service error was encountered as a user was trying to retrieve data from SuccessFactors. This was resolved in the 1.20.100 version by adding a checker to verify if there was no data retrieved from SuccessFactors. If this issue occurs again, it will be displayed correctly as an error message.
An error message in the admin card appeared during server restart while executing an “Automatic Decision” step in a workflow. The fix performed to address this included a check to ensure that the step was re-executed upon server restart.
A fix was implemented to address a workflow error that resulted in customers having difficulty in configuring the email entity to send a document for signature to a user. This issue occurred because the email entity did not contain the first name and last name, which are both required when sending a document via Strato Sign. The current update ensures that Strato can now handle scenarios with first and last names as missing properties.
An issue where users were unable to complete their To-Dos or sign documents was fixed in version 1.20.100. This error was triggered by the incomplete synchronization of records from SuccessFactors, which led to incomplete information availability in Strato. The update performed includes a solution that ensures proper record synchronization.
Users encountered an error as they were trying to update the list of fields in Strato, which led to one field group not being visible. This issue occurs when certain field groups linked to similar entities in SuccessFactors were marked as ‘deleted’ in Strato. The fix included in this release ensures that these field groups are properly updated.
Another fix integrated into 1.20.100 addressed the misalignment of date formats displayed in the workflow admin and report cards, which was caused by a lack of timezone handling in the workflow report card. The fix included in this release certifies the consistency of date processing across all cards and proper handling of timezone in the report card.
The following fixes were deployed in the 1.20.200 Version:
This patch addressed a storage issue that resulted in a user's file being mistakenly directed to the incorrect folder, despite receiving a notification indicating a successful upload. Upon discovering property errors in the uploaded file, a code change was made to enable the proper preparation of file properties, regardless if errors are present during the upload process or not.
A fix was performed to address a workflow error that prevented a user from successfully uploading a document from a Request File step because of an incorrect passed value for its user ID. To resolve this, a code change that enables the sourcing of catalog ID from the workflow as fallback when the preview is null was implemented.
In a rare occurrence, a workflow issue triggered a blank display of a generated document. An internal server error occurred as it was being saved for audit purposes, which affected the server and left the process incomplete. This was handled by implementing a code change that truncated the server logs.
This update addressed a dashboard issue that prompted an incorrect order display of input parameters. The code change applied to resolve this specific issue involved setting the filter from ID to Name, ensuring the accurate display of the parameter sequence.
Export Error on Building Package with Storage Dependencies [ZD 19870]
This version includes a resolution to an export problem that was prompted by the presence of workflow storage dependencies in the package being exported. To proceed with a successful export, the storage rules were extracted and excluded from the package during the creation process.
Dropdown Values in Report Card Settings Not Populated
A user encountered a data error that resulted in the unavailability of a Report Card Settings’ catalog dropdown values upon editing. The issue was triggered because the Report Card configuration was dependent on the execution of at least one workflow. This has now been changed so that the configuration is directly taken from the workflow settings.
The following fixes were deployed in the 1.20.201 Version:
An issue occurred during a workflow execution with a condition that used a date field from SuccessFactors. Since there was no actual value in one of the date type fields used in the following condition operators: "IS", "IS BETWEEN", "IS BEFORE", or "IS AFTER", the workflow ended up with an error. In this hotfix, a validation was implemented so the condition is automatically evaluated as false if there is no actual value retrieved.
In rare cases, a workflow containing a large number of steps would result in an error message when attempting to save the template. This issue has been resolved in the hotfix by an update in configuration to enable a successful workflow execution.
The following fixes were deployed in the 1.20.300 Version:
The user experience in Template Editor was improved to ensure the consistency of template and workflow previews for different recipients.
If a property value was not configured in a Workflow that created a file, the file would not have the default property value applied to it. Consequently, the file would not appear in the File Management when the "include all files" option is selected.
An enhancement was introduced to improve the experience of the users in Strato Storage by enabling them to resize the column width of the filename to view the document name in full.
An improvement was made in Strato Storage that addresses multi-language customers' concerns about fields that are doubled in their search results.
In Strato Storage, an enhancement was implemented to ensure that Excel recognizes and displays special characters correctly when a CSV file is exported and accessed via any spreadsheet (i.e Excel).
The handling of date formats was enhanced in date fields metadata to ensure consistency across date fields in Storage Management.
An improvement was made in Strato Storage to enhance the user experience of multi-language customers that encountered duplicates in subfolders with translated names.
A security enhancement was implemented to ensure that document access is strictly based on authorization. Previously, the advanced search filter did not consider the user's authorization matrix, which could allow unauthorized access to certain documents. With the update, the search filter will always reference the authorization matrix, preventing unauthorized access to designated documents.
An issue where an email was not sent to its intended recipient was resolved through a fix that ensured correct retrieval of emails from the customer catalog; this would only happen during implementation of Strato after the import of an email template. The fix allowed the email to be successfully routed and the user’s communication be delivered as intended.
An improvement was added in our debugging tool to show the approval link. This is to be consistent when accessing the generated document from other preview windows.
During workflow execution, if an email is re-triggered manually, the sender of the email is changed to the person who restarted the workflow. To resolve this issue, a code change was made to capture the original user as the email sender.
The integration between Strato and SuccessFactors was improved to address connectivity issues among customers who do not have access to Employee Central.
The following fixes were deployed in the 1.20.400 Version:
An issue during the user synchronization between SuccessFactors and Strato has been resolved to ensure that all users are correctly saved in Strato.
To improve the search functionality for users, a storage enhancement that makes searching for files based on file descriptions accessible both via Advanced and Basic Search was implemented. For easier and more organized access, the file description is now among the available filter options in Advanced Search.
In this release, an improved Storage Search Functionality is made available for users. To optimize user experience, the Search Delay has been adjusted from 0.5 seconds to 5 seconds, allowing users to type a word in the search box without a loading interruption. Additionally, users can now manually trigger a search by clicking the Search icon or hitting the "enter" key, without having to anticipate a search delay.
A solution that addressed the misalignment of date formats as displayed in the workflow report and workflow admin cards was implemented in this patch. This fix guarantees that date processing is consistent and that timezones are handled correctly across all cards. As a result, users can expect accurate and aligned date displays throughout the workflow module.
Strato has been modified to enhance API calls for systems where the Employee Catalog is disabled, resulting in an optimized transaction between Strato and SFSF. This improvement streamlines the communication process between the two systems, leading to more efficient API calls in the absence of the Employee Catalog feature.