Quantcast
Channel: Devolutions Forum - Recent Posts
Viewing all articles
Browse latest Browse all 19717

Topic "$NAME$ in Parent entry from Sub-Connection Issue" a message from brett

$
0
0
Version: 8.0.24.0

I am not sure what the intended behavior of this setup should be, but its not the way I was hoping it would work:


&quotACME&quot (Group, type Company, Custom Variable 1: acme.local )
> &quotDatacenter&quot (Group, type Site, Custom Variable 1: dc01)
>> &quotExchange&quot (Session, Type: Host, Host field set to: $NAME$.$SITE_CUSTOM_FIELD1$.$COMPANY_CUSTOM_FIELD1$)
[ my understanding is $NAME$ should equal &quotExchange&quot by definition of the session name being &quotExchange&quot ]
>>> &quotRDP&quot (Sub-connection of &quotExchange&quot of type RDP. Computer field set to $PARENT_HOST$)

Issue: When RDP is dbl-clicked on the &quotComputer&quot field calls $PARENT_HOST$ which should use the Hostname from the Parent session holding the sub-connection.

It does appear to do this pretty well, but I get &quot$NAME$.dc01.acme.local&quot. It appears to substitute the $SITE_CUSTOM_FIELD1$ and $COMPANY_CUSTOM_FIELD1&quot but it doesn't touch $NAME$.

I don't know the order of operations for variable substitutions. For example does $PARENT_HOST$ A) go to the parent, and do the evaluation and substitution from the perspective of the parent, or does it B) just grab the string from the parent, and then do the evaluation and substitutions from the perspective of the sub-connection.

If it is A, I would expect $PARENT_HOST$ to evaluate to &quotExchange.dc01.pivcon.local&quot
If it is B, I would expect $PARENT_HOST$ to grab &quot$NAME$.$SITE_CUSTOM_FIELD1$.$COMPANY_CUSTOM_FIELD1$&quot from the parent, and then evaluate it from the perspective of the sub-connection, and thus $NAME$ should equal RDP, and it would look like &quotRDP.dc01.pivcon.local&quot.

However, I don't get A or B, I get &quot$NAME$.dc01.acme.local&quot indicating $Name$ is not substituted in a subconnection.

Please advise on how this should work. &quotA&quot is the preferred behavior as it allows templates w/ sub-connections to be built that require very little editing. Everything is based of the session name of the parent without having to edit a lot of additional fields (provided the session name using the template is the hostname of the system).

Viewing all articles
Browse latest Browse all 19717

Trending Articles