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

Question

Question

Business Process Already Owned by Other Workflow Server

asked on September 14

I am making a change to one of the workflows in our TEST environment, and I get a warning on publish that the workflow is already "owned" by our PROD workflow server. I've never seen this before and am not sure what it means, but I don't want to do anything that will break a production workflow. Anybody know what's going on? Should I just press 'No' on the overwrite question? The PROD environment does have a workflow with the same name, since we promote from TEST to PROD.

A couple of screenshots. First, the web services in our TEST environment as seen in the WF Admin Console, server name ending in T007. The second is of the error message that also shows that I'm connected to this T007 TEST workflow server, not the P008 PROD server.

 

0 0

Answer

SELECTED ANSWER
replied on September 14

Laserfiche business processes set their WF Server location into the repository as part of publishing ("When the user want to starts BP X, call this WF Server for the actual work").

If your test environment has its own copy of the repository and Workflow Server, you can overwrite it without affecting the Prod repository. If the test environment is a second WF Server hooked into the Prod repository, you would be effectively taking over that business process for all users.

3 0

Replies

replied on September 14

Hey Pieter,

Any chance that workflow/BP was down-promoted  from Prod to Test?

A review of prior support cases seems to indicate that message pops up when the workflow originated from a different server.

I'll defer to @████████ for a more authoritative answer on whether it's safe to click Yes or not.

0 0
replied on September 14

Can't say for sure but it's highly likely this is what happened. I'll wait to hear from Miruna about how we should proceed.

0 0
SELECTED ANSWER
replied on September 14

Laserfiche business processes set their WF Server location into the repository as part of publishing ("When the user want to starts BP X, call this WF Server for the actual work").

If your test environment has its own copy of the repository and Workflow Server, you can overwrite it without affecting the Prod repository. If the test environment is a second WF Server hooked into the Prod repository, you would be effectively taking over that business process for all users.

3 0
replied on September 14

Thanks, Miruna. Yes, we have a completely separate set of servers for TEST. This makes it sound like as it stands currently, starting from our TEST environment would actually launch the PROD workflow. So definitely want to get those overwritten.

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

Sign in to reply to this post.