AI Assistant prompts and guidance
The AI Assistant in Pega Blueprint™, available on the left side of the design screens and the Blueprint Preview, helps you create and refine the application design. Describe the intended change in a supported language, and the AI Assistant can propose updates to design elements such as Stages, Steps, fields, and Personas. You review the proposed changes before applying them to the Blueprint.
When to use the AI Assistant
The AI Assistant can support different activities throughout the design process. Review the scenarios below to determine when the tool can support your design work.
- Large design actions: Use the AI Assistant for design changes, such as adding or refining an entire Stage, adding a related set of Steps, recreating a process based on a stakeholder requirement, or exploring a missing requirement before adding it to the Blueprint.
- Small refinements: Use it for targeted improvements while you work, such as adding a missing field, making a field required, updating a Step configuration, sharpening a field description, or asking it to suggest missing fields or alternatives for a Collect Information Step.
- Replacing manual tasks: Experiment with using it for actions you might otherwise perform manually. An example might include grouping, reshuffling, or removing fields; creating Embedded Data Objects; or changing a UI control type, such as converting a checkbox to a radio button.
- Clarification and explanation: Use it to explore concepts, such as Service-Level Agreements (SLAs), routing, and field requirements, or to identify details that might improve a prompt. You can also use it to explore industry knowledge, such as common field requirements for card payments.
Guidance
Apply the following guidance to keep AI-assisted design work focused and aligned with your intent.
- The AI Assistant accelerates design, but it does not replace your judgment. Because these capabilities are being added gradually, try the assistant first for tasks you might otherwise perform manually. Then review every suggested change carefully before committing it to the Blueprint.
- Use it from the relevant screen so the assistant has the right context, especially when working in Preview or refining data, workflows, fields, or Step details.
What makes an effective prompt
The best prompts are specific. A strong prompt names the target, says where it goes, and gives the business reason and any concrete requirements, such as allowed picklist options or whether a field is required or optional.
Examples
| Action | Example Prompt |
|---|---|
| Add a Stage and its Steps | Add a ‘Risk Review’ Stage between the Verification and Fulfillment Stages. Within the Stage, add an automation to retrieve the applicant’s credit score, a decision that uses Approve/Refer/Decline to determine eligibility based on credit score, and a Collect Information Step routed to an Underwriter to review the loan terms |
| Add a field | Add an ‘Underwriter Notes’ field of type Text to the 'Review loan terms' Step so the Underwriter can record observations about the applicant’s credit results and affordability. Do not make the text field required. |
| Improve the description for better Preview data | Update the description of the 'Loan Term' field to identify the allowed values of 12, 24, 36, 48, or 60 months so that the Blueprint Preview generates representative sample data. |
Check your knowledge with the following interaction:
This Topic is available in the following Module:
Want to help us improve this content?