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
Improvement
a month ago

Improvements to Dataset Level Permissions

We’ve made dataset-level permissions clearer and easier to understand.

When we introduced dataset-level permissions, we heard from many of you that the new permissions experience was confusing—especially in Build apps. We listened to that feedback and made several updates to make permissions clearer and more consistent.

Here’s what’s improved:

  • A simpler Build apps permissions view. Since datasets don’t apply to Build apps, separating app and dataset permissions created unnecessary confusion. Permissions now appear together in a single matrix, making it easier to see and manage access for an app.
  • Clearer permission names. Design and Publish this app is now Configure this app, and Administer this dataset is now Administer documents.
  • More descriptive permission statuses. Updated labels make it clearer whether someone has a permission, doesn’t have it, or whether the permission isn’t available.
  • Clearer permission indicators. Updated labels and hover text help explain where permissions come from and what happens when you change them.
  • Helpful guidance. Help text provides additional context about permissions when you need it.

These updates don’t change what dataset-level permissions are designed to do. You can still give people access to the specific content they manage without giving them broader administrative access. We hope these changes make that functionality clearer, and we apologize that our initial rollout didn’t make the permissions experience as clear as it should have been.

One of the main benefits we want to highlight with the new dataset-level permissions is the separation of Configure this app and Administer documents. This gives you more flexibility to let groups like a Sponsored Programs Office or Registrar’s Office administer documents without also giving them access to change the form or app configuration.

Learn more about Dataset Level Permissions →

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

Improvement
3 months ago

New: Academic Ops - Duplicate Term Validation

You can now prevent curriculum records from being saved with overlapping effective Terms.

When you create a new version of an existing curriculum record, Kuali now validates the record's term range against other versions. If the effective terms overlap, you'll see a validation error and won't be able to save or submit the record until the conflict is resolved.

Validation on duplicate term

This helps ensure only one version of a curriculum record is active for a given term range, preventing incorrect versions from appearing in catalogs, lookups, and other downstream processes.

What's New?

Duplicate Term Validation automatically checks the effective terms of curriculum record versions whenever you:

  • Save a draft
  • Submit a draft to workflow
  • Apply edits to a completed record

If the new version's term range overlaps an existing version, Kuali displays a validation message explaining the issue.  Please note, if you have the 'Ignore required field validation on save' enabled in Form Settings the validation will occur on submit rather than save action.

How it works

Duplicate Term Validation prevents overlapping versions by enforcing these rules:

  • A new version's Start Term must be after the previous version's Start Term.
  • A new version's Start Term cannot fall within the previous version's effective term range.
  • A version's End Term must come after its Start Term.
  • Once a newer version exists with an Indefinite end term, an earlier version cannot be changed back to Indefinite.

Term comparisons are based on the actual dates associated with each academic term. Because of this, two versions cannot share the same term boundary. For example, if one version ends in Fall 2026, the next version must begin with a later term.

Example

Suppose an existing course version is effective from Fall 2025 through Spring 2026. If you create a new version with a Start Term of Spring 2026, Kuali displays a validation error because the two versions overlap during that term.

Update the effective terms so the versions no longer overlap, then save or submit your changes.

Improvement
3 months ago

New: Certification and Inline Reviewer Enhancements

We've made several enhancements that make it easier to collect certifications and review information from the right people during workflow—especially when working with repeatable sections like personnel lists or reviewer assignments.

These updates give administrators more flexibility when configuring forms and provide a better experience for researchers and reviewers completing certifications.

What's New

Configure access based on a person in the form

You can now configure Limited Availability and Limited Editability using a Person Typeahead field on the form, not just workflow roles.

This enhancement is especially useful for repeaters, allowing each researcher or reviewer to access only the certification or checklist fields assigned to them.

To configure this feature, add a Person Typeahead gadget to a repeater, then configure Limited Availability or Limited Editability on another gadget within the same repeater. Select User Identity as the rule type, then choose the Person Typeahead field that determines access. You can also combine additional rules, such as allowing administrators to complete certifications on behalf of a researcher.

More granular workflow editing in repeaters

When configuring certification the Admin can now also make a section within a repeater individually Editable at a workflow stop.  This will allow a reviewer to complete their certification, or review checklist, without allowing them to make changes to the rest of the repeater.

Improved Signature Display

The Signature gadget now provides additional audit information when used as part of a certification.

When viewing a document in read-only mode, you'll now see:

  • Signature of the user who signed the form
  • Username of the user who signed the form
  • Timestamp of when the user signed the form

This makes it easier to verify who completed a certification and when it was submitted.

What This Means for You

For administrators

You can now build more targeted workflow experiences by:

  • Configuring Conditional Availability or Conditional Editability based on a Person Typeahead field.
  • Selecting User Identity as the rule type and choosing the person field that controls access.
  • Combining additional rules when needed, such as allowing administrators to complete certifications on behalf of researchers.
  • Making individual sections within a repeater editable during specific workflow stops while keeping the rest of the repeater locked.

For end users

When working on a document, you'll only be able to access the sections your administrator has configured for you.

When viewing completed documents in read-only mode, signature fields now display the signer along with the date and time the certification was completed, providing greater visibility into the certification process.

Improvement
4 months ago

New: Scheduled Secondary Workflows

You can now automate workflow actions based on dates, helping you send reminders, trigger integrations, and manage time-sensitive processes without manual effort.

Scheduled Secondary Workflows let you create workflows that run on a specific date, on a recurring schedule, or relative to a date stored in a form. This makes it easier to stay ahead of upcoming deadlines, renewals, expirations, and other important milestones.

What You Can Do

With Scheduled Secondary Workflows, you can:

  • Trigger workflows before or after a date in a form
  • Schedule workflows to run on a specific date
  • Create recurring schedules that run daily, weekly, or monthly
  • Set workflows to stop after a specific date or number of occurrences
  • Configure multiple schedules for the same document, such as reminders 90, 60, and 30 days before an expiration date
  • Use different workflows for the same date field when different actions or notifications are needed

How It Works

When creating a workflow, select A specific date or interval as the workflow trigger.

Trigger type in Workflow

Add Trigger Criteria

When you select A specific date or interval, the workflow begins with a Trigger step. Use this step to define which documents the workflow should run against and when it should execute.

Secondary Workflow Trigger Step

Choose a Schedule

Scheduled workflows can be configured to run based on a date stored in the form or on a fixed date.

Based on a Date from the Form

Select Based on a date from the form, then choose the date field you want to use. Configure the workflow to run before or after the selected date and specify how many days, weeks, or months should be used as the offset.

Common examples include:

  • 30 days before an expiration date
  • 7 days after a submission date
  • Multiple reminder schedules, such as 90, 60, and 30 days before an expiration date

You can click + Add Configuration to create additional schedules for the same workflow.

On a Specific Date

Select On a specific date to schedule the workflow based on a fixed date rather than a form field.

Set the Execution Frequency

Choose whether the workflow should run:

  • One-time – Runs only on the selected date.
  • Every – Runs on a recurring schedule.

Recurring schedules can be configured to run every:

  • X days
  • X weeks
  • X months

The system automatically handles common scheduling scenarios. For example, a workflow scheduled for the first day of a month will continue running on the first day of future months. Likewise, a workflow scheduled for March 31 will run on the last day of months that have fewer than 31 days.

You can also configure when a recurring schedule should stop:

  • Never
  • On a specific date
  • After a set number of occurrences

Timing of Scheduled Workflows

Scheduled workflow processing runs daily at 5:00 AM Mountain Time.

This timing ensures date-based calculations work correctly across all supported time zones, including Hawaii. For customers in Eastern Time, scheduled workflows will process at 7:00 AM ET.

Improvement
5 months ago

New: Reorder Table and Repeater Rows with Drag and Drop

We're excited to introduce a new way to manage data in Table and Repeater gadgets. Users can now reorder rows using drag-and-drop functionality or keyboard controls for improved accessibility.

Why This Matters

There are many situations where the order of information matters. Whether you're arranging researchers for a System-to-System (S2S) submission, organizing attachments, or updating the sequence of steps in an experimental design, changing the order of entries should be quick and intuitive.

With this enhancement, you can easily adjust the order of rows without deleting and re-creating entries.

Some examples include:

  • Reordering investigators or key personnel in a proposal submission
  • Changing the display order of attachments
  • Inserting a new step into the middle of an experimental design
  • Updating the sequence of activities, tasks, or workflow steps
  • Organizing repeated data entries in the order you need

What's Changed

All tables and repeaters now include a drag handle at the beginning of each row or repeated section.

Example in a Table:

Drag handle for Table or Repeater

Example in a Repeater:

Users can:

  • Drag and drop rows or repeater entries to a new position
  • Use keyboard controls to reorder items for an accessible experience
  • See the order update dynamically as items are moved

This functionality is available anywhere tables and repeaters are used throughout the platform.

Tracking Changes

When Document History is enabled, changes to the order of table or repeater entries are recorded in the document's history. Reordered items will also appear as changes when comparing document versions, providing visibility into how the document has evolved over time.

Improvement
6 months ago

Default View Settings Have Moved to Views

Default View Settings are now managed directly in Views, making it easier to control what users see by default.

Previously, admins configured default views in Data Settings. Now, that functionality lives in the Views list, where you can set any view as the default without switching between different areas of the product. This update also introduces the ability for users to edit their existing views.

What’s New

  • Default View Settings moved to Views (Admins):
    You’ll now find the Default View at the top of the views list.  Initially it will always default to show the Number, Submitted At, and Submitter fields in the Default View but it can always be updated to the desired Columns, Filters, and Sort logic.
    Default View in Views
  • Configure document views before publishing

    The Document List now displays the search and view options before any documents are created.  Previously, options like Search, Sort, Columns, Filters, and Views only appeared after the first document was added. Now, you’ll see these controls as soon as you create the app, so you can configure your Default View and other views before publishing your form.

  • Set any View as the default (Admins):
    Select a view, open the menu, and choose Update with current settings to update the default view for all users with that configuration. Or simply make the necessary changes in the Default View and choose the Update with current settings to bring in the updates.
    Update Default View with current settings
  • Edit saved Views (All users):
    You can now update your existing views by selecting the menu and choosing Update with current settings - this will apply any updates to the filter, column, order, etc. to that view.
    Update any View with current settings
  • In-product guidance (All users):
    When visiting Data Settings, you’ll see a message pointing you to the new location.
    Data Setting message about new location
    A pop-up will appear in Views to highlight these changes and help you get started.
    Views pop-up alerting about changes
Improvement
6 months ago

Interactive Design Lab Improvements Release

We’re excited to share a new set of improvements inspired by our first-ever Interactive Design Lab at Kuali Days 2026.

This session brought together teams across Academic Ops, Build, Ready, and Research creating a new kind of collaboration. Administrators worked directly with product and engineering to share thoughtful ideas for improving the user experience—and the impact was immediate.

Our engineers jumped in during the session, working through feedback in real time and delivering meaningful enhancements based on your ideas.

Now, we’re excited to put those improvements in your hands.

What's New

View Effective Permissions for Any User

You can now view a complete breakdown of a user’s access in the new Effective Permissions tab within the Person record, making it easier to understand roles and permissions across the system. For more details, see the full announcement.

Effective Permissions tab in People

Persistent Space Sorting

Your selected sort order for apps within a Space now persists across browser sessions and is saved to your user profile—rather than being limited to a single browser session.

Wait for Calculation Inputs

A new setting ensures calculations only run after all required inputs are entered, helping ensure more accurate and complete data.

When you Enable calculations in a Number or Currency field, you’ll see a new option: Require all inputs before calculating. When selected, the calculation won’t run until all required fields are completed.

New config in Number and Currency gadgets

Improved Bridge Testing Visibility

When testing a Bridge integration, logs now show the input and output at each step. This makes it easier to troubleshoot and validate your integrations.

Bridge testing logs with inputs and outputs

Custom Titles for Workflow Branch Routes

You can now add custom route labels to individual workflow branches in the workflow builder, making it easier to understand each branch at a glance—without needing to interpret the underlying logic every time you revisit a configuration.

We’ve also added Collapse All Branches to the left step menu, so you can quickly condense your workflow for a cleaner view. When you’re ready, use Expand All Branches to open everything back up.

Route label in Branch step and the Collapse/Expand all options

Sticky Table of Contents in Forms

The Form Navigation on the left side of the document now stays visible as users scroll, so they can quickly move between sections without losing their place.

This table of contents appears when you enable Turn top-level sections into pages in Form Settings.

Form Navigation

Export People List to CSV

You can now export the People list to CSV. Filter or sort the list as needed, then download exactly what you need. Choose between 'Current View' or 'All Data' for your export.

Export People list

Updated Gadget Terminology

We’ve renamed the Multiple Choice gadget to Radio Buttons to better match common terminology.

Multiple Choice now Radio Buttons gadget

More Flexible Date Field Controls

You can now set Date field restrictions based on the Current date, giving you more dynamic control over selectable dates.  This is addition to the existing options of Specific date and Created date.

Date Field Current Date

Improved Time Selection

The Time field selector now includes a dropdown with AM/PM selection, making it faster and more intuitive to enter times:

Time gadget selector

Thank You!

Your feedback made this possible. The ideas shared during the Interactive Design Lab directly shaped these improvements, and we’re excited to keep building together.

Stay tuned for more opportunities to collaborate—and more updates shaped by your input.

Improvement
6 months ago

New: Smarter Search Results in Document Lists

We’ve improved how search works in document lists to help you find the right records faster. These updates reduce noise and surface the most relevant results—especially when you know what you’re looking for.

What’s New

More precise multi-term searches
Search now uses AND logic when you enter multiple terms. Results must match all terms, not just one.

  • Before: Searching “Computer Engineering” returned records with Computer or Engineering
  • Now: Results include only records with Computer and Engineering

This means fewer, more relevant results.

Stronger prioritization for title matches
Results now give more weight to matches in the Title field. If a record’s title matches your search, it will appear higher in the list.  This is driven from the Form Title Field in Form Settings.

Why This Matters

  • Spend less time scanning through irrelevant results
  • Find exact matches faster—especially when searching by title
  • Get cleaner, more focused result sets

What to Expect

  • You may see fewer results for the same searches—but they’ll be more relevant
  • If a search returns no results, try simplifying or adjusting your terms
  • Results will be better ranked, with title matches appearing first

You’ll also see an in-product alert in the document list to highlight this update.  Also, more information can be found in the Understanding Search Functionality in Kuali article.