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

Discussion

Discussion

Best Practices for Document Generation and Signing

posted on December 2, 2014

Hi All,

 

I am curious how other individuals approach document generation and signing using Laserfiche, Forms, and Workflow.  We are using a combination of Forms and Workflow for our process:

  • A user submits a form with gift information.
  • That form is stored in Laserfiche with the action history and the business process information.
  • A workflow is invoked on the saved gift form to generate a letter.  This letter needs to be modifiable, so its generated in Word format using a custom script block.
  • The generated/edited letter needs to be routed to various people for review and approvals.  What is the best way to do this?  Thoughts/notes:
    • We cannot (easily) use certificate signing, as we have many individuals outside our organization that will need to sign such letters.
    • Can we send the letter back out to Forms and use the approval engine?  I like how clean and simple the approval interface is in Forms.
    • Can you accomplish signing with stamps or meta-data (templates) inside Laserfiche/Workflow?  We wouldn't want users to be able to manipulate meta-data or sign for people other than themselves.

 

Curious about how other people have accomplished similar tasks.  Much Thanks!

0 0
replied on December 5, 2014

Thank you very much!  This is valuable information.

 

We ended up using the upload feature to attach the generated letter to the original form.  It's an interesting approach, but works well!

0 0
replied on December 2, 2014 Show version history

You may look at having another Forms process that is populated by querystring data. For example, we have a couple Forms processes that are kicked off by other Forms processes. Once the process hits a workflow task, that workflow does it's think, but then sends an email to an additional user. That email includes a link to the second Forms process and includes querystring data that populates fields automatically, much in the same way a database lookup works.

Once the employee submits the form, it then goes down it's own workflow path and can gather the needed signatures.

For additional information on how to use a querystring with Forms, see the help documentation under the General section and the question "Is it possible to pre-fill the fields on a form by passing in URL parameters?".

In certain situations we also have Workflow enter the needed data into a database and just pass a unique identifier in the querystring that then kicks off a database lookup in Forms.

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

Sign in to reply to this post.