Webinar
90 Mins
BA/CLSA Community: Delivering with Pega GenAI™ Blueprint - Series Introduction
Replay
Overview
Catch up on an exciting kickoff to our Delivering with Blueprint series with our first-ever webinar event for both the Business Architect and Lead System Architect communities!
If you haven't yet experienced the transformative power of Pega GenAI Blueprint™, find out why everyone is talking about it. In this session, we learned why Pega Blueprint is crucial to the start of every project, regardless of your project role. We heard from - and asked questions to - those on the leading edge of Pega application design with Blueprint and hear about the support available as you begin your Blueprint journey.
Agenda
- What is Pega GenAI™ Blueprint?
- History
- Roadmap
- Blueprint "end to end"
- Thoughts from the Panel
- Q & A
- Call to Action
Presenters
| Matt Healy | Director of Product Marketing: Intelligent Automation |
| Neal England | Principal Business Architect, Pega Consulting |
| Sonam Duhan | Principal Business Architect, Pega Consulting |
| Mayur Tadepalli | Principal System Architect, Pega Consulting |
| Carlos Villamarin | Lead System Architect, Pega Consulting |
| Brad Tanner | Consulting Manager, Pega Consulting |
| Christine Fioresi | Consulting Manager, Pega Consulting |
Slides and related links
- Slides from the session
- Create a Blueprint at pega.com/blueprint
- Pega Community: Blueprint hub
- Pega Community: Blueprint frequently asked questions
- Contact us with your feedback
Questions and Answers
Here are the questions that were asked (and answered!) during the event.
General
| Question | Answer |
|---|---|
| Is there any license cost to use Blueprint? | Blueprint is available at no cost to everyone through pega.com/blueprint. Other Pega GenAI capabilities do have a contract associated. Some are $0 but have terms associated and some are priced separately. |
| How often will we see updates to Blueprint. And is there way to see what has changed? | We are delivering changes every Wednesday. We are going to have release notes that come out every Wednesday with the new releases, and those will be on docs.pega.com. We also have the Blueprint Community Hub, where we're going to summarize the new features with the value, the best practices stuff like that. We are also starting up a new a newsletter so you can be an insider and get updates on new features as they happen. We'll have a way for you to sign up for that newsletter soon. |
| How do I join the LinkedIn groups you mentioned at the beginning of the session? |
Here are the links to join each group: |
Blueprint Capabilities
| Question | Answer |
|---|---|
| Can we upload Blueprint at a later time and continue editing? | Both in progress and completed Blueprints are saved and can be accessed via your dashboard for further editing, sharing, etc. as required. |
| Does Blueprint have the capability to generate an application based on Theme Cosmos? Currently it appears to generate only using Constellation as the built on application. | It does. By default, it builds a Constellation app. If you have an existing Theme-Cosmos or UI-Kit app, if you select that as your 'built on' layer when you import your Blueprint, your new app will inherit those UI approaches. |
| Does Blueprint support iterative development? Can I update a case type using blueprint after initial development? | Today, on 24.1.1, you can add new case types to existing apps, but not yet change existing case types. This is the plan over time! |
| In one of our demos to our client, we had to create a Blueprint in German. The Blueprint created assets in the background using special letters (umlauts and sharpess s ß), which caused exceptions during import in Pega. Will this problem be addressed at some point? | Yes. In many cases, there is an easy workaround: enable this DSS: Pega-RulesEngineRuleManagement/EnableUnicodeRuleNames (old release note: https://docs-previous.pega.com/enabling-unicode-character-support-object-names) |
| Can we create Page/Pagelist properties as part of the data model design? | Yes. You can create reference properties on the case data model and define it as single or a list which will create the page or pagelist |
| Is Blueprint compatible with all different frameworks? | When you are filling out the Blueprint and describing what you're looking to automate, there are dropdowns or selections you can make and eventually you get down to different application areas. Many of those are actually based off of our framework, workflows and applications. It's not 100% bulletproof yet, but we're working on it. |
| Is there a prescribed format of the text content that should go into the blueprint input? As the LLM prepares the response based on the content, to save time, if we can have a very prescriptive format of the content which works best, that would be great. | There is guidance provided through the 'What should I write' link. Also, look at the examples that the pre-defined Application purposes provide. These can also be used as examples of what you may want to capture. |
| What are plans for Blueprint & CDH? | Stay tuned! |
| Are there any use cases for the applications/case types without Pega based UI? Or without UI at all? | In the live app preview, you can see the API endpoints for your workflows as well. They'll get updated as you edit your workflows. |
| How integrations will be handled with Blueprint in future? | You can look forward to the ability to import existing assets in the integration space, things like open Api specs and the like. And really define out your integrations and data objects based on the Apis that you have in your back end. |
Application Architecture
| Question | Answer |
|---|---|
| When building enterprise applications, is it correct to assume that we should create a Blueprint for each component application? | We can conditionally select case types and data model when we import blue print into a Pega application env. But a cleaner way would be to define separate blueprints if multiple case lifecycles are involved and are in separate component applications. During a Discovery phase, it can also be useful to have them logically separated if you are working with different sets of business stakeholders and product owner. |
| In the demo, classes are being created as OlyOrg-AthleteManagement-Data-Athlete. What if we want OlyOrg-Data-Athlete put in the OlyOrg ruleset so that we could then refactor into an OlyOrg application? | As it was shown in the demo, you can also create Division and Unit classes. In terms of ruleset merge allocation, that can be defined at the time of merging the branch. |
| How can we leverage existing enterprise assets and integration patterns with this Blueprint design? | We can currently import blueprint into an existing application thus reusing the existing assets. Leveraging Integration patterns is a good question. Please provide details to [email protected] |
| When importing multiple case types from Blueprint how is the class definition managed? Is each case type enabled as 'is class group' or 'belongs to a class group'? | The import sets it as 'belongs to the work class group'. |
| How can we would manage branches when we have two or more teams working together in same application? Do you recommend one application by team with theirs branches or all teams working in same application with all teams branches? | When working in branches, as long as you have the branch order set up right you can have multiple branches in the same application. When it comes to Blueprint imports and you have multiple teams importing different Blueprints, they do get imported into different branches. The key thing to watch for are merge conflicts if you have same data class definitions in both Blueprints. |
Import
| Question | Answer |
|---|---|
| Is it one Branch per import? And can you nominate a branch name per import? | Yes: One branch per import operation. No: Currently you cannot nominate a branch pre-existent in your system, but a new branch is created automatically as the import process starts creating rules in Pega. |
| Can we undo Blueprint imports? | Yes. You can delete the branch after the import. |
| Can we import Blueprint in personal edition version? | You can import the Blueprint into a Community Edition, or any Pega Platform 24.1 environment. |
| Is there a way to only extract subset of the output from Blueprint? | When you import into Pega, you have control over what gets 'committed'; i.e., you can pick and choose case types which get created. |
| When import into an existing app, how does it resolve conflict with existing case lifecycle and datatype/structure? | Right now, importing into existing app is only for adding net new case types / data. It does not support overriding / editing anything. |
Delivery Practices
| Question | Answer |
|---|---|
| Interested to see how the preparation/discovery phase gets shortened with Blueprint. Any artefacts help us understand this better? | We have a user story library which will kick start the Backlog and requirement requirements and coming soon Blueprint Playbook. In the meantime, we will provide information during this webinar series. |
| Are there any examples to show how this can help for an ongoing project where we add increments to existing implementation? | If those increments are to add additional case types, then you can certainly use Blueprint to elaborate the process with your business and IT colleagues. If you are on 24.1.1, you can also load the Blueprint into an existing application. This gives you the option to continuously discuss and design additional processes. |
| Which role (LBA or LSA) creates and take ownership of the Blueprint? | In terms of leading these sessions with the business to identify the case types and design, this would most likely be the LBA, with the LSA loading the exported .blueprint file into Pega. However, both should be present for the end to end blueprinting sessions |
| What work is being done to transform the delivery methodology around Blueprint? | We are currently working on updating the delivery methodology and hope to roll this out in future sessions. Stay tuned :) |
| Is it possible to come across a situation where based on the prompt the case type design suggested by Blueprint is not matching up to the current process for the business, how should we take that discussion ahead with the business? | If the Blueprint output is extremely out of line with what you and the business were expecting, go back through your original selections of the options at the beginning of the Blueprint creation process. For example, if you are trying to wedge a "llama rental" use case into a Wealth Management app, you will likely get some unexpected results. After that, review and edit, the application description, with the business, and re-run the Blueprint. Even if you get the results to 90%, you can color in the remaining 10% afterward. Pega GenAI Blueprint helps you get to that 90% much faster. |