1. Eric Westfall – Indiana University Jeremy Hanson – Iowa State University Building Applications with the KNS

2. The 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 o A standard way to use workflow, perform CRUD operations, handle business transactions KNS extracted into Rice as a module

3. KNS Overview The Kuali Nervous System provides a rich set of open source functionality which can be used to build an electronic document 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

4. KNS Diagram

5. KNS Development CHART_T Chart (POJO) ORM Map Data Dictionary Lookups and Inquiries Maintenance Documents Transactional Documents Workflow (KEW)

6. KNS – The Toolkit KNS frameworks provide infrastructure for common business object operations. o Lookups allow users to find and return specific values. o Inquiries allow users to see related data for a specific value’s record. o Maintenance documents create or update new business object entities.

7. Other KNS Features Data Dictionary Question component Notes and attachments Pluggable business rules KIM Integration for Authorization System parameters

8. Lookup Page

9. Inquiry Page

10. Maintenance Document

11. Business Objects Attributes o Labels o UI Widgets o Validation Lookups Inquiries Relationships

12. Data Dictionary Business Objects o Attributes o Lookups o Inquiries o Relationships Document Definitions o Sections o Fields o Collections

13. The Data Dictionary Business Object XML Provides metadata for business object properties o i.e. maxLength, labels, control types Metadata is accessible in JSPs for business object field rendering Contains lookup and inquiry sections used for constructing those screens by the frameworks

14. The Data Dictionary (cont) Transactional Document XML Associates a Rule class and Presentation Controller or Authorizer class with the document type Maps a document class to a workflow document name and document type Maintenance Document XML Has many of the same features, but also defines the layout of the maintenance document itself.

15. Types of Documents Two types of documents Maintenance Documents Transactional Documents

16. Maintenance Documents Creates, Edits, Copies, and Inactivates Business Objects No GUI programming required, user interface is rendered by framework These are used for maintaining data An easy way to maintain support tables in a database Supports creation of new records and editing of existing records

17. Transactional Documents Any service you can think of 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): o Notes and attachments o Workflow route log (audit log) Integrated with workflow

18. The Document Hierarchy

19. Parallel Hierarchies

20. KIM - Permissions KIM has the concepts of Permission Templates and Permissions Permission Template represents some course- grained permission o Use Screen, Initiate Document, Maintain Records, etc. A Permission is created from a template and has more specific information identified on it’s permission details o for example “Initiate Document” of type “Transfer of Funds”

21. KIM - Permissions Evaluation of permissions is handled by the permission service. KIM provides plug points for implementing custom logic for permission checking o Example: permission checks based on hierarchical data Example Service Operations: o Is principal authorized by permission name w/details o Is principal authorized by permission template name w/details o Get assignees for permission o Get authorized permissions for principal o Get ids of roles that have given permission

22. Permission Data Model

23. KNS usage of KIM Permissions Many permissions exist that are used by KNS, examples: o Edit Document o Look Up Records o Use Screen o Create / Maintain Records

24. Building a maintenance document (1) We start with a business object: a Java class a mapping for the persistence layer a business object data dictionary file our goal: create new ones, edit or inactivate old ones

25. Building a maintenance document (2) Step 1: Build a data dictionary file Business object class to maintain The maintainable Locking keys A rules class Default existence checks The authorizer and presentation controller KEW document type The document's sections and fields

26. Building a maintenance document (3) The business rules class React to events which occur on the document o save o route o approve You have access to user input through the getNewMaintainable().getBusinessObject()

27. Building a maintenance document (4) Set your KIM permissions Who can initiate this document? Who can edit the maintenance document? What fields and sections can be viewed and edited?

28. Building a maintenance document (5) Routing is set through a standard KEW document type

29. Building a maintenance document (6) Add a link in your portal......and you're done!

30. Final Maintenance Document Screen