mk92,
I have been reading up on your situation and have another suggestion. To manage the connector class information, you should definitely utilize what Xuesong is talking about, building a different family_type for each part. When you are going to publish the asset, make sure that you select the proper family_type from the custom connector class file. To help manage how connectors are utilized and whether or not to pass values between try the following.
If you are familiar with iLogic, you could create different conditions that can be used to expose and suppress different sets of connectors. In this simple example, I have created a name plate that has two identically placed connectors. One of the connectors "Pass_Text" will pass the "Customer" parameter. The other connector "No_Pass_Text" will NOT pass the parameter and will only join the two. The iLogic rule simply takes the vale from the "Customer_YN" parameter and uses that to determine which connector is active. If "Customer_YN" is 0 (false), then the "Customer" value is not passed, and if 1 then it is passed. Give it a try and see if it helps, you can also see my screen shots below to help walk you through the process. I have also attached the part model, so that you can see the iLogic rule utilized as well.
The custom connector class file looks like this, so you can copy and try it out.
<?xml version="1.0" encoding="utf-8"?>
<connector _schemaversion_="1.0000">
<Customer family_type="normal" connector_name="Pass_Text" value_source="Parameter">Customer</Customer>
</connector>
Set the "Customer_YN" to 1
Use the Connector tool to join them together and notice the Text changes
Set the "Customer_YN" to 0
Use the Connect tool and notice the Text does NOT change!
Hope this helps and have a most blessed day!
Peace,
Pete
Just a guy on a couch...
Please give a kudos if helpful and mark as a solution if somehow I got it right.