cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Need to share some code when posting a question or reply? Make sure to use the "Insert code sample" menu option. Learn more! X

Creo Schematics Parameters to be propagated to Windchill automatically as well.

Creo Schematics Parameters to be propagated to Windchill automatically as well.

Creo Schematics Parameters to be propagated to Windchill Schematics attributes automatically as well, to be available as attributes in Windchill and be searchable. One can create attributes for Schematics in Windchill however cannot link them to Creo Schematics parameter and set to designate.

8 Comments
klittlejohn
5-Regular Member

In my opinion this should have been implemented long time ago.

CassandraDeLeon
5-Regular Member

I agree that we should be able to designate parameters between WC and CS a long time ago.  At the very minimum have more than name and description.  I would at least want revision and version to carry into the Creo Schematic design.

dheidebrecht
7-Bedrock

Does anyone know if any progress has been made on this front with the release of Creo Schematics 7 ?

klittlejohn
5-Regular Member
Hi dheidebrecht,
No to my knowledge Creo Schematics 7, does not have this option.
Alex_Y
12-Amethyst

Hi @epoeng.,

As you might be aware, WGM was handed off to our close partner Virtual Interconnect for further development as WNCBridge.

 

Currently, we already have the ability to populate pre-defined Creo Schematics parameters with values from Windchill for the title block.
WNCBridge automatically populates a set of present parameters from Windchill attributes.

 

Mapping parameters to windchill attributes (object mapping) is on the roadmap and targeted for a release next year.

Alex_Y
12-Amethyst
Status changed to: Implementation In Progress
 
Alex_Y
12-Amethyst
Status changed to: Delivered

Delivered in latest iteration of WCbridge by VI.

olivierlp
Community Manager

Thank you @epoeng for the idea, @Alex_Y for the update and for all who commented and voted!