Conversation
Maantic
IN
Last activity: 11 Dec 2025 1:51 EST
Defect in blueprint -Old dropdown values retained after changing Industry and Sub-Industry negative scenario testing failed
Issue Description:
Initially, an Industry and Sub-Industry were selected and the flow was completed till the end successfully. Later, the user navigated back to change the Industry and Sub-Industry and proceeded again with a different flow.
At this stage, the previously selected dropdown values and related data are not getting cleared. Even after selecting a new Industry, the system is still retaining old values from the previous Industry.
As a result, the Blueprint is getting generated with the new Industry but with old dropdown values, which do not belong to the new Industry and are not available for selection.
This is causing data inconsistency and incorrect blueprint generation.
Steps to Reproduce:
-
Select Industry and Sub-Industry
-
Complete the flow till the end
-
Navigate back
-
Change Industry and Sub-Industry
-
Continue with the new flow
Expected Result:
All previously selected dropdown values and related data should be cleared automatically when Industry and Sub-Industry are changed.
Actual Result:
Old dropdown values and related data are still retained, even after changing Industry and Sub-Industry.
Severity: High
Priority: P1
Frequency: Always occurring
Pegasystems Inc.
IN
Thanks for sharing your observation. We want to avoid situations where a Blueprint is accidentally wiped out just because someone chose the wrong value from a dropdown. Users may have invested significant time collaborating with stakeholders to build that Blueprint, and we need to protect that work.
That’s why Blueprint includes an explicit Regenerate action. If a user truly wants to discard the existing content, they must intentionally click Regenerate. This behavior is by design and ensures that Blueprint isn’t reset unintentionally. It’s not a defect—it’s a safeguard.
Maantic
IN
@SumanKumarSuman Kumar
Have you reviewed the PDF I shared? From what I understand, it appears that the industry is intentionally mentioned as Healthcare, while the application purpose is listed as Employee Service, which falls under HR Operations. Do you feel this is correct From a user perspective, this still doesn’t seem correct to me. Please review it once again, or we can get on a call to discuss the issue in more detail.
Suggestion: Let’s display an error message at the top. Alternatively, when the user changes the selection, we can block the action and show a message stating that the data has been changed and the previously selected value is no longer available in the current dropdown.
Pegasystems Inc.
IN
As mentioned earlier, we never remove existing Blueprint artifacts unless the user explicitly selects Regenerate Blueprint. We know teams invest significant time and collaboration to create their Blueprints, so we want to ensure nothing is lost because of an accidental dropdown selection.
Please note that the Industry and Sub-industry values are used only as inputs during the initial Blueprint generation. They have no impact when the Blueprint is imported into the Pega platform. The focus should remain on ensuring the Blueprint accurately captures and solves the business problem.
Regards,
Maantic
IN
@SumanKumar I’m not sure how you’re saying there is no impact. You may know the implementation details, but users don’t. As a user, I expected some basic behaviour, and I raised this only because I faced an issue while using the feature. I don’t want to go deeper into this discussion — I just want to close the topic here, as it feels like this was implemented intentionally.