So you’re creating your blueprint and you want preview to show a text area rather than a simple text-input box. Well I’m sure you’ve noticed that there’s no way to capture this in your config - so you probably feel like you’re out of luck. BUT there’s a trick!
Preview renders the input based on the size of the sample data generated by Pega GenAI. Content greater than 30 characters gets you a text-area, less than 30 gets you the standard text input. So if your notes field indicates that this is longer-form content, you’re more likely to get a text area in preview!
This is just another example of why capturing quality notes is an important part of a high fidelity blueprint!
Maybe I just got lucky Or maybe not in my last try.
Using keywords like description, overview, and similar ones, which usually imply more room for context, could also be a good approach, if those words are allowed.
Nice trick, by the way!
This is a great tip, Anthony. It highlights a shift in mindset from trying to control and capture all specifications to providing context and allowing the AI to help you design.
Thanks for sharing these tips—this is a really interesting area to experiment with.
I tried applying the guidance to see if I could influence how a field (return reason) renders in preview (specifically switching from a text input to a text area), but I wasn’t able to get the expected behavior.
Here’s what I tested:
Entered a very detailed, lengthy field description to encourage a multi-line input
Included the keyword “description” in the field definition
Ensured the content itself would clearly warrant a text-area style input
Result (see screen shots below):
The field consistently rendered as a simple text-input box
I didn’t observe any change in behavior based on description length or wording
Or maybe not in my last try.
