We have a situation where localhost was not used in the profile creation and we don't want the profiles to be bound to the server name. Is there any way to update this universally and/or set all workflows to use a specified profile so that we can manage the details of the repository connection centrally?
Question
Question
anyway to update all workflow repository connections or use a universal connection profile
Answer
Workflow does not have global profiles at this time. I wouldn't recommend using "localhost" either since if you want to move the Laserfiche Server and Workflow to separate machines in the future, you're going to have to update all profiles again. A DNS alias is probably the best way to go since you can move that from one server to another and it will be transparent to client applications.
Ok, altering the local DNS might just do it.
It is 10 to 1 more common that a server name changes because of a migration than requests to isolate the workflow server so in my experience localhost is the safest option.
The only reason this customer couldn't use localhost was because of a glitch when typing localhost into the workflow designer from a remote machine where it resolves to the workstation instead of the host that the service runs from.
In forms it always resolves to the localhost that the service runs from but in workflow it gets confused.
That's because Forms is a web application, so any name resolution that happens, happens on the server. The Designer is a Windows application, so name resolution happens locally. A Forms server in the DMZ would have the same problem since your Laserfiche Server wouldn't be on that machine.