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

Question

Question

Question about editing forms already stored on repository

asked on February 10 Show version history

Hi everyone!

Well, let's suppose I have a folder in my repository with all my workers forms where their information is stored, for example, their status or address. These two fields could change; how can I edit the fields in the form that is in my repository and save those changes with a date and version? I'd like to see those changes on the form as well, not in the fields from a template

Thanks in advance

0 0

Replies

replied on February 10

I think you should step back and consider what you're trying to achieve. Forms saved to the repository are a reflection of what the submitted form was at the time when it was submitted/saved. They're not meant to be the source of truth for worker information as it changes with time. 

 

1 0
replied on February 11 Show version history

Thanks Miruna

Let me try to explain my scenario in a very simple way. Imagine I have a “worker file” in the repository for each employee (for example Worker – John Doe.pdf), and in other folders I have the real evidence documents about the worker, such as contracts, trainings, evaluations, and so on. When I open John Doe’s file in the repository, I would like to see in one place the worker ID and a short “evidence / status” summary that says something like “this worker has valid evidence: last training on X date, current contract from Y date”, even though the actual documents live in other folders.

What I would really like to achieve is a simple interface where a user enters either the worker ID or the worker’s name and the system automatically loads all related information about that worker from Laserfiche: basic profile data plus this clear evidence/status summary, and ideally links or captions that point to the underlying evidence documents if someone needs to open them.

Given these constraints, I assume this should be driven by template fields, lookups and Workflow or Process Automation, rather than by editing the original Forms submissions. My question is: what would you recommend as the best-practice pattern in Laserfiche Cloud to build this kind of “worker search plus consolidated view of worker data and related evidence”, kept up to date automatically when new evidence documents are added?

0 0
replied on February 11

Can a form be built as a landing page for this information, instead? I'm not too familiar with Cloud, but we have a process in our on premises portal where a user can enter the ID for a customer and it brings up their information. Could the same concept be used here, where instead of storing this information as PDF documents in the repository, that you instead store it to a table and use lookup rules to pull through to the form?

This is a consideration for not generating a new document each time an edit is made to their employee file, too. 

1 0
replied on February 10

Could you add some kind of annotation to the form?

0 0
replied on February 10

That’s not enough for my use case. I need the form itself to be editable again later, not just saved as a static PDF in the repository.

0 0
replied on February 10

If you turn on versioning for the documents and have metadata fields on the documents, a change to the metadata will create a new version of the document.

0 0
replied on February 10

Yes, as you can see I've  changed that value on metadata fields but the document didn't got modified as well

 

0 0
replied on February 10

You would have to probably download the PDF and edit it, then Upload and overwrite the original.  Laserfiche doesn't have the ability to edit PDF documents.

 

0 0
replied on February 10

Do you know if there is another way to save a form in any other format so it could be edited from the repository?

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

Sign in to reply to this post.