Question

Workflow firing on all entries, not just those that meet conditions

Updated February 16, 2018

asked on February 14, 2018

Hello Everyone!

So I've got a folder in the repository where documents are stored until they are indexed with Metadata. Once indexed, a workflow should fire based on the entry change on the status field being set to "finished". The problem is, when this workflow fires off, it's taking all the entries that are currently in that folder that aren't indexed and don't have the status field set to "Finished". Can anyone give me any pointers?

0 0

Answer

SELECTED ANSWER

replied on February 16, 2018

Hey Everyone!

Thanks so much for all the responses! I was able to fix the error of it grabbing everything and it was in the actual workflow itself. I ended up replacing the "Find Entries" step with "Search Repository". The Search Repository allowed me to really drill down with search syntax to grab only the entries in that staging folder that had a Index Status as "Finished" and move them in the workflow and leaving those without it, in the staging folder.

0 0

Replies

replied on February 15, 2018 • Show version history

maybe add to not trigger your workflow if the user is the workflow user.

and also add the folder path to be sure the workflow will be trigged only from that folder

3 0

replied on February 14, 2018

Open the Workflow Admin Console and then go to the Monitoring - Subscribers node in the left pane. Then select the subscriber instance in the middle pane and in the right pane, select "Show Subscriber Trace Log". This will open a new window where you can see the events and what start rules they triggered. You can use this information to see what is triggered and why.

If the correct rule is being triggered and only once as it should be, then you need to look at your workflow. Is the workflow set to search for or find other entries in the same folder?

2 0

replied on February 15, 2018

Is it possible you have another workflow that is setting the status field to "Finished"? If so, (as Rene pointed out), you don't have your workflow user exempted in your rules, so another workflow setting that status would trigger this one. It's almost always a good idea to add the rule:

user does not equal [yourworkflowuser].

1 0

You are not allowed to follow up in this post.

Question

Question

Workflow firing on all entries, not just those that meet conditions

Answer

Replies

Sign in to reply to this post.