@Harshatrainingsacademy, thank you sir for providing a clear explanation. I just wanted to ask if there is a scenario where a data page can’t be traced ?I was asked this in an interview
In Pega, Data Pages can generally be traced like other components of your application for debugging and monitoring purposes. Tracing allows you to capture and view the execution flow and interactions with Data Pages. However, there can be scenarios where tracing may not provide the expected or complete information related to Data Pages. Here are some situations in which tracing Data Pages might be challenging or less informative: 1.Security and Access Control: If the Data Page is subject to security restrictions, and the tracing user does not have the necessary privileges, you may not be able to see the details of that Data Page in the trace. Security settings can prevent unauthorized users from accessing or viewing certain data. 2.Data Page Configuration: If the Data Page is not configured correctly or if it has specific settings that affect its behavior, tracing might not capture the expected results. For example, if the Data Page is configured to run asynchronously, the tracing might not show the asynchronous loading process. 3.Data Page Caching: Data Pages often involve caching to improve performance. If the data is already cached and the caching strategy prevents frequent reloading, tracing might not show the data retrieval step because it's using the cached content rather than fetching data from the source. 4.Timing and Tracing Settings: If the tracing settings are not appropriately configured, you might not capture the specific actions related to Data Pages. Ensure that tracing is enabled for the relevant components and that the trace level provides the necessary detail. 5.Concurrency and Parallel Execution: If multiple users or processes are interacting with the same Data Page concurrently, tracing might not always show a clear picture of a specific user's interaction with the Data Page. This can be especially relevant in high-traffic applications. 6.Temporary Issues: Occasionally, there may be temporary issues with the Pega platform or the specific Data Page configuration that affect tracing. These issues might resolve themselves over time or require further investigation.
Hi Harsha sir, you help all pega developers to easily understand the topics thank you first of all🙏can you please say the scenario which you stated fetching INR/ dollar. How to implement please
Editable data page is useful , only to manipulate the data and use it with in requestor session... Savable data pages can be used to open, update, manipulate and save back the data to tables...
Access to advanced interview session on advanced topics... Harsha Trainings is one of the leading and Placement Consultant Provided training with qualified trainers on PEGA,DEVOPS, PowerBI,JAVA,DATA SCIENCE, MULESOFT ,Spring&Microservices,OracleFinance,Appian,Core&Advance java,Django,Communication&Varbal and other various leading software technologies…. For those who have gap after education, we have job placement assurance courses... Subscribe to our channel to learn best of best in technology... For training call us on 9652532753, 9885312299
Pega uses a concept called the "clipboard" to manage data instances during case processing. The clipboard consists of pages, and each page can hold data. The size of the clipboard is essentially determined by the available system memory and the configuration settings within the Pega platform. Some key points related to clipboard size in Pega: Java Heap Memory: Pega applications run on the Java Virtual Machine (JVM), and the clipboard size is constrained by the available Java heap memory. If there's insufficient memory, it can lead to performance issues or even application errors. Page Structure: The clipboard is structured in the form of pages, and each page can hold different types of data, such as properties, attachments, or other objects. The size of these pages, along with the number of pages, contributes to the overall clipboard size. Data Pages and Pages & Classes: Pega allows the definition of data pages, which can load data into the clipboard. Additionally, the "Pages & Classes" feature in Pega specifies the class and page name for clipboard pages, influencing the clipboard structure and size. Clipboard Optimization: Pega provides tools and techniques for optimizing clipboard usage. Developers can implement best practices to manage the clipboard efficiently, such as limiting the data loaded into the clipboard and optimizing data page configurations. It's important to note that Pega applications can be highly customizable, and the clipboard size can be influenced by the specific implementation and configurations within a Pega application. For detailed information about the clipboard size in a specific Pega application, it is recommended to refer to the Pega documentation or consult with the application developers or administrators.
Harsha training doing selfless work in the field of education for so many years...
Thank u for your compliments, we try our level best to deliver best to our students and get them jobs
i like this trainer because he 's honest that he has a stomache
Excellent explaination..easy to understand
Thank you... Pls watch other videos too
@Harshatrainingsacademy, thank you sir for providing a clear explanation. I just wanted to ask if there is a scenario where a data page can’t be traced ?I was asked this in an interview
In Pega, Data Pages can generally be traced like other components of your application for debugging and monitoring purposes. Tracing allows you to capture and view the execution flow and interactions with Data Pages. However, there can be scenarios where tracing may not provide the expected or complete information related to Data Pages. Here are some situations in which tracing Data Pages might be challenging or less informative:
1.Security and Access Control: If the Data Page is subject to security restrictions, and the tracing user does not have the necessary privileges, you may not be able to see the details of that Data Page in the trace. Security settings can prevent unauthorized users from accessing or viewing certain data.
2.Data Page Configuration: If the Data Page is not configured correctly or if it has specific settings that affect its behavior, tracing might not capture the expected results. For example, if the Data Page is configured to run asynchronously, the tracing might not show the asynchronous loading process.
3.Data Page Caching: Data Pages often involve caching to improve performance. If the data is already cached and the caching strategy prevents frequent reloading, tracing might not show the data retrieval step because it's using the cached content rather than fetching data from the source.
4.Timing and Tracing Settings: If the tracing settings are not appropriately configured, you might not capture the specific actions related to Data Pages. Ensure that tracing is enabled for the relevant components and that the trace level provides the necessary detail.
5.Concurrency and Parallel Execution: If multiple users or processes are interacting with the same Data Page concurrently, tracing might not always show a clear picture of a specific user's interaction with the Data Page. This can be especially relevant in high-traffic applications.
6.Temporary Issues: Occasionally, there may be temporary issues with the Pega platform or the specific Data Page configuration that affect tracing. These issues might resolve themselves over time or require further investigation.
Thank you sir
Hi Harsha sir, you help all pega developers to easily understand the topics thank you first of all🙏can you please say the scenario which you stated fetching INR/ dollar. How to implement please
Use rest integration....!!!!
Tq sir for explaining clearly
Thank you , pls share with ur friends too
What is the difference between editable and savable data page, and
when to use these data pages ?
Editable data page is useful , only to manipulate the data and use it with in requestor session...
Savable data pages can be used to open, update, manipulate and save back the data to tables...
Nice explanation.. tell me continue class video
Watch keyed data pages video
Hi Mr.Harsha, what are the benefits we get if we join for Pega advanced monthly in this channel?
Access to advanced interview session on advanced topics...
Harsha Trainings is one of the leading and Placement Consultant Provided training with qualified trainers on PEGA,DEVOPS, PowerBI,JAVA,DATA SCIENCE, MULESOFT ,Spring&Microservices,OracleFinance,Appian,Core&Advance java,Django,Communication&Varbal and other various leading software technologies….
For those who have gap after education, we have job placement assurance courses...
Subscribe to our channel to learn best of best in technology... For training call us on 9652532753, 9885312299
Excellent explanation
Glad it was helpful!
Hi Harsha, May I know the clipboard size? I got this question in interview
Pega uses a concept called the "clipboard" to manage data instances during case processing. The clipboard consists of pages, and each page can hold data. The size of the clipboard is essentially determined by the available system memory and the configuration settings within the Pega platform.
Some key points related to clipboard size in Pega:
Java Heap Memory: Pega applications run on the Java Virtual Machine (JVM), and the clipboard size is constrained by the available Java heap memory. If there's insufficient memory, it can lead to performance issues or even application errors.
Page Structure: The clipboard is structured in the form of pages, and each page can hold different types of data, such as properties, attachments, or other objects. The size of these pages, along with the number of pages, contributes to the overall clipboard size.
Data Pages and Pages & Classes: Pega allows the definition of data pages, which can load data into the clipboard. Additionally, the "Pages & Classes" feature in Pega specifies the class and page name for clipboard pages, influencing the clipboard structure and size.
Clipboard Optimization: Pega provides tools and techniques for optimizing clipboard usage. Developers can implement best practices to manage the clipboard efficiently, such as limiting the data loaded into the clipboard and optimizing data page configurations.
It's important to note that Pega applications can be highly customizable, and the clipboard size can be influenced by the specific implementation and configurations within a Pega application. For detailed information about the clipboard size in a specific Pega application, it is recommended to refer to the Pega documentation or consult with the application developers or administrators.
Excellent explanation
Glad you think so!