Jerome Recker (Jerome@quavo)
Lead System Architect
Jerome@quavo Member since 2015 27 posts
Posted: June 15, 2017
Last activity: June 20, 2017
Posted: 15 Jun 2017 17:57 EDT
Last activity: 20 Jun 2017 12:46 EDT

Appl Property in Smart Dispute

I am working on a smart dispute installation, and throughout the sample data, I see reference to the .Appl property, both at account and transaction level. From what I gather, 2 stands for Deposit, and 3 stands for card (PegaFS-Data-Account-.SetApplDesc). My initial assumption was that this was something that pega created in order to keep track of their sample data account types, cards and transactions, and that it did not hold any significant value beyond the sample FSIF data. I have however found other references to this property within smart dispute.

The .Appl value of 3 makes sense to me, in that credit card accounts and transactions should have a value of 3, and they should ultimately create an object inheriting from PegaCard-Sd-Dispute-.

I am somewhat confused about the .Appl value of 2 though. Would a debit CARD have transactions of value 2, because they are tied to a deposit account, or should they have a value of 3 because they are tied to a card? Pega out of box does not use .Appl to determine the class of the checks for a .DepositAccountNumber to have a value. In general I am comfortable with setting the correct class, however I am not sure what to do with .Appl.

Low-Code App Development
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.