You are viewing limited content. For full access, please sign in.

Question

Question

Unable to save annotations in Laserfiche 12

asked on January 19 Show version history

I have a client who is importing a large number of documents using Import Agent. Since Import Agent does not enforce show/hide rules, required fields that are conditionally displayed are not always populated during the import.

As a result, when users later attempt to add an annotation or make other updates to these documents, clicking Update does nothing—there is no visible error message explaining why the update cannot be saved. Users often continue clicking Update without understanding that the action is failing.

After reviewing the issue, we identified that the documents that fail to update are missing a required field due to the show/hide logic in the template.

Most users do not have the Details pane open when working with documents, so they never see the “Required field is empty” warning that appears there. Because of this, the cause of the issue is not clear to them.

Would it be possible to enhance the application so that if the Details pane is closed—or if the user is not viewing the Fields tab—a pop‑up notification or banner appears stating something like:

“This document cannot be updated. A required field is missing. Please open the Fields tab to complete the missing information.”

This would prevent user confusion and significantly improve clarity when required fields are blocking updates.

The users rarely have the details pane open to view the fields when making these changes.  They didn't see the message "Required field is empty" appear in the details pane. Can an update be made that if the details pane is hidden, or if the users is not on the Fields tab to have a pop-up message or banner appear stating to update or save the changes, please fill in the required field in on the document? 

 

 

 

1 0

Replies

replied on January 19

Yes, we can definitely look into that, the current behavior is suboptimal. Though, I would also suggest adding a validation workflow or something to route this documents for correction if the fields are expected to have values. 

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.