Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Kuali Build lets you integrate data from other systems, such as KFS and LDAP.

Smart Advanced Gadgets: Data Lookup (Single Item), Data Lookup (List), and Data Multiselect gadgets allow connection to other data sources and allow fields to be automatically populated in forms based on information provided. Form integrations populate data into a form, like auto-filling certain form fields with user information or creating a dropdown list of options (e.g. KFS accounts, departments, etc).

More information on utilizing Smart Gadgets is available here:
https://kuali.zendesk.com/hc/en-us/articles/21933731329179-Smart-Gadgets-Data-Lookup-Single-Item-Data-Lookup-List-and-Data-Multiselect

Below is a list of available integrations, along with a short description about the data the integration retrieves.

Available Kuali Build Integrations

Description

Details

Developed /
Supported By:

LDAP NetID Lookup

The LDAP NetID Lookup Webservice is used to retrieve various attributes, relative to the current user, as contained in the university's LDAP repository.

  1. Input: Kuali Build Username (a.k.a NetID used to access the Kuali Build System)

  2. Output: UConn NetID; additional LDAP Attributes (e.g. Last Name, First Name, Department # etc.) can be displayed, as well as used in other webservice calls, and are available as linked auto-filled gadgets

ITS IAM Team

UConn Departments

Retrieve a list of KFS Departments and associated metadata

  1. Input: Department Name

  2. Output: KFS Org Code, Head NetID, Location, Type, Reports to Org Code and Organization Name can be displayed, as well as used in other webservice calls, and are available as linked auto-filled gadgets

ITS KFS Team

KFS Account Info by Account Number

Retrieve KFS Account Info and associated metadata by Account Number

  1. Input: KFS Account

  2. Output: KFS Account Attributes (e.g. Fiscal Officer and Account Supervisor Name, NetID, email, Org Code, Expiration Date, etc.) can be displayed, as well as used in other webservice calls, and are available as linked auto-filled gadgets

Note: If you want to use an attribute value in workflow linked via auto-filled gadgets, such as Fiscal Officer (as an example), you must convert the NetID to a Kuali Build user by using the NetID as KB User web service. (Only Kuali Build users may be used within workflow.)

ITS KFS Team

UConn Department Info by Org Code

Retrieve UConn Department information and associated metadata by Org Code

  1. Input: Org Code

  2. Output: Department Attributes (e.g. Org Name, Dept Head Title, Org Type, Reports to Org Code, etc.) can be displayed, and are available as linked auto-filled gadgets

ITS KFS Team

Employee & Supervisor Info by Employee NetID

Retrieve UConn (non-UHC) employee and supervisor information and associated metadata

  1. Input: NetID

  2. Output: Employee and Supervisor Attributes (e.g. Employee and Supervisor Name, NetID, Department, Org, etc.) can be displayed, and are available as linked auto-filled gadgets

ITS KFS Team

NetID as KB User

Used to convert a NetID into a Kuali Build user object (which can be used in Workflow)

In the Workflow portion of a Kuali Build app you can use the created Kuali Build User object in the Who will approve at this step? configuration section of an Approval step (or any other similarly configurable workflow Step)

  1. Input: NetID

  2. Output: Kuali Build User object

ITS ATS Team

Best Practice: If information being retrieved from an integration is an important element of your business process, consider making it required (set the 'Required' Data Source configuration toggle to the on position).


Why is this important? Occasionally, integrations are out of service, and the requested data cannot be retrieved by the Kuali Build system (e.g., LDAP, KFS or other applications are offline or experiencing system related issues). By making the integration required you ensure the form can only be submitted when the data is present, preserving the integrity of your business process.

required-toggle.jpg

Contact ITS-ATS Kuali Build Administrators via the Technology Support Center Portal at techsupport.uconn.edu with any questions.

 

Next

Workflow Essentials

  • No labels