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

Question

Question

Customizing the URL in task notifications

Forms
Updated November 26, 2019
asked on July 16, 2015

We have a customer who has two Forms servers, one internal and one on the DMZ.

We are running into an issue where the URL in the task notifications always points to the main Forms server (in this case, the one inside the network), so if they fill something out on the field from the external URL (i.e. https://www.customer.com/Forms/etc.), the URL they get still says:

http://internalserver/forms/etc.

Which obviously fails.

We need Forms to dynamically change the domain of the URL in task notifications depending on the domain of the forms server where the initial submission gets made. Can we add this as a feature request for version 10?

1 0

Replies

replied on July 16, 2015

It's possible to use the same hostname and have it resolve differently internally and externally.  This is especially nice if your users will sometimes access the internal server and sometimes the external server.

0 0
View 1 previous reply
replied on July 16, 2015

Can you give more details?

0 0
replied on July 16, 2015

It comes down to the fact that you probably have separate DNS systems for internal users and external users, and they can return different IP addresses for the same host name.  I don't have any hands-on experience with this, so hopefully someone who does can correct me if I'm wrong.  See e.g. http://serverfault.com/questions/327395/dns-update-to-resolve-external-address-as-internal-ip

0 0
replied on July 19, 2015 • Show version history

According to the help files, this wouldn't work.

 

Important: If external users will access Laserfiche Forms from one of several Forms Servers connected to the same database, ensure that the Primary Forms Server URL is specified on this tab. The primary Forms Server must be able to access the users for the other Forms Servers. Additionally, therouting service for each of the other Forms Servers must be able to access the primary Forms Server.

 

In order to change the URL in the task notification to "www.customer.com/Forms/etc.", we would need to designate the DMZ forms server as the Primary Forms Server, but the DNS alias would prevent the internal forms server from reaching that Primary Forms Server (it would be redirected to itself).

0 0
replied on July 14, 2017 • Show version history

In this scenario, on the DMZ Forms server, simply add a HOSTS file entry that resolves www.customer.com to the internal Primary Forms Server.  

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

Sign in to reply to this post.

Details
Related Posts
Loading ...