Since Data Standard has made many Vault Admins familiar with Powershell, I would love to use it in design copy workflows, too. Rule sets are not only exhausting to distribute and impossible to enforce, they are limited in what they can do, yet not that easy to set up,
A lot of users confront me with conditional logic when they hear that Copy Design works by "rules". Questions I got were:
- Can I set category (or a property) to THIS when somebody from this group copies it and to THAT when somebody else does it? (or Cat A always goes to Cat B when copied, except when John does it, or when this property is set or really any other condition you could or could not think of)
- Can I set this property to a combination of THIS and THAT for the new copy?
- I track how many variants exist for a given part. Can I update my counter on copy?
- Can I add or remove properties?
Instead of making the UI more complex and still not cover any complexity, why not use scripting? I would rather not see additional user interaction here (people often ask for setting the properties of the copies in advance), that is for the Copy Design dialog to handle, but complex categorization and "resetting" the files and properties to adhere to some sort of company standard would be a perfect use case for Powershell scripting.
In a perfect world this would be controlled server sided somehow.
