g_form.setDisplay( variable set name, false );

vahini
Giga Guru

Hi All , 

we are facing this issue after we upgrade our instance to London , 

before London , for variable sets . Name used to be mandatory field and title is not mandatory . 

But after London , Name is not mandatory and Title is mandatory . 

There are some onLoad client scripts in which i am setting  some variable sets to display false . 

g_form.setDisplay('variable set name' , false) ;

I exactly dont know the back end of setDisplay function , ( what it looks for , does it look for name of variable set  or Title of variable set or variable ??/ ) 

After upgrading to london , all those client script where Name is used in set display false is not working and all variable sets are now displayed . 

i removed name and used Title in that client script to set Display false and it works . 

 

what might be the reason ?? Any document on setDisplay change in london ?? how to fix all those client scripts in which variable sets are set to display false using name which wont work any more . 

 

Before london

 

find_real_file.png

 

 

After London 

 

find_real_file.png

 

 

 

3 REPLIES 3

Allen Andreas
Administrator
Administrator

Hi,

Please show full script here so we can take a look.

Thanks!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

Joel Millwood2
Kilo Guru

Hi vahini,

Please see the following Product Documentation for more information on this change: Service Catalog release notes (London). Under Changed in this release > Modifications to a variable set:

"The Name field of a variable set is deprecated and replaced with the Title field."
"The Internal name field for a variable set is auto-populated based on the Title field for all variable types except break, container split, and container end."
"The Name field for a variable is auto-populated based on the Question field for all variable types except break, container split, and container end."

Hi vahini,

How have you decided to proceed with this, have you already identified the client scripts affected and updated them accordingly? Best Regards, Joel.