Currently there is no way to search for components that have this flag set, nor is there a DRC check for it. See this Idea D7878 on the Ideas site and promote it if you consider it necessary.
I am still somewhat surprised that this is considered an idea vs defective condition. Creating a function that disables parts from being compiled and no method via search, DRC or API to check is very risky.
This will force us to have to create our own soltution again.
When this flag was originally implemented it was not envisaged that users would use it in this way, rather that it would be set by the librarian and left alone.Obviously this is not the case, hence the posting of the idea.
Understood & We appreciate the responses
I cant speak for all customers, but for National Instruments; we have Engineers and technicians build hundreds of parts each year then they are submitted to Librarians for final review.
Initially I can see this flag as being very useful for things still in motion and it prevents users from forcing them to have 100% active and coming from Library (aka progressive flow)
A user can be developing a schematic and drop in place holders for x components and still route wires, and name busses and nets & supporting circuits.
While waiting for the parts to be added to the library flag them as false, continue w/ essentially a partial compile, and update local symbols w/master library parts later.
I might suggest a different strategy...
For my library teams, or person, I have every part created with a Status property. In DxDatabook, this property is easily sorted on. Parts that are still in work are listed as Unapproved, but can still have symbols placed on the schematics. When Verification is done, the .dbc file can easily be setup to check for ONLY Approved parts, so Unapproved are flagged red. This keeps the engineers moving forward.
Once the part is completed with all of its sections, then it can be changed to Approved.
As you can see I also use Obsolete, where older parts are no longer available. I have automation that keeps the users from placing anything new on a schematic that is statused at Obsolete.
Maybe this helps?
Does Mentor evaluate the potential use of every single property before adding it to the automation layer? Was "Forward to PCB" explicitly excluded for some reason? If not, it seems like an oversight/defect.