4. What is the use case for your organization? I could write in the condition file that if Lifecycle State is Released to skip the parameters so they don't change any parameters when fixing poor modeling practices on released models, such as Circular/External References. Can also use the Created On parameter to replace the Date Creation since when doing Windchill Save As actions don't update the Date Creation correctly. Can also check to make sure that our users have these models in the correct contexts within Windchill.
5. What business value would your suggestion represent for your organization? This would help with being better organized within Windchill. Users wont be able to do a Save As in Windchill and get legacy checks on parts that should be getting today's modeling standards due to the Creation Date not updating correctly. When users have modified assemblies and then accidentally run ModelCHECK on 'All Levels' causing more parts/assemblies to be in a modified state, due to parameters/relations/layers getting updated, when these models are in a released state or not checked out at all. Now because they ran ModelCHECK on 'All Levels' they would have to do an 'Erased Not Displayed' and redo their originally intended modifications.