Agreement dynamic attributes example use

Specs are used in the account domain so that the limited data model provided for agreements, which use the same data model and transactions as contracts and accounts, can be easily extended based on agreement type.

Using value packages as an example, a bank might sell a savings account product and a checking account product as a value package. When a customer purchases the bundle, the bundle itself is stored as a managed account with an agreement type of Value Package; the savings account and the checking account are stored as two separate referenced accounts. The bank might have other agreement types, such as Vendor Agreement or Service Agreement, for which it needs to capture and store data. One method of storing this data, could be to add additional attributes to the existing physical data model for the different agreement types. Alternatively, a more flexible way to support additional attributes for different agreement types is to define unique agreement specifications for each agreement type. In this value package example, the spec for value packages might look like this:
ValuePackageSpec

NumberOfAccounts	Long
ConsolidatedMonthlyFee	AmountDerivedType
EligibilityIndicator	String	Enum ("Y", "N")
ValuePackageSubType	String	Enum ("Student Value Package", "VIP Package", ...)
WelcomeGiftClaimed	Boolean

Once this spec is added to InfoSphere® MDM and associated with the Value Package agreement type, these custom attributes will apply to all agreements created with the Value Package agreement type.

For more information on how to associate specs with agreement types, see Developing with specs.