• Overview
  • Data approval
  • Data from campus data sources
• Student data 
• Staff/faculty/employee data  
• Financial data  
• System-wide data 
• Other data sources 
• Sending data from a Low Codes Solution (Betty Blocks) application to another application/database 

Overview

Data approval

As an application manager/technical contact, please work with the appropriate data steward to obtain approval of use for data for each role created within your application. The data steward will want to know what data each of the roles will be seeing in your application, regardless of source, and where the data will be going whether report, notification or integration with another system. Please work with the Office of Compliance as well if web analytics use is being considered.

Data from campus data sources

There is often a different request form for each data type, however, they all ask for approximately the same information. So be prepared to answer: 

• • Name of application,
  • Description of usage,
  • Data elements requested, 
  • Data elements exposed and viewed by others, 
  • Who will be able to view that data,  
  • Other data elements displayed from other sources, 
  • The nature and necessity of displaying requested attributed data,
  • The list of data elements to be stored locally (within Betty Blocks) 
  • And the purge process and timeline of data retention. 

All of the UW-Madison API integrations currently available on the Integration Catalog.

Student data 

1. The DoIT ROAD Team Support road@doit.wisc.edu (Registrar’s Office Apps Development Team) asks that you initiate a request here: Set up a request from Curricular and Academic Operational Data Store (CAOS): https://kb.wisc.edu/19278 will send you to this site where you can fill in a Request Form. https://crisauthorization.wisc.edu/Application/Default.aspx 
2. Once the form has been filled out completely and submitted, print the page and collect the appropriate approvals. Please scan and send the request with the approvals to Reporting Services at data@registrar.wisc.edu. 
3. Once approved, follow the instructions for Setting up SOAP UI for CAOS and obtain credentials for both the Test and Production tiers. 
4. Once you have the credentials, they can be added to your application in the Betty Blocks platform.
   1. Create a configuration with the user_key 
   2. Create the data source and enter the API key from the configuration 
   3. Create a Remote data model that pulls data in from that external data source 
5. If student data is obtained from a source other than CAOS,
   1. An approval process still needs to occur with the appropriate data steward. 
   2. Please contact the Low Code Solutions service team for assistance in determining how best to import/ingest the data into your Betty Blocks application. 

Staff/faculty/employee data  

See the PersonAPI for querying core person data elements such as name, email, address and role information for UW-Madison constituents. The PersonAPI is currently pulling data from HRS, however, it is being built such that live data will come from Workday once that system is live.  

See the HR API (in development according to the Integration Catalog) for HR/employee resources that have a one-to-many relationship with people's jobs (i.e. resources that are common among multiple jobs among multiple people). Examples - employee classification, location info, job definitions etc. 

1. There are multiple informational items available when Getting Access to the PersonAPI 
2. The request will get automatically routed to the appropriate data stewards who may reach out if additional details about the request are needed. Otherwise, after the request is approved by the data stewards, the DoIT API team will reach out to grant access to the Person API.  
3. Once you have the credentials, they can be added to your application in the Betty Blocks platform.
   1. Create a configuration with the user_key 
   2. Create the data source and enter the API key from the configuration 
   3. Create a Remote data model that pulls data in from that external data source 
4. HRS data access can be obtained if the PersonAPI data does not suit the application needs.
5. If staff/faculty/employee data is obtained from a source other than HRS, an approval process still needs to occur with the appropriate data steward.     
6. If obtaining data other than through the PersonAPI, please contact the Low Code Solutions service team for assistance in determining how best to import/ingest the data into your Betty Blocks application. 

Financial data  

See the FinanceAPI (in development) will be able to retrieve structural data related to the Workday Foundational Data Model (FDM), validate accounting journal entries, and retrieve detailed journal transactions. 

NOTE: Finance APIs are being developed against Workday pre-production environments. Live data will not be available until Workday go-live. There are no financial APIs available against SFS. 

1. The Getting Started page provides more information including the Specification for the FinanceAPI. 
2. On the Getting Started page, follow the steps for getting access.
3. The request will get automatically routed to the appropriate data stewards who may reach out if additional details about the request are needed. Otherwise, after the request is approved by the data stewards, the DoIT API team will reach out to grant access to the Finance API.  
4. Once you have the credentials, they can be added to your application in the Betty Blocks platform.
   1. Create a configuration with the user_key 
   2. Create the data source and enter the API key from the configuration 
   3. Create a Remote data model that pulls data in from that external data source 
5. SFS Security page with documented Security Links provides information regarding accessing SFS data. 
6. If financial data is obtained from a source other than SFS, an approval process still needs to occur with the appropriate data steward.  
7. If obtaining data other than through the FinanceAPI, please contact the Low Code Solutions service team for assistance in determining how best to import/ingest the data into your Betty Blocks application. 

System-wide data 

A process for obtaining access to system-wide data (data from across the Universities of Wisconsin) via APIs is in progress. See the EDGC Decision: Data Approval Process for Enterprise APIs. 

The expectation is that the Integration catalog will provide links to the appropriate request forms once those are available. 

To obtain data from these other system-wide systems, use the Data Access Authorization Form at the bottom of this system data page.  

• Central Data Request/CDR Edit Update System (CDR/CEUS)
• Debt Service
• Facilities
• Instructional Analysis Information System (IAIS)
• Job Groups
• Multiple Applications and Admissions Database (MAAD)
• Plant Ledger
• PreCollege
• Student Statistics Book (SSB)
• Transfer Information System (TIS)
• Tuition and Fee Reporting
• Unclassified Applicant Self Reporting 
• Wisconsin GI Bill (Veterans Administrators only) 

Other data sources 

If you are pulling in data into a Betty Blocks application from a system not listed above, the application manager/technical contact must ensure that proper data governance is maintained.  

Please contact the Low Code Solutions service team for assistance in determining how best to import/ingest the data into your Betty Blocks application. Please work with the appropriate data steward to obtain approval. 

Sending data from a Low Codes Solution (Betty Blocks) application to another application/database 

If you're introducing data into a new platform and exposing/using that data to a new or different system, the Application Manager/technical contact must ensure that proper data governance is maintained. Please work with the appropriate data steward to obtain approval. 

Please contact the Low Code Solutions service team for assistance with determining how best to extract the data out of your Betty Blocks application.