Applications built on Pega Foundation for Financial Services interface with and manipulate the classes defined in PegaFS-Data-. The use of these classes lets developers write applications that use the PFFS data model while remaining independent of the underlying physical representation of the data. This is important for the rules delivered with PFFS since the foundation has knowledge of how and to what the classes in the data model will be mapped. When PFFS is installed, one of the first tasks is to connect it to the appropriate backend systems. The PFFS integration layer makes this possible with minimal disruption. Integration classes and rules are in PegaFS-Int- and contained in the PegaFSInt ruleset.

The following graphic shows how the Pega Foundation for Financial Services integration layer fits into the overall application design.

The application avoids a direct dependency on the underlying data stores by building on one or more optional Financial Service (FS) products as well as the PegaFS-Data- classes. In the example above, the FS application is also built on Pega Foundation for Financial Services. This allows for changes in mapping and storage with minimal impact to the top-level application.

This guide presents a high-level overview of the structure of the rules that need to change during the process of mapping Pega Foundation for Financial Services to your system of record.

• Example: Investment security integration