...
Form classes follow the document hierarchy, creating what has been termed "parallel hierarchies." For instance, org.kuali.kfs.fp.document.AdvanceDepositDocument extends CashReceiptFamilyBase which extends org.kuali.kfs.sys.document.AccountingDocumentBase, which in turn extends org.kuali.kfs.sys.document.GeneralLedgerPostingDocumentBase and hey, what do you know, that happens to extend org.kuali.kfs.sys.document.LedgerPostingDocumentBase, and that, finally, extends TransactionalDocumentBase. Forms also have hierarchies, and they often follow at least similar parentage as the document hierarchy. In our example, AdvanceDepositForm extends org.kuali.kfs.sys.web.struts.KualiAccountingDocumentFormBase, extends FinancialSystemTransactionalDocumentFormBase that extends KualiTransactionalDocumentFormBase. In short, it is important that our Form class hierarchy (and our Action class hierarchy) follows the document hierarchy to some extent.
See the hierarchy here 
Creating new slots for adding to collections
| Anchor | ||||
|---|---|---|---|---|
|
...