1. Kuali Nervous System Aaron Godert, Cornell University Jonathan Keller, University of California, Davis

2. Outline What is the Kuali Nervous System? Where did it come from? What does it do? And, what's Rice got to do with this?

3. What is the KNS? KNS = Kuali Nervous System An application development framework that KFS and KRA are built on Allows for pattern based integration with other middleware components Focuses on providing a foundation for efficient development of business functionality Helps to ensure consistent development practices

4. KNS is a Rice Component What is Kuali Rice? Kuali: a humble kitchen wok; Malaysian origins Rice: it is what it is –Sits on the bottom of a dish –Not a very tasty meal by itself –Better with some substance on top KFS - Beef KRA - Chicken KS - Seafood Rice is the foundation to a hearty software product

5. The Goals of Rice The board vision for Kuali is a plug and play module by module approach to software Kuali started as financials, but has evolved into a suite of administrative software (KFS, KRA, KS) A lot of functionality in Kuali systems –Keeping the Kuali code base as small as possible without impacting quality is key Highly productive development environment –For Kuali projects –For non-Kuali projects

6. Rice Goals Cont. A common and consistent architecture –Allow developers to understand other rice enabled projects –Infrastructure would not need to be reinvented on each project - focus on functionality! –Rice team can focus on IT standards, like SOA, that will benefit the entire Kuali software suite –Adoption of other Kuali modules feasible Generic enough for non-Kuali applications KNS plays a major part in this!

7. How We Got Here Kuali Enterprise Workflow (KEW) existed in production at Indiana University Kuali Finanical System (KFS) started development and had an architecture team –Morphed into the Kuali Nervous System (KNS) team –Achieve technical consistency across all aspects of KFS KFS --> KNS --> KEW

8. Along Came KRA Kuali Research Administration (KRA) wanted to reuse the core features KRA needed to integrate with KFS Align our core to support sharing services across Kuali apps in a loosely coupled fashion All Kuali products should be technically consistent under the hood –For end user functionality –For different development methodologies

9. Rice Was Born! KEWKuali Enterprise Workflow KNSKuali Nervous System KSBKuali Service Bus KENKuali Enterprise Notification KIM Kuali Identity Management

10. History of the KNS KFS spent a large amount of development time up front, using the best talent from each of the partner institutions Came up with a foundation on which to build KFS - the Kuali Nervous System It focused on a unified approach to development of functionality –A standard way to use workflow, perform CRUD operations, handle business transactions KNS extracted from KFS and put into Rice as a module

11. KNS Overview Provides reusable code, shared services, integration layer, and a development strategy Provides a common look and feel through screen drawing framework A document (business process) centric model with workflow as a core concept

12. Understanding the KNS Paradigm ENTITY_T Entity (POJO) ORM Mappin g Data Dictionary Lookups and Inquiries Maintenance Documents Transactional Documents Workflow (KEW)

13. Transactional Documents These are data-entry centric documents or “transactions” that model the business processes Examples include: Proposal Development, Journal Entry, Payment Reimbursement Built on a case by case basis using the Kuali Rice tag libraries (encompass snippets of UI behavior): –Notes and attachments –Workflow route log (audit log) Integrated with workflow

14. Maintenance Documents They do not need to be built case by case - just one JSP that draws them all These are the CRUD documents - an easy way to maintain support tables in a Kuali database –C: Create new table records –R: Read or query table records –U: Update existing table records –D: Delete existing table records Examples include: –Budget rates –Project codes

15. Inquiries A way to drill down and get more read- only information about a table record

16. Inquiry Screenshot

17. Inquiry Example Configuration Travel Account Inquiry

18. Lookups A way to search for data by a set of criteria Results of lookups can be returned to other lookups or documents

19. Lookup Screenshot

20. Lookup Example Travel Account Lookup Look up Inst.

21. Lookup Example Cont. <lookupField attributeName="foId" required="false" forceLookup="true" />

22. Other KNS Features Data Dictionary Question component Notes and attachments Pluggable business rules Pluggable authorizations System parameters Extended/custom attributes

23. What Does the KNS Do? Reusable Modules –Data Persistence –Document Framework –Business Rules / Validation –Lookups –UI Components Maintain Consistency Set of Services

24. Data Dictionary Business Objects –Attributes –Lookups –Inquiry Page –Relationships Document Definitions –Sections –Fields –Collections

25. Persistence Framework Business Objects Collections Security –Field Encryption –Masking Extendable

26. Business Objects Attributes –Labels –UI Widgets –Validation Attribute References Lookups Inquiries

27. Documents Maintenance Documents –Edit Business Objects –Rigid Layout Transactional Documents –e.g., Financial Documents –Free-form document layout

28. Maintenance Documents Created without code XML File Definition –Fields on Document –Sections –Locking –Business Rule Linking –Collections

29. Business Rules Rules –onSave –onRoute –onApprove –onAddLine Pre-Rules –Can ask questions

30. Authorization/Security Module Level Document Level Field Level –Read Only Fields –Hidden Fields –Masked Fields

31. Batch Processing Built-in Scheduler Trigger Jobs Steps

32. Questions? KNS Documentation: –https://test.kuali.org/confluence/display/KULDOC/Kuali+Nervous+Systemhttps://test.kuali.org/confluence/display/KULDOC/Kuali+Nervous+System