Question

Using 2 different versions of Forms in parallel

Version 11

Updated March 13, 2023

asked on March 8, 2023

Hi all,

We are currently on forms 11.2 at the moment, and have alot of existing processes with javascript functionality. I would love to use the new features in 11.3 however upgraded our current process is not an option at the moment.

As I understand it there are 2 instances of forms, one which has a public portal. We have the instance without the public portal at the moment updated to 11.3 as a test environment. I was wondering if there were any issues with running two different versions of forms concurrently and how they would affect the shared REPO and WORKFLOW.

Thanks!

0 0

Answer

SELECTED ANSWER

replied on March 8, 2023

Hi Shan,

If the two Forms servers are not sharing SAME Forms database, then it's ok, it does not matter if multiple Forms server with different versions connect to same Laserfiche Server or Workflow server, as long as they have different Forms database. but if the Forms servers share same database, then the answer is definitely no.

0 0

replied on March 9, 2023

Thanks Zhiyong,

Thats great news I think that is our setup. What is the easiest way to confirm this?

0 0

replied on March 9, 2023

If you want to confirm the forms server are using same database or different ones, you can go to the forms configuration site and see what is the database name there.

1 0

replied on March 9, 2023

Great thanks, I'll look for that.

Much appreciated1

0 0

Replies

replied on March 13, 2023

I know the question about the databases and different versions is already answered.

But I wanted to add on to point out that upgrading from 11 Update 2 to 11 Update 3 shouldn't impact any of your processes with custom Javascript. They made some big changes to the new designer, but nothing has been removed or disabled in the classic designer that should prohibit you from continuing to utilize those processes as you already were.

1 0

replied on March 13, 2023

Thanks very much Matthew, I didn't think of that, yes you are right, the old forms would stay on the classic form. For some reason I read somewhere that Javascript would need to be re-written, but if the classic designer is untouched then yes it should work.

Thanks for that!

0 0

replied on March 13, 2023

The confusion could be because with Version 11 Update 3, Javascript functionality was added to the new designer. But because of how different the new designer is from the classic designer, most examples of Javascript and CSS posted to the Answers site over the years won't work in the new designer. And in fact, the new designer runs the custom code within a sandboxed iFrame, so you can't directly access form components, fields, the window, or the document - so a lot of the custom code that has been discussed over the years can't be implemented at all on the new designer.

It's a bit of a trade-off. The new designer has some great new options for field rules and improvements for how the form is laid out, but is limited to the custom Javascript that has been implemented as part of the LFForm object, so if you need any more complex or specialized code, you need to stick with the classic designer.

But the Javascript you have in place already from the classic designer shouldn't be impacted by the upgrade unless you are trying to switch specific forms over to the new designer (which doesn't happen automatically or anything like that).

Good luck!

1 0

replied on March 13, 2023

Thanks Matthew thats another misconception I had, I was assuming 11.3 would give me full Javascript capabilities, thanks for the heads up. I do like the new rules and improvements as well so it's still a big bonus.

2 0

You are not allowed to follow up in this post.

Question

Question

Using 2 different versions of Forms in parallel

Answer

Replies

Sign in to reply to this post.