rffrasca
Upload Progress Bar Enhancement
Hello Sir,
In our office, we have a team of 15 users currently utilizing PDFKeeper, with 4 of them having write permissions and the others having view-only access.
We have encountered an issue during the PDF upload process. While a progress bar is displayed at the bottom right of the screen, users are still able to interact with other open PDFs, delete files, or initiate new uploads before the current upload is finished. This simultaneous interaction seems to be causing performance issues, sometimes resulting in PDFKeeper slowing down or freezing, requiring us to restart the application.
I would like to request an enhancement to move the progress bar to the center of the screen, or to implement a more active blocking mechanism during the upload. This would restrict user interactions with the application until the upload is completed, preventing performance issues when multiple users are working concurrently.
Would it be possible to implement this feature in a future release? It would greatly improve the workflow and performance for teams using PDFKeeper.
Thank you for considering this request. I look forward to your feedback.
Muhammad
@Sohail2949000 - PDFKeeper is designed to allow the user to use the application while PDFs are being uploaded. This is not something I am willing to change. However, if you want to block the user from using the application while the upload is running, I can give you a couple of options:
- Option 1: Provide a user setting to run the upload as a synchronous process. However, a user setting can be modified by the user.
- Option 2: Create a policy that you will need to set in the registry on each client. This approach will be persistent and remain in effect when PDFKeeper is upgraded. The only downside to this is you will need to apply this on each client to set it up. The policy will require admin rights to set and modify so if your users only have user rights, they will not be able to change it.
I also wanted to add that the progress bar will remain and function as is, the only addition will be a wait cursor and of course, the upload will be running synchronously, blocking the UI.
@rffrasca Yes, sir, we can go with option 2. Even after mentioning it, users still don't fully understand, so we need to implement a restriction.
I hope that in future updates, there will be a way for admins to make changes without having to do it manually. I’ve recommended PDFKeeper as the DMS for our company, and we may connect remote locations to it as well.
In that case, manually managing this for all users would be difficult. Additionally, if any of the systems crash or need to be reinstalled, we’d have to go through this process again?
@Sohail2949000 - Unfortunately, if you need to reinstall the operating system, the registry key policy will need to be reapplied.
These kinds of changes are best handled with a system management product; but, if you don't use a product like that, I can brainstorm some ideas. One idea that comes to mind is moving policies into the PDFKeeper database. With this, you can set the policy in the database and PDFKeeper will set state based on that policy when it connects.
@rffrasca we will try manually if it is working well we will keep using manually.
@Sohail2949000 - In the future, if you decide that it would be best to move the policy into the database, you can open an enhancement request for it.