Kuali Announcements logo
Back to Homepage Subscribe to Updates

Announcements

Find all documentation at https://kuali.zendesk.com or click on 'Back to Homepage' above

Labels

  • All Posts
  • Fix
  • New Feature
  • Improvement
  • Announcement
  • Release Updates

Jump to Month

  • November 2026
  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026
  • April 2026
  • March 2026
  • February 2026
  • January 2026
  • December 2025
  • November 2025
  • October 2025
  • September 2025
  • August 2025
  • July 2025
  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • March 2023
  • February 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
Powered by

Create yours, for free!

FixNew FeatureImprovement
2 weeks ago

September/October Release Update

New FeatureS & Improvements

Filter Document Lists by Table and Repeater Data

You can now filter the Document List using fields within Tables and Repeaters. This makes it easier to find documents based on repeated data, such as protocols with specific species or documents with multiple PIs.

Choose whether all, some, none, or more than one row or repeat should match your criteria. Then select a filterable field within the table or repeater and configure your filter.

New Table/Repeater Filter Options

To get started, use the three-dot menu in a table or repeater column header, or search for the table or repeater in the Filter drawer.

──────────────────────────────

Set Conditional Permissions Based on Values in Tables and Repeaters

Not everyone listed on a form needs the same access. You can now set Conditional Permissions based on a value in each person's Table or Repeater row, such as their role, department, or another selection. This lets you keep a complete list of people for reporting while controlling who can view or edit the record.

Here are a few examples of how you can use this feature across Kuali products:

  • Research Proposals: Give everyone in a Key Personnel repeater viewing access, while allowing only those marked PI or Co-PI to edit.
  • Academic Ops Program Proposals: Give faculty and department representatives viewing access, while allowing those marked Program Director to edit.
  • Ready Continuity Plans: Give everyone on a Plan Team viewing access, while allowing those marked Plan Owner or Plan Editor to make changes.
  • Build - Project Request app: Let everyone on a Project Team view a request, while only those marked Owner can edit.
  • Build - Hiring Request app: Give everyone on a Search Committee viewing access, while allowing only those marked Search Chair to edit.

When configuring a Conditional Permission, select A person listed in a table or repeater, based on a value in their row. Then choose the person field, the field to match in the same row, and the values that should grant access.

Permissions are automatically granted to people whose rows contain a matching value, so you can manage different access levels without creating separate fields or repeaters.

New Table/Repeater options in Conditional Permissions

──────────────────────────────

Manage Group Data with New Identity Settings

The Private Data tab in Spaces & Settings has been renamed to System Data. It's the central place to manage Private Data and other system-wide settings (including the newly added Identity Settings).

The new Identity Settings section in System Data gives System Administrators a central place to manage information consistently across all Groups. You can configure standard fields that apply to every Group, making it easier to track institutional information and control how Groups are used across different processes.

To get started, you can enable two commonly used fields with a toggle:

  • Institution Unit Number: Add a text field to track Groups using your institution's unit codes.
  • Active: Add a checkbox to track whether a Group is still in use.

You can also also add custom Text, Textarea, or Checkbox fields to capture additional information across all Groups. Once you enable the standard fields and add custom fields, such as Human Subjects Group in the example above, they'll appear on the Fields tab of every Group, as shown below.

Form Designers can use checkbox fields from Identity Settings or the selected Blueprint to filter Data Lookup gadgets pointed to Groups. For example, you can exclude inactive Groups or show only Groups that apply to a particular process.

Group and Blueprint hierarchy data can also be added to forms and used in conditional visibility, workflow rules, and the Document List, giving you more flexibility to build processes around your institution’s organizational structure.

──────────────────────────────

Create Ratio-Based Calculations with the New Ratio Gadget

You can now capture a ratio on a form as two whole numbers, like 1:2, with the new Ratio gadget, and apply that ratio to a value with the new ratio type of calculation. This lets you calculate proportional values automatically as the form is filled out — such as converting weekly instructional hours into credits on a course form — eliminating manual math and the errors that come with it.

When configuring a calculated Number gadget, you can select a value and a Ratio gadget to automatically calculate the result. For example, a value of 4 with a 1:2 ratio calculates to 2.0.

New Ratio gadget

Use ratio-based calculations for scenarios such as credit-to-contact hours, staffing ratios, resource allocations, or other processes where a value needs to be scaled by a defined proportion.  For example:

  • Credits from contact hours: 45 lecture hours × 1:15 = 3.0 credits
  • Clinical supervision: 24 students × 1:8 = 3.0 supervisors needed
  • Student-to-faculty ratio: record 15:1 on a program proposal

The Ratio gadget stores both parts of the ratio exactly as entered, providing accurate calculations without converting the ratio to a decimal first.

──────────────────────────────

FixES 

Forms
- Default values now fill in for fields inside repeating sections
- Calculations work more reliably, including totals from repeating sections and when you duplicate a document or create a new version
- Number fields keep trailing zeros, warn you about invalid input instead of silently changing it, and are recognized correctly in conditional logic
- Editing restrictions now apply to table columns and to newly added rows, and read-only fields in repeating sections and tables are no longer treated as required
- Fields hidden by conditional visibility no longer block submission (including on anonymous forms) or lose their saved values
- Lookup fields now find matches on partial words, can reach every record when you search, and no longer get stuck loading
- Addressed an issue with inconsistent data masking on Private Data gadgets within Tables and Repeaters
- Long field names display in full when you set up conditional visibility
- Images in rich text fields can now have alt text and custom sizes
- The State/Province field now includes military address options
- Date fields now accept limits of 100 days or more
- Help links now work when a form opens in a side panel
- Signatures now display in the same font for everyone
- Form Preview now shows read-only images and no longer shows a blank first page
- Typing in the form builder is faster for fields inside repeating sections
- Screen readers now announce validation messages more reliably

Documents & Lists
- Draft documents can now be exported
- Date filters now use your institution's time zone, and "Created At" is now available in advanced filter settings
- CSV exports and imports are more reliable, and a stuck import can now be cancelled
- "Show All Versions" now loads for documents with long version histories, and version numbers are now accurate
- Document history is cleaner: fewer automatic "Edited by Kuali system" entries, no false "changed" flags on attachments, and fewer errors when you open it
- Opening an item from your action list now starts at the top of the form
- The Dashboard tab is back in all apps
- In Kuali Ready, plans with large attachments can now be exported
- Fixed several display issues, including cut-off text, dropdowns, and page resizing

Workflows & Approvals
- Required fields in view-only sections no longer block you from completing a task
- Denying a document now works when an acknowledgment is still pending
- Sending a document back to a step that gets skipped automatically no longer stalls the workflow
- A withdrawn document that you edit and update now goes back to Draft
- Notifications now show the names of people selected in fields that hold more than one person
- App admins can now run and manage secondary workflows more easily, and scheduled workflows now work when their dates come from a lookup field
- The workflow builder's Test mode now points to the step that needs fixing and no longer requires unrelated fields
- The Approve button displays correctly on mobile, and email buttons display correctly in Outlook
- Long workflow step names now wrap instead of getting cut off, and other display issues in workflow settings are fixed

Sharing & Permissions

- The Permissions screens are now clearer and easier to navigate, with options that don't apply to Build apps removed. We've also improved performance so the Effective Permissions tab now loads successfully for larger sites.
- Anonymous sharing settings now show and save correctly, and they match between the Permissions screen and the Share dialog
- The "Next" button on anonymous multi-page forms is visible again
- Admins can now remove the built-in "All Authenticated Users" admin access from an app
- Dataset admins can now work with datasets that haven't been published yet
- Duplicating an app now keeps its custom groups and role-based field rules
- Moving an app to a different Space now works
- Publishing errors now explain what went wrong
- Firefox users no longer see an "unsupported browser" warning

PDF Export
- Japanese and other East Asian characters now print correctly
- You're now told when a non-PDF attachment can't be included in the PDF

Curriculum & Catalog
- Nested rule sets now display and expand correctly
- Courses, course codes, and course numbers now display consistently in the catalog and in course labels
- Catalog content inside repeating sections, and "Updated" addenda, now display correctly
- Program links in curriculum rules now open the right page
- Credit summaries now use the right rules when a form has more than one set
- Term validation now catches overlapping start terms
- The French and English catalog views now show rules in the right language
FixNew FeatureImprovementRelease Updates
2 months ago

August Release Update

We’re changing the way we share what’s new in Kuali! Rather than announcing each update separately, we’ll bring new features, improvements, and fixes together into larger release updates when there’s more to share.

These updates give you one place to quickly catch up on what’s new, with links to additional documentation when you want to dive deeper.

Here’s a look at the latest updates.

New Features & Improvements

Dataset Level Permissions

Give users more precise access to the areas they manage.

Admins can now assign permissions to individual datasets and other areas within a product, giving you more control over who can view, manage, or configure specific content. New permissions also separate app design and publishing from dataset administration, making it easier to give users the access they need without granting broader administrative capabilities.

Dataset Level Permissions UI

Existing permissions are unaffected — what people can do today stays the same, and you can begin scoping access per dataset whenever you're ready.

Learn more about dataset level permissions ->

──────────────────────────────

Admin and Reviewer Document Commenting

Collaborate directly on documents during review.

Admins and reviewers can now add inline comments to individual fields, table rows, and repeater entries. Comments support replies, resolution, archiving, and edit history, giving teams a more complete way to manage detailed feedback throughout a review.

Commenting example

Turn commenting on for a form in Form Settings. From there, Workflow Settings controls whether reviewers can comment as well as admins, and each approval, task, and acknowledge step can override that setting on its own.

Learn more about Inline Commenting ->

──────────────────────────────

Virtual Fields

Create dynamic values from information already on your form.

The new Virtual Field gadget lets form designers combine values from multiple fields, form metadata, and custom text into one read-only field. Use the resulting value as a Form Title, display it in the Document List, or reference it in form and workflow logic.

For example, you could combine Subject Code, Course Number, and Course Title to create a value such as ACC 100 - Financial Accounting.

Virtual Field example

Learn more about Virtual Fields ->

──────────────────────────────

Approval Delegates

Let designated delegates approve on someone else’s behalf.

Workflow designers can now configure delegates on any Approval Step via the new Configure a step delegate option. Both the primary approver and their delegates will receive the approval request and can take action.

When a delegate acts, Workflow Status/History records both who completed the action and the primary approver they acted on behalf of.

Learn more about Approval Delegates ->

──────────────────────────────

CSV Import

Create documents in bulk using CSV files.

Dataset admins can now import CSV files to create multiple Kuali documents at once via the new Import option in the Document List , making it faster to load existing or historical records. Imports can also populate multiple rows in tables and repeaters using related CSV files.

Import option in Document List

Learn more about CSV Import ->

──────────────────────────────

Workflow Actions from the Document List

Find your next action without leaving the Document List.

When you open a document from the Document List and have a workflow action to complete, you’ll now see an indicator linking directly to that action. This includes actions such as approve, deny, send back, submit, withdraw, acknowledge, and complete a task.

Document List actions within document

After taking action, you can return to the Document List view of the record.

Learn more about workflow actions from the Document List ->

──────────────────────────────

Admin Send Back and Deny

Admins can now send back or deny a document without being assigned to its current workflow step.

Form designers can allow app admins to send documents back to previously completed workflow steps or deny the document via new configuration options in Workflow Settings. This gives centralized administrators more flexibility to manage documents that need additional work during the review process.

Admin Deny and Admin Send Back options in document

Learn more about Allow app admins to send back and Allow app admins to deny ->

──────────────────────────────

Restrict Non-Admin View of Table and Repeater Rows

Control which individual rows non-admin users can see.

You can now let admins hide individual rows of a Table or Repeater from everyone else working on a document. Turn on Allow admins to restrict row visibility on the table or repeater in your form, and choose whether new rows start out Restricted or Unrestricted. From then on, admins can mark rows individually, and people who aren't admins see only the unrestricted ones — restricted rows are withheld when the document loads, not just hidden on screen.

New 'Allow admins to restrict row visibility' option

Some common use cases for this are letting department users follow a record without seeing every entry (i.e. a Negotiation record), holding an entry back until it's settled and then releasing it, and keeping admin-only notes in the same table as the ones everyone can see.

Example in a Repeater

Row restrictions are also enforced when documents are accessed through the API.

Learn more about restricting row visibility ->

──────────────────────────────

Batch Entry in Tables and Repeaters

Apply the same answer to multiple rows at once.

Form designers can enable the Allow this field to be batch-applied for supported fields inside tables and repeaters. This allows users to enter a value once and apply it across multiple rows, reducing repetitive data entry.  

New 'Allow this field to be batch-applied' config
This is only available on the below specific gadgets added in a Table or Repeater:

  • Dropdowns
  • Radio Buttons
  • Checkbox
  • Data Lookup (List)
  • Data Lookup (Multiselect)
  • Date
  • Number
  • Currency

Within the form, the end user will see a Batch Entry option. Selecting it lets them pick a field and apply one value across the rows. Blank rows are filled by default, or they can check Apply to all rows (overwrite existing answers) to also replace existing answers.

Learn more about Batch Entry ->

──────────────────────────────

Word-by-word Diffing for Rich Text

Rich text changes now highlight word by word.

Show Changes now highlights individual updates within Rich Text fields created with the new Lexical Rich Text gadget, rather than flagging the entire field as changed. Reviewers can quickly identify added or removed words, formatting and link changes, structural updates, and changes to images or tables.

Comparing document versions or reviewing an edit in History shows exactly which words changed inside a Rich Text field, rather than flagging the whole field.

Learn more ->

──────────────────────────────

Duplicate Field Validation

Prevent duplicate records before they enter workflow.

Form designers can configure a Validation gadget to compare field values against other submitted documents. This can prevent duplicate records based on a single field or a combination of fields—for example, preventing two courses from using the same subject code and course number.

Configuration to check documents with same value

When a duplicate is found, the user sees the configured validation message and must resolve the duplicate before submitting the document.

Field Validation

Learn more about Duplicate Validation ->

──────────────────────────────

Search All Documents

Expand your search when filters are hiding the document you need.

When you search the Document List with filters, sorting, or a view applied, Kuali now lets you know that those settings may be limiting your results. You’ll see a prompt reminding you that some documents may be excluded from your search. Select Search all documents to clear the existing filters, sorting, and view and search across the complete Document List.

Prompt if filters exist on search

──────────────────────────────

FixES 

Forms
- Required fields inside repeating tables are now enforced on submit
- Hidden sections no longer lose their data when a document is submitted
- Fixed tables showing up blank
- Numbers entered as .5 are now accepted as a default value in Number gadget (in addition to  0.5
- Long Text answers no longer get cut off in task forms
- Hidden sections no longer block Save with validation errors

PDF Export
- Fixed a US outage that stopped PDF exports
- Better table pagination, number wrapping, and field alignment; removed duplicate subtotals
- Text no longer gets clipped at page breaks
- Exports with very large attachments now fail clearly instead of hanging
- Fixed missing role-limited sections in notification PDFs

Workflow & Integrations
- Drafts left open a long time now submit on the current workflow version
- Reminder emails no longer sent for completed tasks
- Fixed workflow simulation when a trigger condition uses a data lookup field
- Trigger conditions can now check whether a document was deleted
- Integrations no longer send blank values for multiselect fields

Document Lists & Navigation
- Shared view links now keep their saved filter
- Fixed broken document list views in Dashboard Insights
- "Back to Document List" now returns you to the list
- Removed stray scroll bars in the Views panel
- Products now open on the first page as configured

Mobile
- Approve button is now reachable on mobile
- Header no longer covers the section navigation menu

Users, Groups & Permissions
- Fixed group detail pages failing to load
- Roles with more than 100 people now show their members
- Roles and fields can be created, renamed, and deleted again
- Dataset-level permissions are now honored when opening a single document
- Fixed SAML login failures at institutions with large sign-in responses

Academic Operations
- Catalog re-indexing no longer removes live content pages
- Restored program requirements that were displaying blank
- Courses inside Course Sets and Rule Sets now show their code and credits
- Course hover cards no longer flash "No Description" while loading
- Rule change history now shows course names instead of internal IDs

Research – Budget
- Indirect (F&A) costs now display in line items, badges, and Excel exports for all rate configurations
- Subaward indirect amounts now roll into top-level totals
- Calculated expense details are viewable on finalized budgets
- Fixed budget creation being blocked under New Rates Management
- "Create Budget" now works in the embedded view
- Syncing budget settings no longer overwrites existing data
- "Apply on rates" now works correctly when configuring fees

Fix
3 years ago

Accessibility Bugs & Enhancements

Happy Monday to you all! This post is an update on some fixes and enhancements we've made but it also serves as an explanation of how we approach accessibility (and bugs in general) at Kuali.

Noteworthy Fixes

Here are just a few of the recent noteworthy fixes and enhancements that we've recently rolled out in Build:

  • Keyboard focus added/fixed on multiple navigational elements
  • Error messages are now screen-reader compatible
  • Some screen reader messaging (including some button labels) was unclear

We have new stuff we're fixing all the time and a couple of larger enhancements coming soon. 

Our Approach to Accessibility

If you weren't already aware, one of our software development policies is called Zero Bug. This means we try to keep our bug list to zero (or near zero) every week. We aren't always perfect at this but we do a pretty good job.

In terms of accessibility, we actually treat accessibility issues as bugs. Naturally, we try to address them before they become bugs—as part of our typical development process—but occasionally some sneak past us. When they do, we add them to our bug list and apply our Zero Bug policy liberally and with glee.

Report Them Bugs 🐜

So that's a little "inside baseball" for you today. Hopefully that gives you a clearer idea of how we Do Our Thing™ here at Kuali. 

As usual, we encourage you to report any accessibility (or other) bugs. We appreciate the feedback we get from our customers and thank you for helping us make our software better. Cheers! ✌️

Fix
5 years ago

Users & Groups Limited to Administrator Access Only

We've recently updated the platform to limit access to users and groups for system administrators only. This update is being made to further our commitment to providing a secure and scalable platform.  In the future, system administrators will have full access to the users and groups module and can convert system users to system administrators in order to provide them access on a case-by-case basis.

If you have any questions about this release, feel free to comment here or email us at [email protected].  Happy building!

Fix
5 years ago

Improved conditional logic controls based upon smart gadget data integrations

Form and workflow designers now have increased flexibility in developing conditional visibility logic and custom workflow branching. 

Previously, designers could only manage advanced form and workflow logic of *Boolean data if the field type either was empty or was not empty. 

Now designers will be able to build advanced conditional logic and workflow branching conditions based upon whether Boolean data tokens added into a document via a Smart Gadget integration are either true or false.  

This new functionality will now enable designers to not just confirm if integrated Boolean fields have the presence of data (i.e. 'not empty') but will also confirm the true/false status of that data.

If you have any questions on this new improvement, don't hesitate to email us at [email protected] or comment here!

*Boolean field types are only available through Smart Gadget integrations and do not exist as independent gadgets in the form designer.


Fix
5 years ago

Removed several gadgets from being used as variables in custom email notifications

We've recently removed several gadgets from being referenced as a variable on custom email notifications.  

This change was  made with recent system optimizations in order to improve the experience of end users as the impacted gadgets were previously breaking email formatting notifications.

This change does impact previously configured custom email notifications.

The impacted gadgets removed include:
  • Rich Text Fields
  • Signature
  • Image Fields (removed from subject lines)
If you have any questions about this recent update, don't hesitate to comment here or email us at [email protected].
Fix
5 years ago

Recent changes to 'Submitted By' Gadget

We have recently made some changes to the Submitted By gadget due to issues being reported in Kuali Build and feedback submitted by customers. 

Some of these issues and feedback include the following. There were some instances where data contained in the gadget did not populate despite the document's metadata holding the correct value. Additionally, customers reported being confused when seeing submittedBy versus meta.submittedBy in notification variable lists and in other areas in the system.

Our hope is that these changes will reduce confusion and streamline the way metadata is used in Kuali Build applications.

We have changed the Submitted By gadget to use the value contained in the metadata. This change prevents issues with the gadget not being populated when data exists. A side effect of this change is that the gadget itself no longer has a data value, which impacts the following scenarios:    

  • Conditional Visibility using the Submitted By gadget data will no longer have data to read. Customers will need to update any Conditional Visibility rules to use meta.submittedBy when referencing the submitter moving forward.
  • Notifications using the Submitted By gadget data will no longer have data to read. Customers should update variables used in notifications to read off the meta.SubmittedBy data rather than the Submitted By gadget.
  • PDFs generated shortly after the fix will have blank Submitted By fields. Moving forward PDFs will generate correctly. Any PDFs that have blank Submitted By fields should be regenerated.
  • Anywhere where "Submitter" or "Creator" were listed to refer to the submitter will now read "Submitter - Display Name" in some areas of the system.

We have pushed out fixes for these problems, and with those fixes we have also migrated impacted data to ensure that the correct value shows up throughout customer forms. 

You can read more about these changes here. Please let us know if you have any questions regarding these recent updates.