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

Question

Question

Can you use a Starting rule to exclude subfolders of a Path

asked on August 20, 2018

I would like to use a starting rule that excludes a Path and all of its subfolders.  I used Path "does not contain" and then entered the starting folder in the path.  This is not excluding files in the subfolder from the workflow.  Is there a way to exclude the subfolders?

1 0

Replies

replied on August 20, 2018

You can try to use the path does not match regular expression.

0 0
replied on August 20, 2018

Can you provide a screenshot of the exact rule configuration you tried? I've used "Path does not contain" for several workflows and it should work on subfolders.

0 0
replied on August 20, 2018

In further testing, I no longer think that is the issue.  I have found if I narrow the workflow to the specific subfolder I still don't get the folder excluded from Workflow.  I have used 'does not contain' before, and it worked.  I am not sure what the issue is.  I have attached the rule and the workflow.  Any help on how to trouble shoot this would be appreciated.

Workflow.JPG
Rule 'Changed'.JPG
Rule 'Created'.JPG
Workflow.JPG (65.65 KB)
0 0
replied on August 20, 2018 Show version history

If you open up the Workflow Administration console, then navigate to Monitoring > Subscribers and double-click the subscriber you can view the Subscriber Trace Log which will show you exactly how the conditions are being evaluated.

My best guess so far is that the Path value is not matching exactly.

Is "1. Team Folders" at the root level of the repository, or is it within a subfolder?

0 0
replied on August 21, 2018

Jason,

Thanks for taking a look at this.  I looked at the Subscriber trace and the starting rule, for some reason it is only showing the starting rule for the Document and user not equal to wf.  It seems to be ignoring the rest, specifically the folder to ignore.

1. Team Folders is within a subfolder, but it is selected from a drop-down which won't allow for a typo.

Any ideas on what to try next?  I have some consulting hours, so I may have them look at this on a screen share.

 

0 0
replied on August 21, 2018

You show screen shots for 2 starting rules.  Does your workflow have other starting rules that you are not showing?

In the Subscriber trace, what is the name of the rule it is evaluating?  Does the name match either of the 2 rules posted in the screen shots?

1 0
replied on August 21, 2018

Can you attach screenshots of the rule evaluation from the Subscriber Trace?

0 0
replied on August 21, 2018

I am not sure if this is what you are looking for, if not, please let me know where I would find the information you need.

1.JPG
2.JPG
3.JPG
4.JPG
5.JPG
1.JPG (46.24 KB)
2.JPG (50.81 KB)
3.JPG (47.17 KB)
4.JPG (52.78 KB)
5.JPG (53.2 KB)
0 0
replied on August 22, 2018

Oh, your starting rules section seems to be collapsed. It should look something like this:

 

Can you try mousing over the section right underneath the "Starting Rules" tab. Your cursor should change to indicate you can drag the rule evaluation section down to see the entire list of rules that get evaluated off this one event.

0 0
replied on August 21, 2018

Bert,

Those are the only starting rules - Create and Change.  I do see some other actions like Delete and Move take place.  I do not know how to view the Starting rule that is being used, I am not seeing it in the Subscriber Trace.  Do you know where I could view the name of the Starting rule?

0 0
replied on August 22, 2018

Everyone,

Thanks for your help.  I had consulting look at this and they believe this might be a SQL caching issue.  The workflow on Subscriber is running as expected, but the results are not expected.  I will re-open the issue if it still needs further investigation.

0 0
replied on August 22, 2018

For the record, the Subscriber checks for update rules every 30 seconds. So there could be up to 30 seconds delay between the time a rule is published in the Designer and the time the Subscriber starts using a new rule or the updated version of an existing one.

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

Sign in to reply to this post.