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

Question

Question

invoke workflow specify workflow server

asked on March 31, 2017 Show version history

Where is the specific workflow server name specified for Invoking workflows? After moving a workflow server all new Invoke workflows tasks show the workflows installed but old invoke workflow tasks that already exist in existing workflows are looking to the old server.

 

Edit: Also found there is a way to show the hidden connection profile information for each activity by adding an additional profile to the master workflow profiles list. But even though the profile is set to use the current profile the list of workflows is still looking to the old server. We had to replace every single invoke with a new activity.

0 0

Answer

SELECTED ANSWER
replied on March 31, 2017

Invoke Workflow defaults to the current server. The options for it are in the advanced properties under the gear icon in the top right corner of the Properties pane for the activity. 

Connection profiles have no impact on which WF Server is used by Invoke Workflow.

0 0
replied on April 3, 2017

Ah, good to know for next time. It seems to bind to the server name which causes all workflows with invoke processes to break if the server name changes. Also all the repository connections were using the server name and I could not find anywhere to change this in the administration console. We had to re-publish every workflow. Thanks!

0 0
replied on April 3, 2017

The WF Server name is not saved in the XML when "use current server" is selected.

Redirecting connections profiles when moving servers is discussed in the help file and in this thread.

0 0
replied on April 3, 2017

Got it. Seems like I would want to re-publish anyways though because of the timeout issue.

I wish instead of only having the option to "Copy" a profile I could instead "Use" a profile. Then I could make changes to the profile from a central location.

0 0

Replies

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

Sign in to reply to this post.