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
{{ message }}
This repository was archived by the owner on Mar 27, 2025. It is now read-only.
The UX Roadmap (#15) suggests to have a load/save import-export profile. This will enable the user to
Since the updated import functionality is not yet implemented, the following points discussed about how save and load operation behaves and what purpose they solve for an export operation.
Save: While an export operation is done, the admin might have a very specific requirement which may arise in future as well, and for this, he would have used the query widget to accomplish it. However, if he again wishes to export the results for such a query again, there is no way the current implementation which will allow him to do so. Hence a save profile operation on export would help and it will save the queries and selections made by the user in the export form which can be used later in the future and he won't have to go through the effort of again making the same queries. He can save multiple such profiles and give a unique title to each of them.
Load: This operations simply loads the profile that the admin might have saved. An admin might have saved multiple profiles each related to a specific task. Hence a load functionality in export will enable him to select a particular profile from the list of saved export profile, the result of which will be displayed in the preview section as soon as such a profile is loaded.
The UX Roadmap (#15) suggests to have a load/save import-export profile. This will enable the user to
Since the updated import functionality is not yet implemented, the following points discussed about how save and load operation behaves and what purpose they solve for an export operation.
Save: While an export operation is done, the admin might have a very specific requirement which may arise in future as well, and for this, he would have used the query widget to accomplish it. However, if he again wishes to export the results for such a query again, there is no way the current implementation which will allow him to do so. Hence a save profile operation on export would help and it will save the queries and selections made by the user in the export form which can be used later in the future and he won't have to go through the effort of again making the same queries. He can save multiple such profiles and give a unique title to each of them.
Load: This operations simply loads the profile that the admin might have saved. An admin might have saved multiple profiles each related to a specific task. Hence a load functionality in export will enable him to select a particular profile from the list of saved export profile, the result of which will be displayed in the preview section as soon as such a profile is loaded.