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

Question

Question

Workflow Starting Conditions are being disabled by the system without warning

asked on November 5 Show version history

The starting conditions have a checkbox that allows you to disable them by unchecking Enable event.

You can export workflows to local file which can be imported as a new workflow (similar to an on-prem system) and I was asked to create a copy of a workflow for a support case. Therefore I exported the production workflow in order to import as a new workflow (there is no copy button)

You can then import workflow files as new workflows.

However later the customer asked if we disabled a starting rule on their production workflow and we did not, but it was disabled by someone.

I found that if you import a workflow file, the workflow which the file was created from gets it's starting rules automatically disabled without anyone touching it.

When you check the starting rules, the Enable event checkbox is unchecked.

This is a huge problem as this should never disable itself unless someone asks for that to be done, many instances were missed because it was disabled for a period of time.

Submitted a support case: 248170

0 0

Replies

replied on November 5

The import of the workflow is likely the cause, rather than the export.  When you are importing the previously exported workflow, the linked or attached starting rule is being overwritten.  By default imported starting rules are set to disabled to allow for review.  During the import there is an option to discard any starting rules attached to the workflow.  This post has a much more detailed discussion as to what is likely happening.

2 0
replied on November 5

Oh I see, this caused an issue last year too. I don't see why a starting rule would be shared amongst workflows, it should be local to the workflow itself. We don't want a user modifying one workflow causing another workflow to break.

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

Sign in to reply to this post.