Feature Request: Extra parameters on BoxLayout

RE: Feature Request: Extra parameters on BoxLayout

Mike Schmitt — Tue, 26 Aug 2025 15:11:55 GMT

I don't believe that has anything to do with the implementation I'm suggesting here, which is simply for the BoxLayout label to consume a!richTextItem() to dictate certain aspects of the formatting of the box label.

RE: Feature Request: Extra parameters on BoxLayout

simonj3483 — Tue, 26 Aug 2025 14:47:12 GMT

Problem with a!richTextItem() is you cannot add the heading attribute which goes against accessibility guidelines. (Something of a bee in my bonnet at the moment)

RE: Feature Request: Extra parameters on BoxLayout

Shubham Aware — Tue, 26 Aug 2025 14:36:59 GMT

I totally get your frustration with BoxLayout's limitations. We've all been there trying to match specific design requirements only to hit a wall with the preset styles! Adding custom color and margin parameters would be a game-changer, letting us finally build those pixel-perfect interfaces our clients expect without jumping through hoops with workarounds or custom plugins.

RE: Feature Request: Extra parameters on BoxLayout

Mike Schmitt — Tue, 26 Aug 2025 14:29:30 GMT

If Appian were to address this, I would hope they'd consider updating the "label" parameter to simply the "a!richTextItem()" component (with certain restrictions, like it would probably have to ignore links, linebreaks, bulleted lists, etc, but could honor formatting, style, color and size inputs). The benefit here is that it wouldn't require a whole host of novel named parameters to a!boxLayout() just to handle formatting of the label. Either way, I'm not really holding my breath.

RE: Feature Request: Extra parameters on BoxLayout

Stefan Helzle — Tue, 26 Aug 2025 13:48:40 GMT

Did you consider to build your specific box layout using nested card layouts? This way you would have more freedom.