Variables in the catalog item are not displaying as per order in two column layout

[Srihari_Avuluri]

Hi All,

I have a requirement to display variables on the specific field selection

I created a sampla catalog to explain the issue.

I have three variables in between container start and end.Those are test1, test 2 and test 3 with respective orders 100,200 and 300.And an add on is all the variables are hidden on variable level intially and im trying to display based on "test onchange" field selection.

Attached screenshot of variables for item below:

When test on change field is selected to "test Ref" my requirement is to hide test 1 and test 3 and in a two colum layout

Below is the client script i added :

When tried the catalog item the form looks like this .Arrow position is my expectation for test 2 variable as that space is not occupied by any other variable.

Note:1) I haven't used container split as i don't have any issues whether variables displayed on the left or right as long as they are in sequence.And also i have too many variables for other selections so i really can mention what should go left and right.

2) if i use single column layout those are displaying in order but i have around 20 variables for few selections for that reason i need two column layout to avoid large catalog form.

Any leads on this is highly appreciated.Thanks in advance.

Srihari Avuluri

[Voona Rohila]

Hi @Srihari_Avuluri 

As per your variables the test1,test2,test3 are in continuous order but as per your catalog view the variables are placed in split.

Please share proper screenshots again.

[Srihari_Avuluri]

Hi Rohila,

I used container start and end only with two column alternating sides.

Not used the container split , attached the variables screenshot in the original question itself.

Thanks,

Srihari

[Srihari_Avuluri]

@Chuck Tomasi @Mark Roethof @Pradeep Sharma 

@Ankur Bawiskar @Prashanth Kuma3 @Dhruv Gupta 

would love to hear your thoughts on this matter! Thanks in advance

[Srihari_Avuluri · Accepted solution]

Got in touch Servicenow HI Support and it was a global issue.

Problem 'PRB1677196' created for this for the fixture in upcoming releases