Scope Difference between SNIP and SNAP for CONN and IN

Dear Wing team!

I am not sure if this is working as designed or its a kind of oversight. For me its a kind of irritating inconsistency I always need to remember when I switch between SNIP’s and SNAP’s.
The parameters "srcauto" and "altsrc" are loaded/updated for SNAP’s with the Scope Contents CONN but for SNIP’s with the Add Items Contents IN. For me its logical that those two parms are part of the CONN contents.

1. Does this work as designed?

2. Are there other Elements of the CONTENTS selection where there is a difference between SNIP’s and SNAP’s or the this the only one exception?

Thanks for reading, Michael
—————————————-
Working with SNAPs, the Contents CONN loads/updates the paramteters
"in": {
"conn": {
"grp": "LCL",
"in": 1,
"altgrp": "OFF",
"altin": 1
},
"set": {
"srcauto": true,
"altsrc": false
}
and the Contents IN loads/updates the parameters
"in": {
"set": {
"inv": false,
"trim": 10,
"bal": 0,
"dlymode": "M",
"dly": 0.100000001,
"dlyon": false
},

BUT the SNIP Add Items for CONN saves the parameters
"conn": {
"grp": "LCL",
"in": 1,
"altgrp": "OFF",
"altin": 1
}
},
and the “Add Items” for IN saves the parameters
"in": {
"set": {
"srcauto": true,
"altsrc": false,
"inv": false,
"trim": 10,
"bal": 0,
"dlymode": "M",
"dly": 0.100000001,
"dlyon": false
},
},