Save As Functionality to use Target Object Intialization Rule for Attributes/Security Labels

[BrianSullivan]

Hello.

Save As Currently does not use Object Initialization Rule for Attributes/Security Labels of where the Object is being created into.  A preference or Property forcing Save-As to consider Default Vaule for Security Label in its Creation Point should be added.

Use Case.

Context Public:  Saves As a CAD Component "bracket.prt" with Security Label Value PUBLIC  to "new_bracket.prt"

During Save-As Select New Context ITAR and a Subfolder.

Currently Save-As will make "new_bracket.prt" in the ITAR context but will not Read the OIR for a Default Setting.  The ITAR COntext Defaults New CAD to use value the Export Control Label Value ITAR.  The "new_bracket.prt" created with same Security Label Value as on the Source Context "bracket.prt" PUBLIC.

This requires:

1. Users to remember to go change Security Label

2. User must have Modify Security Label Access Control in 11.x to Edit Security Label (Which some customers like to limit who can change value as ITAR could be set down to Public..)

[BrianSullivan]

Alternatively or Additional.

PTC could consider a Preference that allows Security Labels value to Change on Move.  (Save As to New Context is basically a Move).  I have multiple customers who store Restricted Content in their own context..  so a Context Preference with Name of Label/Value or OIR Default Value to allow Automatic change would fit these companies Business Process.

Currently they have Purchased/Built Listeners to close the Functional Gap

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.