Question
Citibank
US
Last activity: 10 Mar 2025 7:36 EDT
Pega Mashup Future
What is the Pega Roadmap for Pega Mashup? Are there any plans to deprecate in the future?What does pega look as alternate to support the omni channel experience(DX API)?
Updated: 27 Feb 2025 7:49 EST
Pegasystems Inc.
GB
@MireilleDallaire is this something your team might be able to answer?
@SUDHARSANK below is a GenAI-powered tool. All generated answers require validation against the provided references.
Pega Mashup Roadmap
Pega Mashup (also called Pega Web Mashup) continues to be actively supported and integrated into the Pega Platform. It remains a strategic component for embedding Pega application content within external websites and mobile applications. Based on current documentation and roadmap information, there are no specific indications that Pega plans to deprecate Mashup technology in the near future.
Deprecation Plans
While there are no explicit plans to deprecate Pega Mashup at this time, it's worth noting that Pega has been expanding and investing in alternative approaches for omni-channel experiences, particularly through the DX API. This investment pattern suggests that while Mashup will continue to be supported, the strategic direction is gradually shifting toward more flexible API-based integration options.
@MireilleDallaire is this something your team might be able to answer?
@SUDHARSANK below is a GenAI-powered tool. All generated answers require validation against the provided references.
Pega Mashup Roadmap
Pega Mashup (also called Pega Web Mashup) continues to be actively supported and integrated into the Pega Platform. It remains a strategic component for embedding Pega application content within external websites and mobile applications. Based on current documentation and roadmap information, there are no specific indications that Pega plans to deprecate Mashup technology in the near future.
Deprecation Plans
While there are no explicit plans to deprecate Pega Mashup at this time, it's worth noting that Pega has been expanding and investing in alternative approaches for omni-channel experiences, particularly through the DX API. This investment pattern suggests that while Mashup will continue to be supported, the strategic direction is gradually shifting toward more flexible API-based integration options.
Omni-Channel Experience Alternatives (DX API)
The primary alternative that Pega offers for supporting omni-channel experiences is the Pega Digital Experience (DX) API. This is a set of model-driven REST API endpoints that provide UI metadata to help develop seamless user experiences across different front-end frameworks while leveraging Pega's case management capabilities.
The DX API offers some distinct advantages over traditional Mashup:
- Centralized Business Logic: With DX API, you don't need to encode business logic in every channel. You can reuse single-sourced rules, validations, and processes across different channels.
- Greater Flexibility: DX API provides more customization options for developers who need a tailored user experience.
- Future-Proof Integration: If a custom front end is built to accommodate DX API responses, it can automatically adjust to changes in the Pega Platform, enhancing maintainability and reducing time-to-market.
- Optimized for Self-Service: DX APIs are particularly well-suited for web self-service use cases where aligning user experience with digital strategy is important.
When to Use Mashup vs. DX API
Use Pega Mashup when:
- You need quick integration with minimal development effort
- You want to embed the standard Pega UI directly
- Your customization needs are limited
- You need to rapidly deploy Pega functionality in an external site
Consider DX API when:
- You need a highly customized front-end experience
- You have front-end development expertise available
- You want more flexibility than Mashup provides
- You're building a new implementation that needs to be future-proof
- Your use case requires consistent business logic across multiple channels
References:
- Pega Digital Experience (DX) API Overview
- Development of web self-service interface
- Pega web mashups for embedding traditional UI in external web pages
- Differences between Traditional DX API and Constellation DX API
Citibank
US
@MarijeSchillernCan you help? Is Data instance first design pattern still applicable?
Pegasystems Inc.
GB
@SUDHARSANK this sounds like a new, unrelated question. If so, please can you post it as a New Question?
Can you mark Accept Solution to the original reply if it's closed?
Eclatprime Digital Private Limited
AU
Hi @SUDHARSANK,
What is the Data Instance First Design Pattern?
The Data Instance First design pattern in Pega involves persisting data related to a case before actually creating the case. This approach is beneficial when the decision to initiate a case depends on the data collected. For instance, when using a mashup, it's unnecessary to create a case immediately; instead, you can persist the case data first and decide later whether to create the case.
Key Characteristics:
-
Data Capture Before Case Creation: Collect and store data prior to initiating a case.
-
Decision Point: Determine, based on the collected data, whether a case needs to be created.
-
Flexible Integration: Allows integration with external systems where immediate case creation isn't feasible or necessary.
🔹 Applicability of the Data Instance First Design Pattern
This pattern is particularly useful in scenarios where:
-
Data Evaluation is Crucial: You need to assess the collected data to decide if a case should be initiated.
Hi @SUDHARSANK,
What is the Data Instance First Design Pattern?
The Data Instance First design pattern in Pega involves persisting data related to a case before actually creating the case. This approach is beneficial when the decision to initiate a case depends on the data collected. For instance, when using a mashup, it's unnecessary to create a case immediately; instead, you can persist the case data first and decide later whether to create the case.
Key Characteristics:
-
Data Capture Before Case Creation: Collect and store data prior to initiating a case.
-
Decision Point: Determine, based on the collected data, whether a case needs to be created.
-
Flexible Integration: Allows integration with external systems where immediate case creation isn't feasible or necessary.
🔹 Applicability of the Data Instance First Design Pattern
This pattern is particularly useful in scenarios where:
-
Data Evaluation is Crucial: You need to assess the collected data to decide if a case should be initiated.
-
External Data Collection: Data is gathered from external sources or systems before case initiation.
-
Resource Optimization: Avoids unnecessary case creation, thereby optimizing system resources.
Example Scenario:
In a recruitment process, candidate information is collected and stored in a Candidate data object. This data serves as a reference to initiate a case for scheduling interviews and selecting candidates for available positions. Implementing a data-instance-first approach allows for efficient handling of candidate data before deciding to create a case.
🔹 Is the Data Instance First Design Pattern Still Applicable?
Yes, the Data Instance First design pattern remains applicable and relevant. It offers a structured approach to data management, ensuring that cases are created only when necessary, based on the data collected. This pattern is particularly beneficial in scenarios where data needs to be evaluated before initiating a case, thereby optimizing system performance and resource utilization.
Current Relevance:
-
Enhanced Flexibility: Allows for more flexible workflows by decoupling data collection from case creation.
-
Improved Performance: Reduces unnecessary case creation, leading to better system performance.
-
Integration Capabilities: Facilitates integration with external systems where immediate case creation isn't practical.
For more detailed information and examples, you can refer to Pega's official documentation on design patterns:
If you have further questions or need clarification on specific aspects, feel free to ask! 😊
I hope you understand,
Thanks
Regards
Raja
Eclatprime Digital Private Limited
AU
Hi @SUDHARSANK,
Pega Mashup Overview
Pega Mashup enables the integration of Pega applications into external websites or portals, allowing users to interact with Pega features without leaving their current environment. This integration is achieved by embedding Pega content using an iframe or JavaScript.
🔹 Pega Mashup Roadmap and Deprecation Plans
As of the latest available information, there is no official announcement from Pega regarding the deprecation of Pega Mashup. It remains a supported feature, allowing organizations to embed Pega functionalities within external sites. However, it's essential to stay updated with Pega's official communications for any future changes.
🔹 Pega's Approach to Omnichannel Experience: DX API
To enhance omnichannel capabilities, Pega introduced the Digital Experience (DX) API. The DX API provides a more modern and flexible approach to integrating Pega's case management and business processes across various channels and devices.
Key Benefits of DX API:
Hi @SUDHARSANK,
Pega Mashup Overview
Pega Mashup enables the integration of Pega applications into external websites or portals, allowing users to interact with Pega features without leaving their current environment. This integration is achieved by embedding Pega content using an iframe or JavaScript.
🔹 Pega Mashup Roadmap and Deprecation Plans
As of the latest available information, there is no official announcement from Pega regarding the deprecation of Pega Mashup. It remains a supported feature, allowing organizations to embed Pega functionalities within external sites. However, it's essential to stay updated with Pega's official communications for any future changes.
🔹 Pega's Approach to Omnichannel Experience: DX API
To enhance omnichannel capabilities, Pega introduced the Digital Experience (DX) API. The DX API provides a more modern and flexible approach to integrating Pega's case management and business processes across various channels and devices.
Key Benefits of DX API:
- Consistency: Ensures a uniform user experience across all platforms.
- Flexibility: Allows integration with diverse front-end technologies and frameworks.
- Scalability: Supports seamless expansion across multiple channels without redundant configurations.
For more insights on implementing omnichannel experiences using Pega's DX API, you can refer to Pega's Conversational Channels Capability.
🔹 Recommendations
While Pega Mashup continues to be a viable integration method, organizations aiming for a comprehensive omnichannel strategy should consider adopting the DX API. It offers enhanced flexibility, consistency, and scalability, aligning with modern digital transformation goals.
For the most accurate and up-to-date information, it's advisable to consult Pega's official documentation and community forums regularly.
If you have further questions or need assistance with implementation details, feel free to ask! 😊
I hope you get the information on Mashup
Thanks
Regards
Raja
Pegasystems Inc.
GB
@Koti Raja your reply looks almost identical to the one I generated using GenAI.
Please can we make you aware that if you plan on using GenAI in your responses, you are obliged to disclose this at the time of posting.
Please see the updated 'About Support Center' best-practice guidance:
Eclatprime Digital Private Limited
AU
Hi @MarijeSchillern,
Thank you MarijeSchillern, for replying to the above answer,
Next time onwards I will follow that the answer is provided by GenAI-powered tool. All generated answers require validation against the provided references.
Thank you MarijeSchillern, for reminding that.
Raja