Check-In a top-level assembly every subcomponent / assembly modification?

[CHASEONHO]

In the case of visualization, changes are not made to subcomponents.
For example, all CAD data published on the first server has version A.1, and the assembly visualizes the subcomponents of A.1.
After modifying and verifying some of the following subcomponents, each component has A.2, but the assembly still displays A.1 and does not display the latest appearance of the modified components.
You must also check in the assembly again to see the latest appearance.

Do I have to check in every time a subcomponent changes to keep all assemblies in which the component is used up to date?

Is there another good suggestion?

thanks

[BenLoosli · Accepted solution]

Visualization is a snapshot of your assembly. Change a component and you need to take a new snapshot.

Yes, the proper method is to check out the assembly that has changed components, then check it back in to get the new snapshot.

[CHASEONHO]

Thanks

as result, CAD user has not problem check a data real-time.
but normal user who use Creo view or visualization maybe doesn't check a data real-time.
cause Creo View and Visualization was must check-in when component was modified.

[BenLoosli]

Set Windchill to publish on check-in.

Every file that is checked-in gets a new image published, so everything stays up-to-date.

[jbailey]

It seems to me that you could also just republish the representation for the assembly.  If you are using "latest" it will pull the latest of everything and republish without having to check out / check in?

[BenLoosli]

A lot depends on your configuration management rules.

Publishing As Latest is the best, but it could lead to a work-in-process component being in the visualization.

We do an As Stored publish at check-in time and at promotion request submittal time. This way we get the configuration that is meant to be released and not something that may not represent the proper configuration.

[jbailey]

Correct,

But by suggesting to just check out and check in (without any suggestion of the configuration desired) - you are publishing an "as stored" configuration vs a "latest" configuration, So I am guessing this is not the case.

[TomU]

Windchill can be configured to either publish "As Stored" or "Latest".  Some companies like to publish drawings "As Stored" and publish assemblies as "Latest" but unfortunately this mixed approach is not possible without customization.  If you publish everything as "Latest", Windchill will automatically mark all upper level assemblies as out of date when a lower level component changes.  You can then configure what you want to happen next - either automatically republish each of the upper level assemblies, or just leave them marked as out of date.  Realize that automatic republishing ("Rev rolling") can quickly generate a huge number of publishing events.  One possible option is to use positioning assemblies (or extended positioning assemblies).  These can automatically load the current (latest) version of each component without having to republish each upper level assembly every time a lower level component is updated.