Validate _connectivity rule in AA

I work for a gas company, we have point feature class which has 5 subtypes with different connections like reducer has 2, three way tee has 3 and so on , I am trying to set Validate _connectivity rule for my value method in domain table, I am not sure how to use subtype under Table name. Can anyone help me?

No one answer my previous question, hopefully I will get some help for this issue..... I try to set up some rules for dynamic table, except last value rule none of them are working. here I have attached the table , not sure what mistake I am doing . I would appreciate any help.

Thanks for your response, I am trying to use Validate connectivity rule for reducers & couplings which are subtypes of Non controllable fitting feature class. Where should I enter Valency or Nodes specific number? I try to use under Value info ,Table name & Field name none of them work. Any suggestions?

Example: NoncontrollableFtg_point|11 --11 represents reducer, reducer should have 2 nodes, under which column should I enter 2 number?

How about SPLIT_INTERSECTING_FEATURES methods, why it is not breaking main, does it have to be in Geometric Network too?

My another concern is placing End cap is taking long time about 5 min, if you see highlighted portion of log file , it is querying for 713300 features, I think that's the reason the process is taking longer. Also what does index 15 represents?

I use same Intersecting _Feature method for service line, which works fine, it took 2 sec to pull main ID field from Main feature class into service line table, when you see log file it is querying for only 1 feature which it should be doing.

When using Intersecting_Edge, you only need to specify the field, not Layer|Field in the value info as it detects the edge from the geometric network.

For intersecting feature with lots of features, what scale are you editing at? The current code evaluates the map tolerance as well as the xy resolution to ensure the point finds the line. The problem with the map tolerance is as you zoom out, the search area widens. I think I revert this and only use data tolerance. Your map, you do not happen to be in Decimal Degrees, are you?

When using Intersecting_Edge, you only need to specify the field, not Layer|Field in the value info as it detects the edge from the geometric network----We don’t have geometric network built in so I am not sure whether method works for us.

For intersecting feature with lots of features, what scale are you editing at? It depends on Technician; we don’t have standard scale value.

The current code evaluates the map tolerance as well as the xy resolution to ensure the point finds the line. The problem with the map tolerance is as you zoom out, the search area widens, I think I revert this and only use data tolerance —I noticed that too , now adding feature is not taking too long.

Your map, you do not happen to be in Decimal Degrees, are you?----No we don’t.

Also expose a new option in the aa.config to clear the last value on stop editing like you requested.--- It works now, whenever I stop the edits it erases my values. This is what we are looking for.