Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Agent search and configuration

Updated on May 17, 2021

When you search for an agent using the fields provided on the Agent/Agency Management screen, a D_AgentList data page is initialized and populates the data as a list based on the search criteria.

When you click the Last Name or First Name link in the search results, the Update Agent Information screen opens where you can update agent information.

To view the D_AgentList data page, in the Dev Studio header search text field, search for and select D_AgentList.

The object type definition of this data page is PegaIns-Data-Party-Person-Agent, which is used in the context of agent-specific data. This data page is sourced by a GetListOfAgents report definition of the PegaIns-Interface-Agent class. This class is mapped to the IIF_Agent table in the PegaDATA database. This is the table in which all the agent-specific information is persisted. Every agent is identified with an AgentId unique key. This table also has an AgencyCode column that links an agent with the corresponding agency.

This data page accepts the following parameters to retrieve the list of agents from the IIF_Agent table in the database, and then populates the data as pxResults() pagelist of the PegaIns-Data-Party-Person-Agent class:

ParameterValue
AgentIdParam.AgentId
LastNameParam.LastName
AgencyCodeParam.AgencyCode
FirstNameParam.FirstName
EmailParam.Email

The Agent data that is retrieved from the interface layer is mapped to the database table, and then is mapped back to the data class (i.e., PegaIns-Data-Party-Person-Agent) using an AgentListMapper response data transform of the Code-pega-List class. To view the clipboard structure, at the bottom of Dev Studio, click Clipboard.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us