Catalog Task Variables Layout

[JoelH]

Hi, I'm new here and I have been tasked with Snow forms in my office, and I have never seen SNOW. I have done some of the online courses here on the site, but this is very new and massive for me. I have created a new request form and managed to make it look and work fine as per first attachment. I have used contain ers to open and close columns, so I got a two-column layout on the request form. However, when we get to the catalog task it looks awful, and I have tried so many things, but it won't play nice. I'm happy for it to just be one column when looking in the catalog task but I can get it to work. It seems the request side of things also drives the catalog layout. 

any ideas to try would be great and thank you for your time.

[Community Alums]

Hi Joel,

Form layout will be same on both Request and Catalog Task.
If apply single column view then it will be applied on both Requested Item and Catalog Task.

Let me know if you need further help.

Please mark the answer as Helpful/Correct if it helped you.

Best Regards,

Brahmjeet

[JoelH]

ok well i get that. But why is the layout out so badly in the catalog part vs the request? As it doesn't look good and not easy to read. Is there a way around it or to fix it? Except for going to a one column layout that the users don't want

[Community Alums]

Just remove the containers and it will work fine for you.

[Community Alums · Accepted solution]

Apologies, I guess you edited the response later, if you don't want to switch to one column view for all variables, then please use the following for first two variables:

Container Start

First variable: Who is this request for

Second variable: Location

Container End

Container Start

rest of left column variables

Container split

rest of right column variables

container end

I hope this works for you