You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When viewing the Detail-Page of a Workflow-Item the user can see a list of documents that was attached to the Item.
If this document is, for whatever reason, not available anymore the user still sees a list entry for that missing Item without a name. Also when the user tries to click the download button, a 404 is returned from the Api and the user will get no document. This is confusing for the user
How to reproduce 🕹
Two possibilities
Try to view and download documents that were uploaded with version 1.19.0
Try to view and download documents that were deleted from storage service
How to Fix
Break up workflowitem information in subproject viewDetail into
workflowItem - viewSummary - Will represent a list item in the subproject Detail
workflowItem - viewDetail - Will contain Document
Workflowitem.viewDetail will mark unavailable Documents so the Frontend will be able to show the user that a document is corrupt / not available for download.
Your Environment 🌎
Tech
Version
Frontend
v1.24.0
API
v1.24.0
The text was updated successfully, but these errors were encountered:
Description 😯
When viewing the Detail-Page of a Workflow-Item the user can see a list of documents that was attached to the Item.
If this document is, for whatever reason, not available anymore the user still sees a list entry for that missing Item without a name. Also when the user tries to click the download button, a 404 is returned from the Api and the user will get no document. This is confusing for the user
How to reproduce 🕹
Two possibilities
How to Fix
Break up workflowitem information in subproject viewDetail into
Workflowitem.viewDetail will mark unavailable Documents so the Frontend will be able to show the user that a document is corrupt / not available for download.
Your Environment 🌎
The text was updated successfully, but these errors were encountered: