Scenario (Ref Case: C13859578): In a Creo session connected to a local WC 11 M030 instance with which the instantiability of OOTB type Managed Baseline has been set to "no" (because we have two instantiable sub-types that we use instead, complete with OIRs that define life cycles and a baseline folder), a user can check the box to create a baseline on checkin and Windchill will create an OOTB Managed Baseline even though the type is non-instantiable. This is not desired behavior, not just because the baseline is put in the wrong location, but because the baseline lifecycle is not correct.
Ideas, in order of preference (most to least):
Create a preference/option that allows the customer to configure their environment to allow or disallow baseline creation on check in (of course, if allowed it will need to honor sub-types and instantiability settings).
Altogether eliminate the ability to create a Managed Baseline on checkin.
Have Creo/Windchill recognize that the OOTB Managed Baseline ("parent") type is uninstantiable, look for instantiable sub-types, and prompt the user to choose one of the instantiable sub-types (if there are no instantiable sub-types, then an error stating such should be thrown to alert the user that a baseline cannot be created…even then, the perfect solution would be that the tool recognizes that there are no instantiable baseline types and remove the ability to create a baseline option altogether)
Provide instruction to the customer detailing how to customize Creo/Windchill so that the ability to create a baseline at checkin is not possible
Throw an error when an attempt is made to create an un-instantiable baseline at checkin (this is, by far, the least favored idea since errors are usually undecipherable by the common user, and likely to lead to user confusion and/or frustration...not to mention the need to start the checkin over).