Prostream update - week 9, 2024

Release #77

Issue resolved: Document name is missing

When sharing documents, the name of the document was not shown in the download screen due to a bug. This has been resolved: you will see the document files normally again.

Issue resolved: Snagstream integration

Due to a bug, the connection to Snagstream was not always made properly. The connection was not shown or you received an error message when connecting Prostream and Snagstream. This has been resolved and the integration is working normally again.

Issue resolved: Stamping of documents

When uploading a new version of a file, the preview was not always immediately available, making it impossible to stamp a QR code. This caused error messages and files were not stamped correctly. This has now been resolved, you can stamp QR codes normally again.

Issue resolved: Approval of files

When you tried to approve a file, you received an error message. The file was not approved correctly. This has been resolved - approving files works as expected again.

Issue resolved: Preview of Excel, PowerPoint and Word files

When you open the side panel of an Excel, PowerPoint, or Word file, you should normally see a preview of the file. Due to a bug this was temporarily not the case.

Issue resolved: Files without file extension

When downloading an entire folder from Prostream in a ZIP file, you received an error message if no file extension (such as .pdf) was appended to the file name. This prevented the file from being opened. This has been resolved.

Issue resolved: Attachments to non-Prostream users

When sending a message to someone who is not an active user in Prostream, the log of the files attached to the message did not show this user. This made it unclear to whom the file had been sent. That has now been resolved; you will see the recipient's email address in the log of the file.

Issue resolved: Metadata of new files

When adding new files to a folder with metadata, you must first add metadata before you can upload the file. This was temporarily not the case due to a bug, but that has now been resolved.