Web Browser template not using $CUSTOM_FIELD*$ variables
I am having trouble getting a web browser template to use my host session $CUSTOM_FIELD2$ variable (use template host is checked). This works when using the "Website" type session, but not the "Web Browser" type session. The Web Browser just opens with nothing in the address bar. I'd like to use the web browser type session so that it can be added to the Macros\Scripts\Tools tab (also having trouble with this) and filtered by mandatory properties. The Website type session does not offer this in the template settings.
RDM Version: 2021.1.36
All Comments (7)
Hello Ryan,
Thank you for contacting us on that matter!
What type of Data Source are you using? Are you currently on the Free or the Enterprise edition of RDM?
Also, would it be possible for you to provide us screenshots of how your Web Browser template is configured? I would like to recreate this setup on our end and see if I am able to reproduce this behavior.
Best regards,
James Lafleur
I have Devolutions Server as the data source (v2021.1.19.0) and Enterprise version of RDM.
This is the working "Website" template.
Non-functional Web Browser template
In addition, when I set this template to show in the Macro\Scripts\Tools section, it does not populate an icon there.
Hello,
Thank you for your response! I would like to verify if changing the Web Browser to either Chrome or Edge and then restarting the session changes anything about the issue, or if it persists.
Best regards,
Gabriel Degrandpré
Sorry for the delay. No change using Chrome vs Edge
Hello,
Thank you for your response. I will do some tests to see if I am able to replicate the issues you describe. Once I have replicated, I will be able to open a ticket to our engineering team to report the issue to them for a fix.
Best regards,
Gabriel Degrandpré
Hello,
I wanted to let you know that I have been able to trace the source of the issue with the $CUSTOM_FIELD2$ variable when used in the Website field of your Web Browser template. It seems that, even in regular Web Browser entries, these custom field variables are not supported at the moment. I have opened a ticket to our engineering team to report this issue so it can be corrected.
We will keep you posted when we have new information to share regarding this case.
Best regards,
Gabriel Degrandpré