Kuali Rice at Indiana University

1. Kuali Rice at Indiana University How Kuali Rice is Accessed and Leveraged July 29-30, 2008 Eric Westfall

3. Application Integration • KEW Thin Clients • HR • ERA • EPIC • TK • SIS • KEW Embedded Clients • IUF • Coming Soon • Travel • KFS • Kuali Coeus

4. Statistics • 24 x 7 x 365 (minus maintenance) • HTTP Requests per Month - 45,084,367 • Users – 156,675 • Document Types – 96 • Workgroups – 1,610 • Rules – 9,097

5. Portal Deployment • Deploy into our Onestart Portal application • Deployed using iframes for most screens • Have a Notifications Tab which contains an Action List portlet • Test environments are also available from the portal • For administrators or power users, separate sections are published which allow access to Rules, Workgroups, etc.

7. Action List Counter • On the “Notifications” tab there is a counter which indicates the number of items in the user’s Action List • We created a simple standalone application which provides this service • Onestart portal uses Ajax to connect and read value • Will also pop-up a message to the user when items enter their Action List

8. Client Application Publishing • Client applications publish their own sections with entry point into their application and/or KEW • Examples: • eDocLites will use the portal to deploy links for accessing and creating their documents • Workflow Quicklinks included by HR • Publish content which has a URL to KEW Document Search with some query parameters already filled in – helps trigger searchable attributes for end users

9. Decision Support Services • The Kuali Rice database is replicated to our DSS environment daily • We’ve developed some views which provide access to document and eDoc Lite data • Views apply row-level security based on the “reporting workgroup” defined on Document Type • We’ve created some simple reports in IUIE • A common use case for accessing this data is for query or extract by EDL clients