Brian Schanen

Michelle Stone

Allan O'Leary

Tyler Beck

Irvin Hayes Jr.

Autodesk PLM Community Center


« Tip Tuesday! Tune In to This Best Practice Tip for Autodesk PLM 360 Configuration | Main | Greenpoint: Solving Challenges with Emerging Tech »

08/13/2015

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Brian Schanen

Hey Paul,

Thanks for the feedback, we should be clear though that this is just a default setting - changing the rule to suite your requirements is as simple as copying the default rule and removing this option.

Our expectation is that users will almost always build their own copy design rules to meet their own requirements.

We will consider changing default in the future if we find that more folks want to retain iLogic, traditionally this has been an issue as file names change impacting iLogic rule settings based on components.

-Allan

CadSetterOut

Whoa!

That is a massive gotcha. Why would you want to strip out my iLogic rules by default without telling me?

I'm not keen on this feature at all.

Luckily, Randy Mabery has provided a work around:

http://inventbetter.blogspot.co.uk/2015/07/vault-copy-design-action-rule-sets.html

Paul

Brian Schanen

Lucky I wrote this post then!

ScottMoyse

"This default rule mimics the legacy copy design behavior, so if you do not require additional capabilities default will do the job, simply updating the part number, resetting the category to that of a new file and removing iLogic."

Except, you could choose... in fact you were reminded to choose if you wanted to remove iLogic rules from the copied files or not. The new Copy Design just does it without informing the end user. Which could cause no end of trouble in some companies.

The comments to this entry are closed.