How to remove extra white space with Variable Editor in new UI Experience

[George Chen]

Hello all,

I am trying to remove the extra white space (refer to the screenshot illustration below) in the Variable Editor in an incident record in the New UI Experience.    I can see this does not happen in the old UI16 (Qubec) and also in the PDI where the Variable Editor is not included in a tab, i.e. 'Submission Details'

I've tried to remote the space by the methods below but did not help

• g_form.setDisable('[name of CONTAINER'], false);  // this unfortunately hides all or part of variables that are meant to show
• Try to implement a Client Script with DOM manipulation; // this does not locate the variable
  

• Try to manipulate the HTML component by g_form.getControl('variables.NAME OF CONTAINSER'); //this returns null
• In the new UI, the Global UI Script may be an option, but I am afraid if this approach is over-killed (plus it may be a global impact)

This white space only appears if the Variable Editor is placed within a tab (form section), but not in the main (parent) section, and therefore I was wondering if anyone has any advice on hiding the block in new UI Experience, preferably with no DOM involvement. 

Your attention and advice would be appreciated.

Thank you folks.

The white space I try to remove

The Variable set section which containers Containers

This does not happen if the Editor is added to the main section (not in a tab)

[Brad Tilton]

Hi George, 

I would open a support ticket for this issue, but you may be able to affect this by configuring the css in the theme. Here is a good place to start: Next Experience UI Resource Hub

[George Chen]

Thanks again Brad.  I have reached out to HI and got to know there is a known issue to this cosmetics issue", 

"Afer looking into our knowledge base, this appears to be a known issue reported in PRB1578164.
Please note that you can now view the current status of the Problems associated to your Case by navigating to: Self Service -- Problems.
I am now going to mark this Case as 'Pending Problem'. We will update you when the problem has been fixed or a workaround is available. "

I look forward to the problem progression in San Diego and hoping a future patch would address this.  From my company it has classified as P5 (Low priority but need addressing), and we are good for now and San Diego is anticipated to go live this weekend on 4th June. 

[George Chen]

Hi Brad,

It's really appreciated to hear your response.  Definitely I will go over the the CSS theme and walk through the new UI Resource. If necessary, I will work with my team to see if a HI ticket is needed. 

Thanks again.