A new integration layer and data page rules are introduced in Pega7 Smart Investigate release. Prior to Smart Investigate 7.

• A separate database integration layer was not defined.
• Data from the database was fetched directly via connect-SQL rules making it tightly coupled with the application.
• New set of connect-SQL rules had to be defined in the application to extend the support for new databases.

Starting Smart Investigate 7x.

• A new pluggable database integration layer has been added for easy implementation.
• Data from the database is fetched via Data Pages through Report Definition rules.
• With Report Definition rules, the troublesome approach of creating new connect-SQL rules for new database is eliminated, making the application loosely coupled with Database.

As part of the integration layer Connect-SQL rules in Smart Investigate Layer have been converted to Report definitions referred through Data pages.

Ideally Integration class is required if data is read from external system. We don’t need the data integration layer if the if data is populated during runtime in database table or If the framework is designed for mapping data class layer with database layer for storing data (for example: Data- Admin-Operator-Security class instances are directly stored in DB table)

Following are the list of Smart Investigate Database tables considered for adding Integration layer in the Framework.

• Research Manager Layer
  • ADDITIONALPYMTINFO
  • HISTORY
  • MESSAGE
  • PAYMENTCHARGES
  • PAYMENTTXN
• Payments Layer
  • PCB_ACCOUNTS
  • INTERESTRATES
• Securities Layer
  • SECURITY
  • SETTLEMENT