Copy Design Rule Set - Rule not triggered for Office files

Copy Design Rule Set - Rule not triggered for Office files

cat.ter
Participant Participant
1,144 Views
9 Replies
Message 1 of 10

Copy Design Rule Set - Rule not triggered for Office files

cat.ter
Participant
Participant

We're in progress of implementing Vault to handle our microsoft office files (Word, Excel, etc). (We're using Vault 2021 .2.2 Update.) In that regard, we see the Copy Design functionality as a useful approach to copy the office files and have them assigned to our Numbering Scheme in one operation, since the Office Vault Add-In does not assign a number from the Numbering Scheme to the office file.

 

Because of this planned use of Copy Design, I've added a couple of new Rules to our Copy Design Rule Set to clear (Set Blank) some of the properties values that are assigned to those office files. But the problem is that those rules are not run at all, so the new file retains the original property values from the original file, instead of clearing the value as expected.

See picture from the rule set below:

catter_0-1631093036522.png

 

I've tried with condition on File Extension instead of File Name, with the same result.

I've also tried with a new Rule Set with just the "Doc Rule" in it, still with the same result.

 

I can not get this to work at the moment, and it really seems like a bug to me. Or is this because the files are not from an Autodesk application? 

 

Any help is appreciated.

 

And an additional question:

Will all the rules in the Rule Set have the potentially to run, or is it only the first one from the top matching the conditions criteria? (or what is the behaviour for running Rules in the Rule Set?)

0 Likes
Accepted solutions (1)
1,145 Views
9 Replies
Replies (9)
Message 2 of 10

JamesMcMullen
Autodesk
Autodesk

I would modify your rule to "File Extension" and not "File Name".  This should allow you to do what you want to do.  

 

Regards,

 

 


James McMullen
Principal SQA Eng.
0 Likes
Message 3 of 10

cat.ter
Participant
Participant

@JamesMcMullen; I've already tried that, and it does still not trigger the rule.

Can anyone reproduce the behavior on the same build as I'm on (2021 .2.2)? Or does anyone have any other suggestions as to what can cause this, if not a bug?

0 Likes
Message 4 of 10

JamesMcMullen
Autodesk
Autodesk

I did set up an environment and it was working correctly.  I am unsure if you have both "doc" and "docx" extensions.  I would make sure the rule is based on "File Extension" for "doc".  Once that rule is done, click the "Copy..." button and create another rule for "docx".  Here is an image of my suggestion from 2021.2.2 Update:

 

WordCopyDesignRules.png

 

Regards,

 


James McMullen
Principal SQA Eng.
0 Likes
Message 5 of 10

JamesMcMullen
Autodesk
Autodesk

Another option would be to use the "OR" operand.  This would be "doc OR docx".

 

Regards,

 

 


James McMullen
Principal SQA Eng.
Message 6 of 10

cat.ter
Participant
Participant

Thanks for your suggestion @JamesMcMullen, but I've already tried this.

 

New test Rule Set:

catter_1-1631166556698.png

 

Resulting file does not have the blank property values as expected:

catter_2-1631166594775.png

 

Any suggestions to what is happening?

0 Likes
Message 7 of 10

JamesMcMullen
Autodesk
Autodesk

In looking at your picture, you are filtering on "file extension" contains "doc" and the file you are referencing has a "docx" extension.  Therefore, my last suggestion was making the filter be "file extension" contains "doc or docx".

 

Regards,

 

 


James McMullen
Principal SQA Eng.
0 Likes
Message 8 of 10

cat.ter
Participant
Participant

@JamesMcMullen

Thanks, I appreciate your help. I've tried your suggestion now, using the OR operator, and to my suprise it worked.

catter_0-1631257660389.png

 

I'm surprised it worked, since logic dictates that "docx" contains "doc", so for Word documents I assumed I would only need to check for that. So it turns out the "contains" condition actually works as a "is" condition... That is misleading in my opinion, and the "contains" shouldn't be an option if it does not work as one would expect. Or am I missing something? Could you shed some light on how the "contains" condition actually works?

 

And do all the rules in the rule set have potential to run, or how does that work? Does it stop evaluating the remaining rules once one rule have it's conditions met?

0 Likes
Message 9 of 10

JamesMcMullen
Autodesk
Autodesk
Accepted solution

Yes, I agree that "Contains" is not executing the way it should.  We are going to investigate that.  I did find another work around as well.  You could use "%" at the end.

 

For the rule set question... Once a rule that meets all the criteria and executes the operation will move to the next file. 

 

Regards,

 


James McMullen
Principal SQA Eng.
Message 10 of 10

cat.ter
Participant
Participant

Thanks for the help James.

Looking forward to the update with the issue resolved.

0 Likes