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

Question

Question

Form Saves login screen instead of form

asked on December 4, 2015

Hi, we have an odd situation- when our Forms are saved (pdf of tiff, template or no template) it saves the login screen instead of the form! This did not used to happen, all that happened was that we added https to the forms site.

 

See attached picture at the bottom of the post. Also, the forms server error log displays a warning:

"12/4/2015 5:40:28 PM
Laserfiche template: ''.
Message: Invalid object name.
Parameter name: templateName
Stack trace:    at Laserfiche.RepositoryAccess.Template.GetInfo(String templateName, Boolean preloadFields, Session session)
   at Laserfiche.Forms.CommonUtils.LFHelper.CheckAndEditTemplateField(Session lfDb, String templateName, Dictionary`2 templateFieldInfoDictinary, Boolean checkFieldIfTemplateExisits)
 

Source: Laserfiche Routing Service"

 

Notice RepositoryAccess - in LF Configuration Page everything validates successfully.

The Save to Repository action from Process Modeler does not have any templates assigned (it used to but we tried it without). 

 

Any ideas? 

 

 

0 0

Answer

SELECTED ANSWER
replied on December 7, 2015

Hi all, we have a resolution! I will post it in case anyone else has the same issues. Our VAR, Nick Upton, figured it out.

 

Like I mentioned in my OP, we had recently switched to https (we are not in production env yet so it was alright to change settings), then realized that forms are saving to the pdf of a LF Login Screen (weird!).

 

Go to your Form Config page (https://yourURL/FormsConfig),  under Forms Server tab, make sure to check Use SSL Connection on Primary Forms Server URL. 

 

Then go to your Workflow server, open the Workflow Administration Console, localhost>External Objects>Web Services  and make sure your service URL is updated to include https.

 

If you have any workflows that are initiated in you Process Modeler, go to those workflows and on you Retrieve Form Content Action check the server settings - they should reflect the settings in your Workflow Administration Console.

 

Thank you Nick and thanks to James and Ege!

0 0
replied on December 7, 2015

You're welcome, Lidija!

1 0

Replies

replied on December 4, 2015

Does it start to work normally again if you revert back to http? That's the first thing I'd check. It would help you verify that as the cause.

0 0
replied on December 4, 2015

Ege, thanks for your reply! I will try that and report back :)

 

Thanks!

0 0
replied on December 4, 2015

Hi Lidija,

In Forms configuration, what do you have entered as the Primary Forms Server URL? Is it the same URL that you use to access Forms? If not, try making those match. (If one is http:// and the other is https:// that might explain what happened.)

With regards to the error message, are you trying to save any metadata fields at all? That kind of message can be thrown if data from a form field being saved to a Laserfiche metadata field is invalid, for example if the value is a string that is too long.

If these problems persist, you may want to contact your reseller to open a support case for further troubleshooting.

Hope this helps!

0 0
replied on December 4, 2015

James, thank you for your reply- the Primary Forms Server URL is exclusively in the format //machine/Forms. If you were to put in https: in front of it, it would tack on //https://machine/Forms

 

Sorry :( I am working with my VAR on the issue, but I figured I would ask just in case someone had a similar problem :)

 

Thanks!

 

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

Sign in to reply to this post.