Similarly, the IntakeAgencyDetails flow action of the PegaIns-Data-Party-Org-Agency class calls the post-processing activity SaveAgencyInformationWrapper of the PegaIns-Data- Party-Org-Agency class. This wrapper activity, in turn, calls the SaveAgencyInformation activity of the PegaIns-Interface-Agency class. This called activity, such as in the case of the agent creation activity, creates an agency code while creating a new agency, and then renormalizes the data from the data layer to the interface layer. Similar to the agent case, these agency activities are reused for updating an existing agency as well.
The data class used for Agency data is PegaIns-Data-Party-Org-Agency, and the interface class is PegaIns-Interface-Agency.
To view the SaveAgencyInformation activity, in the Dev Studio header search text field, search for and select SaveAgencyInformation.
For site specific implementation, the data pages should be updated to have the appropriate sources for their agent data.
Previous topic Create agent Next topic Customer management