Dynamic Widget Sizing for Custom Case Item Detail Pages

mariano_froh

Dear Community,

how can we dynamically adjust Custom Widget sizes on the case item detail pages to fit the content?
In the image below, we demonstrate our problem with one Business Case data widget:

We followed the instructions on https://market.axonivy.com/market-cache/portal/portal-guide/12.0.9/doc/portal-developer-guide/customization/case-item-details.html to create custom Case Item Detail pages for different Case Categories.

Our questions

Is there a way to have the widget sizes/coordinates determined dynamically at runtime?
Are there other ways to handle this (apart from the customization in the documentation), or how could we make the widgets dynamically adapt to their content?

Background

We know that widget sizes can be set in the variable Portal.CaseDetails, however, the coordinates there are static.
In our business cases, we have stored different repo data as business case data. We want to display this data in individual widgets. However, not all data is populated at every stage of case processing; it is added gradually.
For this reason, we want certain widgets to either not appear at all if there is no associated business case data in the Business Data repository yet, or for these widgets to automatically adjust their size to fit the content.

Note: To indicate that there is no data in the repo yet, we’ve added an info box with corresponding text in the attached image. However, such solutions aren’t ideal from a UX perspective.

Thank you very much for your help and tips!

PS: We are using Axon Ivy 12

Thai Phan

Hello @mariano_froh ,

Thanks for the detailed description.
Out of the box, Portal does not support these requirements. The case detail page uses a fixed grid where each widget has static coordinates and size defined in the Portal.CaseDetails variable — there is no built-in way to resize widgets to fit their content at runtime, or to automatically hide widgets based on whether business data exists.
It's also worth noting that even if a widget could be hidden or auto-fitted, the overall page layout would still not look balanced. Because the layout is coordinate-based, when two columns with very different heights sit side by side, shrinking or hiding one widget just leaves a large empty area instead of reflowing the rest. This is a limitation of the fixed-grid model itself.
Given this, our recommendation would be to focus on improving the content and presentation inside your custom widget — for example, showing only the sections that actually have data and presenting the "no data yet" state in a more compact, friendly way. This keeps the experience clean without depending on dynamic widget sizing, which Portal does not currently provide.

Best regards

mariano_froh

Thai Phan Thank you for the reply, we'll optimize the space used within the widgets.
Best regards