Question

Workflow condition: when entry moved

Workflow

Updated July 23, 2015

asked on July 23, 2015

I've come across two situations now where I want WF to start when an entry is moved into or out of a folder, one or the other but not both:

In one case, I want to be emailed when someone tries to move an entry OUT of a folder before the process is finished;
In another case, I want WF to notice when someone drops a file INTO the wrong folder and have WF move it to the right folder.

I'm working on Case #2 right now. The WF is activating when it is supposed to and then it is activating again after workflow drops it into the controlled folder. I'm assuming it's doing that because the controlled folder is a sub-folder of the workflow's target folder. How do I get WF to not activate again after the move from the target folder to the subfolder? (I have already used "user does not equal workflow" in the Conditions window.)

I have a good alternative I can use for this Case #2, but I'm looking at this also as a training opportunity. "How would I solve this if I really needed it?"

Thx, Connie Prendergast, Flagstaff County

0 0

Replies

replied on July 23, 2015

A couple of suggestions:

Check the subscriber trace log in the admin console to make sure the rules you think should be passing for the workflow are.

Make sure the workflow user is actually named 'workflow.'

The brute force approach: create a tag called "Processing..." or such and as soon as the entry enters the workflow give it the tag. Add a starting rule "Entry : Tag (PROCESSING) is not set."

2 0

replied on July 23, 2015

Kevin:

Just checked the WF and the user is Workflow. (Dead End)
Just checked the subscriber trace - interesting! I've been waiting for an opportunity to try this out. It shows
- the move into the folder (WF1) (everything is correct)
- the other WF (WF2) set to act on new docs in the controlled folder (everything is correct)
- DOES NOT SHOW the second activity that I'm trying to stop (WF1) that runs again after the move. It does show that WF checked the rules once the doc was moved in, but the results are FALSE indicating that a WF wasn't started, however, the WF Design search window shows that it did.

I'm off on holidays now, will look into this when I'm back.

Regardless, I think I got us side tracked. I'm curious to know why it's running a second time, however, my initial reason for posting was to see if I could find a way to get a WF monitor a folder for things moving in, but not things moving out (or such type of situation). :)

I'll check back in here in two weeks. THANKS! Connie

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow condition: when entry moved

Replies

Sign in to reply to this post.