When building modern Pega applications with Constellation, we often face a common challenge: how to provide contextual information to business users without cluttering the interface or overcomplicating the implementation.
The natural instinct might be to reach for custom DX components, but before you embark on a high-investment path, consider this: Constellation’s design system already provides powerful, out-of-the-box ways to deliver contextual information exactly where and when your users need it.
These native features are not just easier to implement - they’re also maintained and enhanced by Pega with each release, ensuring consistency, accessibility, and compatibility across your application. Let’s explore these approaches and discover how they can transform your user experience without the overhead of custom development.
Before we begin:
- This article is written in the context of Infinity ‘25; some of these features are only available from this version.
- I am only focusing on Forms, aka what a user does inside a step or user action in Constellation (see image above). There are other features to help guide users or add context available to us Out-of-the-Box, but in this article, we are just focusing on the Form itself.
Assignment Instructions: Setting the Stage for Success
Assignment instructions appear at the top of a form, providing users with clear, concise guidance on how to complete the entire assignment. Think of them as the opening paragraph that sets expectations and provides context for everything that follows. This is your opportunity to explain the purpose of the form, outline any prerequisites, or highlight critical considerations before users begin entering data.
The beauty of assignment instructions lies in their prominence and timing. They’re the first thing users see when they open an assignment, making them ideal for high-level guidance that frames the entire interaction.
Configuration
Assignment instructions are configured on the step from Case Designer. It can be further configured in the top-level View associated with your form. You can add dynamic content using field inserts to personalize the guidance based on case data, making the instructions even more relevant and actionable.
- See Collecting information from a user for more details on configuring this in Pega.
- These are “simple” dynamic text rules, that do not support rich text (for good reason). See Dynamic text: Making Context Work for Your Users section for more details on the different types.
When to use
Use assignment instructions when you need to provide overarching guidance that applies to the entire form, such as explaining the purpose of data collection, outlining dependencies on previous steps, or setting expectations for completion time. However, as with any good communication, brevity is key. Keep your instructions short and focused to avoid overwhelming users before they’ve even started.
Multiple embedded views – multiple instructions
The above example is a simple scenario where you have a form with a single view. In Pega it is possible to reuse views, embedding multiple views in your form view. For example, a mortgage application, could have a “personal details” and “mortgage details” view embedded in it. My personal preference is using form groups to organize data (see next section), however, this does provide you with more flexibility and options in more complex data capture scenarios.
Instructions on Form Groups: Organizing Related Fields with Context
Form groups allow you to cluster related fields together, and the instruction capability for form groups takes this organization a step further by providing context for the entire group. This is particularly valuable when you have sections of a form that serve distinct purposes or require specific approaches to completion.
Instructions on form groups strike a perfect balance between the broad scope of assignment instructions and the field-specific nature of helper text. They provide context for a logical grouping of fields, helping users understand how these fields relate to each other and what they collectively accomplish.
Configuration
Form group instructions are configured in the View by accessing the gear icon on the form group itself. This is the same interface you use to configure the form group’s layout and behavior, making it a natural part of your form design workflow.
- These are standard dynamic text rules, that support rich text. See Dynamic text: Making Context Work for Your Users section for more details on the different types.
- See Configuring field groups for more details on configuring this in Pega.
When to use
Form group instructions are ideal when you have sections of your form that represent distinct concepts or require different approaches. For example, if one section collects customer information while another gathers payment details, form group instructions can help users mentally shift between these different contexts.
Required fields: Clarity that guides
When designing forms for business applications, one question inevitably arises: which fields should be required? The answer seems straightforward - you need certain data to complete your business process, so you make those fields mandatory. But here’s where things get complicated in traditional implementations: marking fields as required often becomes a balancing act between data integrity and user experience. Too many required fields and you create friction that drives abandonment. Too few and you risk incomplete data that derails downstream processing.
Configuration
Marking a field as required in Constellation couldn’t be more straightforward. During form design in App Studio, you access the common field settings for any property and simply check the “Required” option. That single configuration choice triggers a cascade of built-in behaviors that handle everything from visual indication to validation logic to error messaging - no custom rules needed; no complex configuration required.
- See Configuring common field settings for more details on configuring this in Pega.
When to use
While Constellation makes it technically easy to mark any field as required, the more important question is which fields should carry that designation. The strategic answer: requires only the minimum viable data needed to support your business process. Every additional required field you add creates friction in your user experience, so each requirement should be justified by genuine business necessity.
- Start by identifying the absolute must-have - data without which your process literally cannot proceed. These are your core required fields. Next, consider fields that are highly desirable but not strictly mandatory. Can you collect this data at a later step? Can you derive it from other sources? If so, consider making these fields optional and using helper text or contextual messages to encourage completion without enforcing a hard requirement.
- Also think about timing. Not every field required for your complete business process needs to be required at the initial form. Constellation’s case management approach allows you to collect data across multiple steps, which means you can distribute required fields throughout a workflow rather than front-loading them all in the first interaction. This progressive data collection approach improves initial completion rates while still ensuring you eventually gather all necessary information.
- Consider using dynamic requirements as well. Constellation supports conditional visibility and validation, which means you can make a field required only when certain conditions are met. For example, if a user selects “Other” from a dropdown, a text field for additional details might become required. This contextual requirement ensures you collect necessary clarification without burdening all users with a field that’s only relevant in specific scenarios. The platform’s support for when rules and conditions makes this dynamic behavior straightforward to configure without custom code.
Finally, remember that clear labels, helper text, and contextual information can often encourage field completion as effectively as a required designation. If users understand why a field matters and how it will benefit them, they’re more likely to complete it voluntarily. Required field indicators enforce completion, but thoughtful information architecture inspires it - and inspiration typically creates better quality data than enforcement.
Helper Text: Inline Guidance for Individual Fields
Helper text is your go-to solution for providing field-specific guidance without disrupting the visual flow of your form. This text appears directly beneath the field it describes, offering just-in-time information that helps users understand what’s expected without forcing them to navigate away or click additional elements.
The real power of helper text is its subtlety and immediacy. Unlike information icons that require interaction or instructions that might be forgotten by the time users reach a particular field, helper text is always visible and positioned exactly where users need it. This makes it perfect for clarifying data formats, providing examples, or explaining the impact of a particular field on downstream processing.
Configuration
You can configure helper text through the common field settings. Navigate to the gear icon on any property in your View, and you’ll find the helper text option. The text should be concise and distinct from your field label - think of it as supplementary information that enhances understanding without duplicating the label itself.
- Helper text is plain text only. It is not a dynamic text rule so is currently no reusable.
- See Configuring common field settings for more details on configuring this in Pega.
When to use
Helper text works best for explaining data format requirements (such as “MM/DD/YYYY” for dates), providing examples of acceptable values, clarifying the purpose of less obvious fields, or explaining how the field value will be used in the application.
Placeholder text: Supplemental information for Individual Fields (not recommended)
In the world of form design, providing clear, field-level guidance is essential for a smooth user experience. A feature you may encounter for this purpose is placeholder text—the light gray text that appears inside an empty form field. However, based on significant accessibility and usability findings, the official guidance from Pega Accessibility is clear: placeholder text should not be used.
While it may seem like a simple way to offer users a hint, placeholder text introduces critical issues that can lead to confusion, data entry errors, and a frustrating experience for many users.
Placeholder text is controversial for two primary reasons that directly impact users:
- The Contrast & Confusion Dilemma For text to be accessible, it must meet a minimum color contrast ratio. However, when placeholder text is dark enough to pass this standard, it appears to be a pre-filled value. Users can easily mistake this for entered text and skip the field entirely, leading to validation errors on submission and forcing them to correct a mistake they didn’t know they were making.
- Disappearing Context and Cognitive Load The moment a user clicks into a field, the placeholder text vanishes. For users with cognitive disabilities or short-term memory challenges, this is a major usability flaw. The helpful context is gone precisely when they need it most—as they are forming their answer. This forces them to rely on memory, increasing the cognitive burden of filling out the form.
Given these significant drawbacks, the Pega Accessibility team does not recommend the use of placeholder text. However, it is still available in our platform for configuration.
Configuration
You can configure placeholder text through the common field settings. Navigate to the gear icon on any property in your View, and you’ll find the placeholder text option. The text should be concise and distinct from your field label - think of it as supplementary information that enhances understanding without duplicating the label itself.
- Placeholder text is plain text only. It is not a dynamic text rule so it is currently not reusable.
- See Configuring common field settings for more details on configuring this in Pega.
Additional Information: Deep Dives Through the Information Icon
Sometimes users need more than a sentence or two of guidance - they need detailed explanations, examples, or even links to supporting documentation. This is where the additional information feature shines. Represented by an information icon next to your field, this feature provides on-demand access to rich, detailed content without cluttering your form’s visual design.
When users hover over or focus on the information icon, an overlay appears with your configurable content. This overlay can include rich text, images, links, and field inserts, making it incredibly versatile for complex scenarios. The key advantage here is that the information is available but not intrusive - users who need it can access it, while those who don’t can proceed without distraction. This feature is fully accessible with keyboard users.
Don’t miss out! In my experience, this is often missed when considering your options to improve the user experience of a form. Most likely because it is done at the Data Model level, and not something authored in a View. This is an important option to include in adding context to your forms.
Configuration
The additional information setting can be found in the advanced section when creating a new field in the Data Model Tab of a Case or Data Object. This positioning in the data model makes sense, as it allows you to define this supplementary information once and reuse it wherever the field appears in your application.
- These are standard dynamic text rules, that support rich text. See Dynamic text: Making Context Work for Your Users section for more details on the different types.
- See Adding a help icon to a field in Constellation and Adding fields to your application for more details on configuring this in Pega.
When to use
Additional information icons are perfect for complex fields that may require detailed explanation, fields where regulatory or compliance information is relevant, scenarios where you want to provide examples or best practices, or situations where you need to link to external documentation or resources.
- Cognitive load considerations: This adds an additional tab stop for a keyboard user. So, this feature should be used wisely. Like many of these features, overuse can undo a lot of the usability we are trying to achieve. In this instance, car should be taken to use when needed, or you can double the keyboard stops if on every field.
Contextual Messages: Real-Time, Condition-Based Feedback
New to Infinity '25, contextual messages represent the most dynamic of our approaches. These are warnings or informational messages that appear based on specific conditions, providing users with real-time feedback as they interact with your form. Unlike static helper text, contextual messages can respond to user input, showing or hiding based on when rules and custom logic.
This conditional nature makes contextual messages incredibly powerful for guiding users toward optimal outcomes. You can warn users about potential issues before they submit, remind them of requirements based on their selections, or provide encouragement and confirmation when they’re on the right track. The messages support dynamic text rules with field inserts, allowing you to create personalized, context-aware guidance that feels intelligent and responsive.
Configuration
Contextual messages are configured within the Form view settings for individual fields. You can define the conditions under which the message appears using when rules, and leverage dynamic text rules to create messages that incorporate case data. This combination of conditional logic and dynamic content makes contextual messages highly adaptable to your specific business requirements.
- These are standard dynamic text rules, that support rich text. See Dynamic text: Making Context Work for Your Users section for more details on the different types.
- See Adding form messages to a field for more details on configuring this in Pega.
When to use
Contextual messages excel in scenarios where field values affect requirements for other fields, when you need to warn users about potential data quality issues, in situations where field combinations create special conditions or requirements, or when you want to provide real-time validation feedback beyond simple data type checking.
Remember, this feature does not stop the user from submitting the form, it is guidance or a soft warning. If there is a validation that needs to be enforced upon submit, then that context can be configured in the next option.
Validation: Smart Data Integrity Without the Complexity
In Constellation, validation isn’t just about catching errors - it’s about guiding users toward success before errors even occur. The design system emphasizes a preventive approach that combines clear communication, intelligent field behavior, and strategic validation rules to create a smooth user experience that protects data integrity without feeling restrictive.
The foundation of this approach starts with clarity.
- Clear labels tell users what information you’re asking for. Helper text provides additional context.
- Required field indicators make expectations explicit.
- And when validation does need to step in, the system surfaces errors directly at the field and form level with specific, actionable messages that help users understand exactly what needs to be corrected.
This layered approach means that validation rules become your final safety net rather than your first line of defense. By the time a user encounters a validation error, they’ve already received multiple forms of guidance designed to prevent that error in the first place. This philosophy reduces frustration, improves completion rates, and creates a user experience that feels supportive rather than punitive.
Configuration
Constellation applications rely on the Conditions tab within the View configuration.
- These are “simple” dynamic text rules, that do not support rich text (for good reason). See Dynamic text: Making Context Work for Your Users section for more details on the different types.
- See Validating input values on a form and Validations for ensuring data integrity for more details on configuring this in Pega.
When to use
With Constellation’s validation capabilities at your disposal, following a few key principles ensures your implementation remains both effective and user-friendly.
- Lead with prevention, not correction. Use clear labels, helper text, and field formatting to guide users toward correct input before they encounter validation errors. Your validation rules should be the safety net, not the primary instruction mechanism.
- Keep error messages specific and actionable. When validation fails, tell users exactly what’s wrong and how to fix it. Instead of “Invalid input,” say “End date must be after start date.” Specific messages reduce frustration and speed resolution.
- Validate at the right time. For business logic validation, waiting until the user attempts submission often feels less intrusive. Consider the user’s mental model and validate at moments that feel natural. It is also the easiest validation to implement (in App Studio).
Dynamic text: Making Context Work for Your Users
Infinity '25 introduced Constellation support for the dynamic text rule. Amongst other benefits, it can utilise data from your case, and in some cases utilise images and rich text. The important emphasis is can, there are two flavours of dynamic text:
- Standard: Allowing rich text, properties and images
- Simple: Plain text, allowing inserting properties only.
This is an important distinction, as rich text is not appropriate for use in all contexts in the Constellation Design System. Using too much rich text - or layering multiple types of text in your interface - can create significant pitfalls that undermine the user experience you’re trying to enhance.
In Infinity '25, dynamic text can be used for the below scenarios, all allow rich text and images (standard type), except the last:
- Assignment instructions – You can use Dynamic Text Rules with field inserts to provide tailored, data-driven guidance at the form level.
- Instructions on Form Groups – These support Dynamic Text Rules, allowing you to include dynamic field references within form group guidance.
- Additional Information (Information Icon) – This explicitly allows you to define or create a Dynamic Text Rule as its source, enabling field insertions like company name or other case data within the help overlay.
- Contextual messages – These real-time feedback messages can be paired with standard Dynamic Text Rules, enabling field inserts to tailor messages based on current case data. This is a simple type that can only use plain text.
Placeholder, Helper text, and Validations do not currently support dynamic text rules.
Making the Right Choice: A Framework for Success
With powerful Out-of-the-Box options at your disposal, how do you choose the right approach? The key is to match the scope and timing of your guidance to your users’ needs. Assignment instructions work best for high-level, form-wide context. Helper text serves field-specific, always-visible needs. Form group instructions bridge the gap between these two, organizing related fields with context. Additional information icons provide deep, on-demand detail. And contextual messages deliver dynamic, condition-based feedback.
The beauty of these out-of-the-box features is that they work together seamlessly. You can use assignment instructions to set the stage, helper text to guide field-by-field completion, form group instructions to organize logical sections, additional information icons for complex fields that need extra detail, and contextual messages to provide real-time feedback based on user input. This layered approach ensures that users receive the right information at the right time, in the right format.
Moreover, these out-of-the-box UI elements are intrinsically linked. This means that when you enhance your forms, make architectural changes, or even consume your application via an SDK, there is no need to undergo lengthy refactoring. The components are designed to work in harmony, so updates in one area are seamlessly reflected across the system, ensuring a cohesive and future-proof user experience.
Perhaps most importantly, by choosing these native Constellation features over custom DX components, you’re investing in solutions that evolve with the platform. Pega continuously enhances these features with each release, improving accessibility, adding capabilities, and ensuring compatibility with future innovations. Your investment in learning and implementing these features today will continue to pay dividends as the platform advances, without requiring the ongoing maintenance and updates that custom components demand.
Additional resources
Find configuration documentation for each feature mentioned in the article above. For those wishing to explore more details on Constellation Design System and Accessibility in Pega:
Enjoyed this article?
See suggested articles from our Constellation 101 series and view all our Knowledge Shares from our User Experience Expert Circle.
Contributions
A big thanks to @Maciej_Dybal @PowerJill @lachc in contributing to this User Experience Knowledge Share.