PEGA | Requestor Types In PEGA | Remote Requestor Tracing In PEGA | PEGA 8.6 | Training

[@anandaraonuthalapati9487]

👍👍👍

[@HarshaTrainingsacademy]

Hi anandarao thank u

[@Becool-0527]

Q) u said once requestor login then browser we can able to see that requestor session and logoff then that ID is removed. 2nd time login then it will generate req id ..in this case how we can find 1st session details ?

[@HarshaTrainingsacademy]

In Pega, once a user logs in and a requestor session is created, that session's information is stored in the Pega database and associated with the user's session. However, accessing detailed session information, especially across multiple logins and logoffs, might require administrative access and knowledge of Pega's internal data structures. If you're trying to retrieve detailed session information of a specific requestor across multiple logins, logoffs, and sessions, you might need to use the Pega Tracer, SMA (System Management Application), or custom logging mechanisms. Here's how you could approach it: 1.Pega Tracer: The Tracer is a powerful debugging tool in Pega that provides detailed information about how rules are processed during a requestor's session. You can use the Tracer to monitor the execution of activities, data transforms, and other rules for a specific requestor. While the Tracer primarily focuses on current sessions, it can help you understand the actions taken in each session and can be useful for tracking the flow of execution. 2.System Management Application (SMA): SMA is an application in Pega that offers various tools and monitoring capabilities for managing the Pega platform. SMA provides insights into server nodes, requestors, and other runtime components. You might find information about active requestors, sessions, and their status using SMA. 3.Custom Logging: If you need more detailed historical information about sessions, you might consider implementing custom logging. You could develop custom log entries using Pega's Log-Message method or your organization's preferred logging mechanism. By logging session-specific information, you can create a history of user interactions and details related to each requestor's session. Remember that accessing and managing session-specific information can involve technical and security considerations. You might need appropriate permissions and access rights to view detailed session data. It's also important to follow your organization's data privacy and security policies while handling user session information. If you're specifically trying to track session details across logins, you might need to design a custom solution that stores and associates session information based on unique user identifiers or tokens that persist across sessions. Such a solution might involve custom development and integration into Pega's framework.

[@naturalworld1002]

hi thanks , in real time projects , a csa equalent developer will has access to admin, app ,prediction studios??

[@HarshaTrainingsacademy]

Hi, ain studio access may not be given.... But prediction it depends.. if the person has to work on Decisoning , he / she will be given access to it..

[@Bunny-ux2bs]

👍👍👌

[@HarshaTrainingsacademy]

Thank u bunny