@AmarBhuwania 

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

Based on my research, this appears to be related to how report definitions handle caching in Pega 8.23.1. When a report is run by one user, the data is being cached and then incorrectly shared when another user runs the same report, rather than retrieving fresh data specific to the second user.

Here are several approaches you can take to resolve this issue:

Immediate Solutions

1. Modify Report Definition Settings
   • Check if your report definition is configured to use data pages for caching
   • Update the report definition to fetch data directly from the database instead of using cached data
   • This is especially important for reports containing user-specific data that shouldn't be shared
2. Review Data Page Configuration
   • If your report uses data pages, ensure they are configured with the appropriate scope
   • Change the scope from "application" to "requestor" to ensure data is user-specific
   • Set appropriate refresh strategies to clear cached data between user sessions
3. Add User Context to Report Filters
   • Modify your report definition to include user-specific parameters in the query
   • This ensures that even if caching occurs, the cached data is specific to each user
   • Add filters based on user ID or other user-specific attributes
4. Clear Custom Filter Section Page
   • This issue may be related to a known behavior where the custom filter section page isn't properly cleared between users
   • Check if your report uses a custom filter section and ensure it's properly reset between runs

Long-term Best Practices

1. Implement Data Segregation
   • Use cache partitioning techniques to separate data between different users
   • Avoid global caching for user-specific information
   • Ensure that sensitive or dynamic data is not cached across user sessions
2. Optimize Report Performance
   • Specify the number of records that your reports retrieve from the database
   • Enable paging in reports
   • Filter data that your reports display to limit the amount retrieved
3. Regular Cache Management
   • Implement proper cache invalidation mechanisms
   • Consider using agents to periodically refresh or clear caches
   • Monitor cache usage and performance

If these solutions don't resolve the issue, it might be worth checking if there's a specific patch or hotfix available for Pega 8.23.1 that addresses report caching issues. The Pega Support team would have the most up-to-date information on any available fixes.

References:

• Best practices for creating reports
• Practical Applications of Report Definition and Data Pages
• Pega 8.x Cache Management