Do you have an issue with a specific file(s)?
Can you reproduce using one of our samples or online demos?
Are you using the WebViewer server?
Does the issue only happen on certain browsers?
Is your issue related to a front-end framework?
Is your issue related to annotations?
Please give a brief summary of your issue:
(Think of this as an email subject)
Apryse WebViewer Save File Button
Please describe your issue and provide steps to reproduce it:
(The more descriptive your answer, the faster we are able to help you)
Is there any way to monitor when the save file button is done in the save as modal? I want to overlay some custom annotations on save but then remove them when the user either save or x’s out of ht modal
Please provide a link to a minimal sample where the issue is reproducible:
Hello, I’m AiRon, an automated tech support bot While you wait for one of our customer support representatives, I can help you with your question.
To monitor when the save file button is done in the save as modal within Apryse’s WebViewer, you can attach event listeners to the modal’s lifecycle events. This way, you can trigger actions when the modal is opened or closed, such as overlaying or removing custom annotations.
Some things you can try:
Use the documentViewer events to detect when the save modal is opened and closed.
Overlay your custom annotations when the save modal opens.
Remove the custom annotations when the modal is closed, either by saving or by clicking the cancel button.
Consider using the closeElement API to handle closing actions on the save modal.
Is there a reason you need to add these annotations only when clicking save file? You can check if the save modal is open with the visibilityChanged event. When the modal is open you can import new annotations and remove them once the modal closes.
Awesome this worked! and just one other question is it possible to customize the save as modal or do I need to generate my own and can I work off a template
It would depend on the amount of customization you need.
You can customize the CSS properties by linking an external stylesheet in the constructor.
We do allow anyone to fork our UI and make changes. The issue with this is if you plan to update then you will have to make the changes again in the new version of the UI. We recommend making as little changes as possible and we cannot support these customizations on our end.
This is where the save modal is located in 11.4.
You can also create your own custom modal, but you would have to create everything from scratch.
