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

Question

Question

Using Workflow to Post a Laserfiche Form

asked on January 19, 2015 Show version history

At Empower 2015 it was mentioned that in Workflow, an HTTP Form Post activity could be used to post a form in Forms. Has anyone done this? If so, I have the following questions:

  1. Does each field need to be setup to use specific headers or is "Automatically configure headers" sufficient?
  2. What should be used for the field name? Should it be the "name" value of the field as it appears in the browser source code?
  3. Does the "Preferred Response Format" need to be something other than "HTML"?
0 0

Replies

replied on January 21, 2015

To give some additional information for this I have setup the web service to be the same web service that we use for the Forms -> Workflow setup. Is that what I should be using, or should I be setting up a different Web Service? Below is a screenshot of the current setup:

When I test with the settings above I get a 400 Error.

0 0
replied on January 21, 2015

Found out why I was receiving the 400 Error and corrected that so now I receive a 200 OK response status. So now even thought the workflow completes without errors, I am not seeing a form was actually submitted. Do I need to add custom headers or set the fields to a specific content-type in order for it to work correctly?

0 0
replied on January 29, 2015

Has anyone had any success trying this?

0 0
replied on February 10, 2015

Hi Blake - I haven't used the Form Post activity to post to a form.  I have, however, used URL encoding to fill out a form - I don't know if that helps or not, but the format is: 

 

www.something.com/formLocation#Field1=value1&Field2=Value2

 

It's not exactly what you're looking for, but I've used that to pretty good effect.

0 0
replied on February 10, 2015

Samuel, thanks for replying. That is what we are currently using. The idea with being able to post a Form is that it would then assign a task to a Forms user rather than the Forms user having the email notification get lost in their email.

0 0
replied on February 10, 2015

I would recommend against doing this at this time. 

 

I know it wont make anyone happy, I honestly would love to get this in my workflows as well, but it currently is a function that even when working, will need to be revised/revisited with each update to LF Forms. I was informed by Laserfiche that even when they use it it has been a huge hassle to update it throughout its lifespan as a form/process.

 

If you must do it, you will want to document your work to help you update it in the future when it breaks.

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

Sign in to reply to this post.