Enhancement: Settings - Save Status Feature

[js3110]

Description

For Users that want to be able to leave the app and come back, we want them to be able to continue exactly where they left off.

This is a larger parent issue that will require a few steps to achieve.

Things that we want to be able to do:

• Easily save settings with version control and comments
• Easily upload the settings, with ability to select the version ( see image example)

• On upload of settings, the app has all inputs filled in as they were previously, ideally with mapping step already completed. Plots, filters, parameters, NCA setup should all be populated (and NCA already run? so results can be seen)
• Settings upload should be flexible, eg if settings are uploaded for a different study, only populate the widgets that match with the settings, and if the settings file does not contain all of the parameters, only the parts available in settings should be updated.

Additional issue is to create a template file that can be updated based on user preferences, only for the settings that are not unique to the data (eg Parameter selections per study type, default units, default rule sets)

Definition of Done

The requirements for the feature to be complete:

• Save button so that user can leave app and come back with no issues
• Ability to upload and select which version of the app to return to
• Ability to return to exact status of application as was left
• Flexible upload so settings can be applied to different data,
• Flexible so missing settings do not cause error and instead just apply defaults

[js3110]

@Shaakon35

Would need to discuss a bit more and align on what sub issues should be created in order to make this feasible.

@m-kolomanski
We have been discussing this issue before, but now it is becoming more of a priority and so we need to figure out the best way to move forward. Currently we are using rds file for settings but we received a suggestion of having a yaml file as this will be a lot easier for users to read and edit. What do you think about this?
And any suggestions on the best way to break down this issue/what needs to be handled first?

[js3110]

PR #860 is linked to this in a way, as well as #718 as the greater parent issue, which may need to be reworked depending on this discussion

[Shaakon35]

A few thoughts:

1. It would be great to be able to erase, delete a version in the pop-up version history screenshot
2. Have a "Save" button on top right, always there. It shows the pop-up version history screenshot and allows you to save at any moment the settings only (or the whole project as a zip file)

[js3110]

A few thoughts:

1. It would be great to be able to erase, delete a version in the pop-up version history screenshot
2. Have a "Save" button on top right, always there. It shows the pop-up version history screenshot and allows you to save at any moment the settings only (or the whole project as a zip file)

Do you have something in mind currently for how the pop up version history is created? Where is the data coming from? How is it stored? The user would need to write and read from the same folder every time to ensure that we can then retrieve the different versions i guess...

But then I think it is just easier for them to manually delete versions since it will be stored locally on their folder

[Shaakon35]

Do you have something in mind currently for how the pop up version history is created? Where is the data coming from? How is it stored? The user would need to write and read from the same folder every time to ensure that we can then retrieve the different versions i guess...

But then I think it is just easier for them to manually delete versions since it will be stored locally on their folder

I think the yaml file should save all the versions:
v2:
date: 13/01/2026
settings: blabla
comment: "final NCA"
v1:
date: 12/01/2026
settings: blabla
comment: "first NCA"

The pop up would show all this metadata of the settings files, and therefore will be reused over time.
Every time the zip folder is downloaded, the settings file is updated with a new version, and when this setting file is uploaded to the app (via data tab), it checks the box of the most recent version (in this case, it will use v2).

[js3110]

@Shaakon35 I added some sub issues as the first steps toward this goal, let me know if you have any comments