[FALL] Fix File Persistence on Page Reload for Single and Multiple File Uploads #1759
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue & Reproduction Steps
This PR addresses two key issues related to file persistence within File Upload components in Screen Builder:
The solution introduces a
fetchFile
function, which retrieves uploaded files by their ID on component mount ifthis.value
exists, providing consistent file persistence across reloads.Changes:
fetchFile
logic to retrieve uploaded files by ID whenthis.value
is present during component mount.How to Test:
package-versions
installed to utilize the Autosave functionality- Single File Upload
- Multiple File Upload
Note: Due to unsupported autosave functionality, file persistence will not work in Web Entry and Collection screens.
Related Tickets & Packages
- FOUR-19799
- FOUR-14168
Code Review Checklist