Frequently Asked Questions

This is an accordion element with a series of buttons that open and close related content panels.

What is a low code tool and what can they do for me?

Low code tools are visual application development tools where developers and software development teams can build applications of medium to lower complexity. This can save time, boost productivity, reduce costs, and increase flexibility for certain applications.

For more information about what types of features and development are possible on the low code Betty Blocks platform check out Is Low Code Solutions right for me?.

Who is the intended audience of low code tools?

There are 2 main audiences for these tools: Those that will automate workflows and create applications, and those constituents and partners that will benefit from using those workflows and applications.

Will we be required to move existing applications to the low code tool?

No. Our intent is to provide tools that folks want to use. This effort will not remove tools already in use.

Must I use the selected low code tool? Can I use a different tool? Will my tool go away?

You do not have to use the selected low code tool and no tools will be removed as part of this initiative. We encourage using campus provided tools (e.g. Betty Blocks, Qualtrics, Google Forms, etc.) to better assure your applications and data are safe, secure, compliant with policy, and can leverage other campus IT and data infrastructure. Using tools not provided by campus comes with risks where the benefits need to be compared to the risks and potential impacts.

 

Who will pay for tool licenses?

The service will be provided as a fully subsidized service from the Division of Information Technology (DoIT).

Is the low code initiative related to the Ancillary System Program (ASP) initiative?

They are related as this initiative is under the ASP umbrella and ASP deadlines are driving the timeframe. However, this initiative is looking beyond ASP needs for what’s needed in a campus low code tool.

 

How are you soliciting input and getting buy-in?

Information about how stakeholders across campus were involved in the selection of the low code tool can be found in the Low code tool selection process document.

Beyond selecting the low code tool, a service advisory board has been formed with representatives from across campus to help ensure the success and utility of this new service campus wide.  Additionally, there are several other ways that folks on campus can get involved including our Microsoft Teams channel and in the future our communities of practice.

What will campus support look like for the low code tool?

The Low Code Solutions RACI provides information about what campus support will look like for the low code tool and service.

How will I get training on the selected tool?

An overview of the training opportunities and how to get started can be found on our training page. Additionally, how-to documentation related to the Low Code Solutions service and Betty Blocks platform are available in the Low Code Solutions KnowledgeBase.

How soon will the Low Code Solutions service/low code platform be available?

Information about the implementation of the Low Code Solutions service and access to the low code platform can be found on the about page of our website.

Will the low code tool support sensitive or restricted data (e.g. Student/FERPA, PHI/HIPAA)?

For information about what types of data the low code tool supports please see the terms of service.

How soon can I expect to hear back after I've submitted a request to the Low Code Solutions team?

The service team will help answer questions and requests that come through the customer support form or serviceteamforlcs@office365.wisc.edu.

Hours of operation: M-F, 8:00 AM – 4:00 PM (excluding holidays)

During these hours urgent requests will be responded to within 1-4 hours and standard requests will be addressed within 2-3 business days with the following caveats:

  • Application creation with SSO capabilities may take up to 2 weeks based on team availability and dependencies.
  • SSL certificates may take up to 2 weeks. Note that most support for the Betty Blocks platform itself is provided from their Netherlands headquarters.

How will the data that is pulled from campus APIs be governed?

Application managers/developers will need to go through the data approval process according to the API team’s process. After approval, the application manager/developer would obtain the credentials from the API team to pull data from the API for that specific application. See Data usage approval for UW-Madison, UW System and other data sources for more information.

Any reusable block API will not have the credentials saved with that block. When the block is pulled into an application, the approval process mentioned earlier will be required prior to credentials being provided by the appropriate API team.