When using the "Save as" funtionallity, the newly created objects inherit the values for all custom made attrubutes.
Often these values has to be modified anyway, so the object has to be check out/modified/checked in after the "Save as"
Having the ability to modify the values in the "Save as" wizard would reduce the work of copying an object.
Or at least get the ability to reset the values.
Save As should support OIR and initialize the new objects rather than creating duplicates to make sure OIR logic is adhered to and proper values are used for custom attributes. This is especially true if the value of a custom attribute is used to control the logic of the OIR's.
but afaik as I know it is not possible to remove the value or setting it back to some default!
But yes, you should be able to overwrite it with a fix value. But only save as is not sufficient.
Revise also needs to be taken into account as well as the requirement to be able to enter other attribute values than name/number on save as.
This should help customer to edit attributes. We would like to add the english name for a changed object but this is not possible as lon as this option is not implemented.Now we have a new name for our object but the english name is wrong!
Reset a defined set of attributes during "save as" and "revise" operations is a must.
170 Votes and still no plans to implement? Did anybody from PTC saw this idea yet? Who is responsible for this? Jeffrey Zemsky or Lori Sood?
I am starting to consider how this might be implemented and I wanted to ask the following:
What should happen if attributes violate their current soft-type restrictions?
Use Case: Legacy Data
- I create a Part and related CAD Document with an integer attribute INT=10.
- Then an admin changes the soft-type constraints on INT to only allow values between 1 - 5.
What should happen when a copy the Part and/or CAD Document with INT=10?
If the UI allows you to edit the attribute during Save As, should the save as operation fail and make you set the attribute to a valid value?
Note: Today, it bipasses the constraints (since there is no way to edit the attributes) and Save As would succeed with no errors.
PRO: I can enforce the new constraints and users won't be allowed to create new Parts or CAD Documents which violate the current soft-type constraints.
CON: Save As will be more difficult, since there could be errors due to soft-type constraint violations.
Your thoughts on the matter would be very helpful.
@JenniferPierron, sounds like a perfect use case for a new preference: 'enforce constraints' (yes/no).
Jen, the way you described it is the way I would expect it to work. The Save As operation creates a "new" item and the new item should adhere to all the current constraints, not the constraints in place when the original object was created. If I wanted everything to stay the same, I would be looking for an action named Duplicate.
I also would enforce the new constraints since a save as is a new copy of something and if the requirements have changed they need to be enforced.
Requirements from my side for the Save-As. This includes not only editing attributes
An additional question: Should Save As in the "commonspace" have different rules than Save As in Workspace?
- In Commonspace, I also would have expected that the new data conform to the new soft-type restrictions (although Tom proposed a preference).
- In Workspace, since the object is not yet checked in, perhaps we could be more lenient and allow the user more time to resolve the issue before checking in. It is possible for me to prevent Check In; but allow the Save As.
As to resetting the attribute values, I think that point is clear to me; but it may not resolve all situations where the values are violating the attribute's constraints; therefore I would like to focus on what to do if they are not reset for now.
@bruegg - I think you bring up several other enhancement requests that are also important; but I think there should be other threads for these ideas. For Save As of WTDocuments, please add your third and fourth bullet to your thread here: https://community.ptc.com/t5/Windchill-Ideas/Save-as-for-WTPart-and-WTDocuments/idc-p/468560#M6260
@bruegg - For bullet #5: Numbering thematic... WTPart same number as CAD Model and CAD Drawing - If you are not happy with the enhancements in 11.0 M020, then please start another thread:
@JenniferPierron I know that there are a lot other ideas around. Some of them were even created by me.
I would like to see a complete new user story instead a of a patch to the existing wizard. Perhaps I'm a dreamer but I would like to see a wizard where the user is being helped and this includes definitly not only the attributes!
Please also have the enumerated names on your radar. If a customer using enumerated names they probably have also some legacy parts without the enumerated names and newer ones which a name was selected. For this situation you need also a preference to enforce the constaints or not.
for which version is the implementation of this idea planned?
22.214.171.124 or 12.0.0?
Because, as written in this article, there is one year of difference between the two versions.
We are currently working against a plan to make this available as part of the 126.96.36.199 release scheduled for June 2019.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.