Work with Template groups

Hello everyone,

While rebuilding our vault, I came across a very interesting feature. With “Template Group,” you can quickly store individual connections in folders with the respective entries. I find this very useful, especially in a Linux environment.
However, I have now discovered a problem. Perhaps it is a bug or it is by design.

When I create a system with a finished template group, I create a folder with the hostname of the system as its name. Here, I then store $COMPUTER_NAME$.domain.tld as the host entry in the entries. Next, an RDP entry is created, which is basically inherited from everything else. Including HOST. And here it takes the entry from the parent folder, which contains “$COMPUTER_NAME$.domain.local”. This works as long as I don't use Devolutions Gateway.

When using Devolutions Gateway, $COMPUTER_NAME$.domain.tld is transmitted to the gateway. The connection is interrupted because no connection can be established. Which is understandable.

Here is the gateway log:
ERROR devolutions_gateway::listener: TCP peer failure error="tcp://$COMPUTER_NAME$.domain.tld:3389 failed: failed to lookup destination address: No such host is known. (os error 11001)" client=xx.xx.xx.xx:58896

Is there any way to fix this problem? Or is it a bug? Or have I overlooked something?
And template groups are not yet implemented in Devolutions Server. Am I correct?

Best regards
Alex