Whitespace Expansion is for Sales, not Design!

Hi! Since we’re on this, it would be great to also add room in the templata selector field in JO Programs. 

It gets wider once you select a long name, but not before. We have multiple initiatives, versions, email steps. No amount of correct name coding is helping with this. Advanced JO is already really slow to map and this is making it harder. 

This is so, so accurate. And there are so many posts about it. There are two main issues at play, and already a TON of posts around each issue (see below).

​@Padolfi, the idea I was thinking of that is MOST closely related is the bottom-most one here (having the ability to apply labels or tags). This is one of the biggest issues I’ve felt with the lack of whitespace.

The issue

Because of the limitations in our digital journey assets (both programs and templates), as well as other Horizon elements...

• One level of subfolders
• No way to categorize assets with labels/types

… we have to use longer, more descriptive names we can then search for that include all relevant information (program versions, type, audience, etc.) so we know which is which. Because these names are so long, they get truncated by the systemic abundance of white space.

A step forward

Improvements to organizational tools (folders and tags) would make it so we didn’t need to be quite as descriptive in these names, which would then let the names be visible in a smaller selector field. (As well as other benefits, such as cleaner reporting.)

Related ideas

1. Foldering

   •  

2. Organizational labels/tags

   •  

Why has this been over 2 years to fix this?

Similar vein, not being able to specify how many columns wide a field should be on any 360 attributes tab/ or within an attributes widget on Summary. 

We have this functionality with Rich Text fields, but not others. 

If I know a string is going to need 2 columns to be read properly, why not let me make it so. 
 

2 years and it’s still in “Discovery” T_T

I reported an issue related to whitespace in November 2024 concerning Calculated Fields in Dynamic JO, where it was impossible to update the value in one of my calculated fields after setting it the first time.

A fix was released last week, which solves my problem with evolving my configuration as I clone this template month after month to address the lunch and learn of the month. However, now I can't see the input type or operator at a zoom level of 100% on a 27” viewport.

We need to do away with these modals. We do not need to see the program layout in parallel to creating or updating calculated fields. Let's use the screen estate wisely so we can configure our programs, data designs, rules, etc., efficiently and comfortably.

Thanks. 

👆💯

There’s soooo much unused space (see the blue lines on ​@alizee’s screenshot). This wasn’t an issue in advanced JO (see the second and third screenshots below). You can actually see the logic and operators. What was the reason for this design choice in Horizon?

Or Cockpit views - not showing the full name of the view is unbelievable.

Another white space issue, that seems new.

My engagement models in the dropdown now show up with … because they’re too long. Meanwhile, there’s a ton of whitespace in the modal.

Please, let’s think responsive design. 

Here’s a new one for today (it seems fresh - probably an over the weekend happening):

There’s plenty of whitespace here to absorb those boxes scaling with the contents inside them. Let’s make sure they do.