Changes to custom variables in Enterprise Edition 2020.2.12

Implemented

Changes to custom variables in Enterprise Edition 2020.2.12

avatar

I just upgraded to 2020.2.12 and have noticed some of the custom variables I created are missing in the GUI.

I use a template to a build site location. The top is folder, which I add location in custom #1 and IP subnet in custom #2. These variables equate to site_custom_field1 and site_custom_field2. I can see these variables exist on previously created connections, but they are missing when I check the properties for the site folder.

Is there a setting I need to check to switch back to the previous configuration?

Thanks. DK

All Comments (8)

avatar

Hello,

Would it be possible for you to post screenshots of what happens now and what used to happen in the previous version? I tested on my end, and the usage of variables like $SITE_CUSTOM_FIELD1$ in an RDP that belongs to a site folder still works well, so I must be missing something to reproduce your behavior.

Regards,

Hubert Mireault

avatar

Here is a screenshot from the custom fields from an existing group of entries. Custom #1 and Custom #2 are blank with #1 being the location subnet and the #2 being the location number. However, these values are still populated in the child RDP entries.

undefined

One item I forgot to mention was that I rename the custom labels. These customs label names are part of the template. When I attempt to build a new location, the custom label names are not present.

avatar

I think your screenshot isn't showing, it might have attached wrong. Could you try posting it again?

But from what I understand you mean that the custom field's "name" isn't transferred properly when creating it from a template, right? We'll take a look at that and see if we can reproduce the issue. I don't think it's an intended change.

Regards,

Hubert Mireault

avatar

Oh my bad, I see the screenshot now. Must have been on my end 🙂 We'll take a look and see what is going on.

Regards,

Hubert Mireault

avatar

Hello,

We were able to reproduce your problem. The fix will be available in version 2020.2.13.0. Sorry this version was just released, so it will be in version 2020.2.14.0.

Regards

Jonathan Del Signore

avatar

Thanks for the update. Any idea when 2.14 will release? This is an annoying bug. :)

avatar

Hello,
We will try to do a release tomorrow with more fixes.

Regards

David Hervieux

avatar

Just wanted to report back....2020.2.14 fixed this issue. Thanks.