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

Question

Question

Unwanted Business Process Start Rules

asked on February 11, 2014

 My Laserfiche demo server has a copy of a repository from another server, which had various business processes, workflows and start rules.

On my demo server I have several Business Processes that appear if I select 'Start Business Process' for any image.  Some of these Business Processes do not exist on this server. They have never been published on this server.  I have checked the other server and those Business Processes have been deleted or disabled.

I would appear that these Business Processes have been registered somewhere even though their workflows do not exist.

Is there any way to remove these entries from the Start Business Process list?

 

 

The "Emailed Invoices NEW" is not a workflow on this server.

 

1 0

Answer

SELECTED ANSWER
replied on February 11, 2014

The easiest way to get rid of them would be to publish a new BP with the same name and then delete it.

1 0

Replies

replied on February 11, 2014

Yes, that's expected behavior. When you publish a business process, in addition to the underlying workflow, a reference to the workflow name and the WF Server is saved in the LF repository. So if you just swap out the WFServer, you end up with these orphaned BPs.

 

When you try to publish another BP, the WF Server checks the name and the WF Server info in the repository and then warns the user if they don't match the current WF Server. This is by design to handle accidental overwriting of other business processes in the case where multiple Workflow Servers may be sharing the same repository.

1 0
replied on February 11, 2014

I have published and deleted a Business Process with the same name.  This has deleted the unwanted Business Process from the Start Business Process list.  Thank you Miruna.

Interestingly, although on the other server I had deleted the offending Business Process, when I published the workflow with the same name on my demo server, it showed an error saying that this workflow was still "owned" by the original server.

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

Sign in to reply to this post.