Allow all system, model, and component-level parameters to be used in model annotation.

[kfry]

This is an enhancement request to support all system-level, model-level, and component-level parameters in model annotations.

There's a long list of parameters available (https://www.ptc.com/en/support/article/CS133915), but many of them can only be used in drawing annotations.  We want to be able to access these parameters in model annotations too.

And of course, this implies they are fully supported in Creo View as well.

Thanks.

[M_C_Anderson]

I was going to create a post suggesting what may or may not be the same idea.

1. What product and version are you running?
Creo Parametric 7.0.9.0

2. What is the problem?
Standard "attached note" annotations can show component parameter values when using the syntax: 

&<parameter name>:att_cmp

However, symbol annotations with variable text CANNOT access attached component parameters in this way. They can access assembly parameters, but adding the att_cmp suffix breaks the value entry.An attached note with the text entry "&FIND_NUMBER:att_cmp" does properly show the value of the FIND_NUMBER component parameter.
A symbol with the same text entry results in an error *** value display.
3. Are you using a workaround? If yes, please describe it.
The workaround is to manually enter the text instead of using parametric data.

4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
The use case here is to author MBD and show find numbers that are stored as component parameters at the assembly level in BOM balloon annotations.

5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)

This affects all designers authoring MBD and introduces an extra potential source of error.

[achirila]

Hi @kfry! Based on the information you provided and the clarifications @M_C_Anderson brought, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.