Family Table Verification Status

Hello @Trebla 

There is no way to configure this kind of information in Model Tree. Consider here that in your snapshot, the active object is the generic. and - still according to your snapshots- 2 instances are verified whereas one is not. This kind of information, if it was existing:

• would therefore make sense in the Model Tree of instances, and not of generic models.
• would be therefore useless, because, most of the time, it's in the generic (and not in a given instance) that users want to know if family table is verified or not (without accessing manually >Tools >Family Table >Verify each time they would like to know this)

That said, my guess is that, in background, you would like to have this kind of information to prevent users (or at least to mitigate risks) to checkin Family Tables with Unverified instances. If my assumption is correct, related to that, upon checkin of a generic in a linked session, a conflict UI always opens informing users that instances are NOT verified. and this Conflict UI proposes Ignore this error by default. On this, consider following points:

• verify_on_save_by_default, when set to yes in config.pro, will default the choice to Verify Now, instead of Ignore this error (produced with default value no of this config option). With value yes, Verify Now will be the default, but do not prevent users to manually set back to ignore this error and checkin
• If above option is not enough (due to still manual possible action explained above), ModelCHECK can be configured also as a GateKeeper in Save mode in linked sessions, giving a clear unoverridable error upon checkin attempt of family tables with unverified instances. Just consider that an implementation of this solution is a bit complicated (just would like to let you know it's possible), and cannot be covered with simple exchanges in post. I would suggest to contact a PTC Partner if you would like to implement this kind of logic in your production environment:
  1. For the whole configuration of Model CHECK (first)
  2. And then for the configuration as Gate Keeper in linked session (as a second step)

Regards,

Serge