What is a one sentence summary of your feature request?
The Webviewer should support pagination to allow browsing through all records beyond the current 500-entry limit without relying on the search function.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
When password records are exported as a Webviewer file, the number of records displayed on the first page can be configured during export. The system enforces a limit of a maximum of 500 records. If more than 500 records are exported, the Webviewer only displays the first 500 records.
To access a record that is not among the first 500, it can only be found by entering a matching keyword in the search field. This means that users must know exactly what they are looking for.
This behavior is identical when a system job is configured for the automatic export of an emergency Webviewer. As a result, the emergency function is of very limited use if the corresponding Webviewer contains more than 500 records (in our case, more than 8,000 records).
If the original Password Secure database fails and access to data from the emergency Webviewer is required (e.g., because it contains important credentials needed to rebuild systems after a total loss), it is impossible to get a complete overview of the Webviewer’s content. Only the first 500 records are displayed; any additional records can only be accessed via search.
If the correct keywords are not known, users may not be able to find critical credentials, even though they are present in the Webviewer.
The Webviewer’s behavior should therefore be urgently adjusted.
The current limit of 500 entries per page is acceptable to prevent excessive memory usage in the browser. However, there must be a form of pagination, so that:
Page 1 displays records 1–500 (depending on the setting),
Page 2 displays records 501–1000,
and so on.
Regardless of the specific design, it must be possible to browse or navigate through all records in the Webviewer without having to rely on the search function.
How do you currently solve the challenges you have by not having this feature?
There is currently no practical workaround available for this issue when dealing with more than 500 records in the Webviewer file.