My use case is to implement a Pega GenAI Agent that can, at runtime, help identify the Activities, Data Transforms, Data Pages, and other rules being executed behind a particular screen or case. The agent should also provide contextual information about how these rules are being invoked, their execution flow, and their dependencies.
The current challenge is that there is no readily available tool or API that enables the agent to dynamically discover and retrieve the rules associated with a screen or case at runtime. As a result, the agent lacks visibility into the underlying rule execution context.
can anyone guide me how to make this work through any tool or workaround
Hello Arya, something like running your usecase with tracer / Performance Anlayser or Performance profile on, and extracting that data and feeding to the Agent. With the right instructions it should be able to build your outcome. But it would be per usecase specific outcome. But may I know how you are going to use this outcome?
So basically at runtime of any service case i want the user to interact with the agent chatbot to get information of how the current screen is being populated with data and what all have been running behind the screen and that chatbot like gets all the data from the activities , DT’s running behind the screen and gives the information to the user (pega Developer or Architect) and might offer better solutions of the particular rule if there is any flaw in the screen the user want to improve, the thing is i am unable to pass the data from the tracer to the agent .. you have any way how to do that?