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

Question

Question

Search repository from Forms

asked on March 8, 2015

We have certain files within the LF repository that need to be linked to newly submitted files uploaded via Forms.  I would like to have the form submitter be able to do a search, from the form, for the file to be linked so there is a validation by the submitter.  Workflow will do the work in the back end.

I am looking to have an end user fill out a text field in forms, then have the info entered used to search the repository and return file name results.  This would be used to validate the file exists in the repository before submitting the form. 

Is this possible?

Thanks

0 0

Replies

replied on March 9, 2015

Hey David,

Every document in the repository has a unique Entry ID. You could use this to identify the correct document:

  1. The user finds the correct document
  2. The user reads the Entry ID from the properties
  3. The user fills the Entry ID into the Form field
  4. The Workflow finds the entry using an Entry ID search
    1. Syntax = {LF:ID=%(Forms_EntryIDValue)}

 

From here you can pull the entries name.

 

 

 

1 0
replied on March 9, 2015

Thanks for the reply Nathan, we are more looking along the lines of a submitter enters the name of the file (they should know this as these files are named via WF earlier) in a text field in Forms then that name is searched for in the LF repository to allow for the submitter to confirm.

0 0
replied on March 9, 2015

Maybe the new Laserfiche Connector could be used for this? We've done something similar to what you're trying to do, but had to make it a two-step process.

The first step is entering the information and submitting the form. The information gets submitted to Laserfiche with the form's instance ID, triggering a workflow. Workflow does a search for the document and puts the form's instance ID on it.

In the second step, the user opens the form and a database lookup is done (via a stored procedure) to get the document id associated with the instance id.

It's kind of a roundabout way of getting it, but it seemed to work for our client.

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

Sign in to reply to this post.