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

New Feature
4 months ago

New: Propose Revisions to Completed Documents

You now have another way to update existing documents. In addition to editing a document directly or creating a new version, you can now propose a revision to an existing completed version and route those changes through your configured workflow before they're applied.

This new capability within Document Versions helps preserve the integrity of finalized records while giving your team a structured way to submit corrections or updates through your existing approval workflow.

When Should I Use a Revision?

Revisions are ideal when you need to update an existing completed version but want those changes to be reviewed and approved before they become part of the record.

Unlike editing a document directly, revisions don't immediately change the completed document. Instead, they create a draft copy of the selected version that can be updated, submitted through workflow, and approved before the changes are merged into the original version.

Unlike creating a new version, revisions don't create a separate version with its own version-specific information. They allow you to keep working with the existing version while maintaining an approval process for any proposed changes.

A common example is Curriculum Management, where a course or program has already been approved for an upcoming catalog and is actively being referenced as the version that will be published. If a correction is needed before the catalog is released, users can submit a revision to that approved version, send it through workflow for approval, and have the approved changes merged into the existing version without creating a new version or updating the term range.

How to enable Revisions

If your form uses versioning, administrators can enable Revisions in Workflow Settings.

  1. Go to Workflow Settings.
  2. Make sure Allow resubmission of documents to workflow is enabled.
  3. Select Allow revisions of completed documents.

Allow revisions config in Workflow Settings
Once enabled, users with permission to create new versions can also create revisions.

Creating a revision

To propose changes to a completed document:

  • Open the completed document.
  • If you're viewing the version you want to update, click Revise on the right side of the page.
    Revision option
  • To revise a different version:
    • Open the Version dropdown.
    • Select the menu next to the version you want to revise.
    • Choose Propose revisions to this version.
      Proposal Revisions option in version menu
    • Or alternatively you can open the document and click the Revise option in the right sidebar.
  • Make your changes in the draft revision.
  • Submit the revision to workflow for review and approval.

How Revisions Work

You can create a revision from any existing version of a document.

While a revision is in Draft or Workflow, it appears nested beneath the version it was created from in the Version dropdown. This makes it easy to see which version is being updated.

Once the revision is approved, its changes are merged into the selected version. At that point, it no longer appears as a separate revision in the Version dropdown.

Track Revision History

Revision creation and approval are recorded in the document history if History is enabled in Form Settings, providing a complete audit trail of proposed and approved changes.

If your organization uses Time Machine, you can also view what each version looked like at different points in time.

New Feature
4 months ago

New: Version Types and Limit Editability

You can now configure Version Types and Limit Editability to control how users interact with forms based on the type of version they're working on, where the document is in the workflow, or the user's role.

These new capabilities give administrators more flexibility to build workflows that match real-world business processes while protecting important data from unintended changes.

Why This Matters

Not every version of a document should allow the same edits. For example, a protocol renewal may only require updates to renewal-specific fields, while an amendment may allow changes to different sections.

You may also need to limit who can edit certain fields on forms that don’t use document versions. In those cases, you can use Limit Editability to control editing based on your specific process needs.

With Version Types and Limit Editability, you can create more structured editing experiences without building separate forms or workflows.

What You Can Do

  • Create custom Version Types to categorize different types of document updates.
  • Make fields editable or read-only based on the selected Version Type.
  • Control field editability using the Limit Editability configuration on forms with or without document versions enabled. You can limit editability based on workflow status, workflow step, user role, app permissions, and other supported conditions.
  • Utilize Version Types across conditional visibility, workflow branching, limit availability, and limit editability rules.
  • Build more advanced conditional logic using One of the following is true (OR) and All of the following are true(AND) rule groups.

How It Works

Configure Version Types

Enable document versioning in Workflow Settings, then add one or more Version Types that users can choose from when creating a new version of a completed document.  The selected Version Type becomes document metadata and can be used throughout your workflow and form configuration.

Workflow Settings -> Version Types

Configure Limit Editability

Enable Limit Editability on any form gadget to define when a field should be editable or read-only.  Limit Editability supports the same rule builder used for Limit Availability and can evaluate conditions based on:

  • User's role in app
  • User's role
  • Submission's version Number
  • Submission's version type
  • Submission's workflow status
  • Submission's workflow step

Limited Editability Configuration

Unlike standard read-only fields, Limit Editability is enforced at the API level, helping ensure users cannot modify protected fields through integrations or other external methods.  

End User Experience

For forms with versioning enabled, users with permission to create a new version will now see a Create Version panel in the right sidebar of completed documents.  If Version Types have been configured, users select the appropriate Version Type before creating the new version. That Version Type determines how the form behaves based on your configured rules.

Create new version options for end user

If no Version Types have been configured, users can still create a new version using the standard Create Version option.

Important to Know

  • Version Types must be selected when a new version is initially created and cannot be changed afterward.
  • The selected Version Type is available throughout the platform for conditional visibility, workflow branching, limit availability, and limit editability.
  • The Create Version action has moved from the document actions menu to the right-hand sidebar for forms with versioning enabled.
  • Limit Editability takes precedence over the Make individual form sections at this step hidden or editable setting in a workflow step. Even if a section is configured as editable in the workflow, fields within that section will only be editable if they also meet the conditions defined in the field's Limit Editability configuration.
New Feature
4 months ago

New: Resubmit Withdrawn Documents

You can now edit and resubmit withdrawn documents without starting over.

Previously, withdrawing a document was a permanent action. If you needed to make a change and resubmit, you had to either duplicate the withdrawn document or recreate in a new submission and then resubmit.

With this update, withdrawn documents can be reopened, edited, and resubmitted—saving time and reducing duplicate work.

Why This Matters

Sometimes a document is withdrawn because of a small mistake, missing information, or a last-minute update. Instead of creating an entirely new submission, you can now pick up where you left off.

This helps you:

  • Correct errors without recreating your submission.
  • Retain existing form data and attachments.
  • Maintain the document's workflow history.
  • Get updated information back into review more quickly.

How It Works

After withdrawing a document, you can reopen it directly from My Documents.

  1. Navigate to My Documents.
  2. Locate the withdrawn document.
  3. Open the document actions menu.
  4. Select Edit.

My Documents - Edit option in Withdrawn documents

The document will return to a Draft status while preserving the workflow history from the original submission.

After making your changes, submit the document as you normally would.

Important to Know

  • Only the original submitter can edit and resubmit a withdrawn document.
  • The document's workflow history is preserved.
  • Users who no longer wish to continue a submission can leave the document in a withdrawn status.
  • Resubmitted documents follow the normal submission and review process.

Getting Started

The new Edit action is available on all withdrawn documents, past and future in My Documents. If you withdraw a document and later need to make changes, simply click edit, update the information, and submit it again.

New Feature
4 months ago

New: Create Linked Documents Without Leaving Your Current Document

We’re excited to introduce Inline Document Creation, a new way to create and link related documents while you continue working.

This helps users stay in context when they need to connect one Kuali document to another, such as linking a participating site to a protocol or an outside entity to an annual disclosure.

Why This Matters

Users often discover they need to create a related document while completing their current work. Previously, this required leaving the document, creating the related record, returning to the original document, and refreshing the page before selecting it from a lookup field.

Now, form designers can add a + Create New option to supported lookup fields. This lets users create a related document in a modal, then automatically link it back to the document they started from.  

This reduces duplicate data entry, keeps users in their workflow, and makes linking related documents more intuitive.

What’s Changed

Form designers can now enable Allow creating new documents inline on supported Data Lookup (List) and Data Lookup (Multiselect) gadgets linked to Kuali datasets.

When enabled, users with permission to create documents in the linked dataset will see a + Create New option in the lookup dropdown.

+Create New option in lookup

A new document opens in a modal over your current document. Complete and save or submit the new document. Once finished, it will be automatically linked to the original document.

Please note: If the linked dataset contains a Data Lookup field that references the dataset you are currently configuring, an Auto populate source document in destination lookup option will be available. By default, this setting is None, but you can select a lookup field to automatically populate with a reference to the originating document whenever a user creates a new document using + Create New. This creates a two-way relationship between the documents, making it easier to navigate between related records.

New Feature
4 months ago

New: Automatically Populate Editable Form Fields with Data Mapping

We're excited to introduce Data Mappings, a new feature that allows users to automatically populate editable fields in a document using data from a linked Kuali document or other external integration.

This enhancement helps reduce manual data entry, improve data consistency, and streamline workflows that rely on information from other data sources.

Why This Matters

Many processes require users to reference information from another document and then continue working with that data in their current document. Previously, users often had to manually copy information from a linked document or external source into editable fields, which could be time-consuming and increase the risk of errors.

With Data Mappings, administrators can configure mappings that automatically transfer information from the selection a user makes via the lookup into editable fields on the form. Once the data is populated, users can review, update, and continue working with it as needed.

This is especially useful when:

  • Creating documents that build upon information from a previous workflow
  • Pulling data from shared Kuali documents into a new form
  • Reducing duplicate data entry across related processes
  • Improving data accuracy and consistency
  • Allowing imported data to be modified as requirements evolve

What’s Changed

Form designers can now configure Data Mappings on Data Lookup (List) and Data Lookup (Single) gadgets.

Data Mapping Configuration

A mapping defines how data from a linked document is transferred into fields on the current form. When users select a document from a configured lookup field, they can apply a mapping to automatically populate supported fields.

A mapping can also be configured to run automatically when a document is selected via the Apply on change option, creating a more seamless experience for end users.  

To use this mapping, your form must include at least one field that matches the selected source type. If no compatible fields are available, you'll see a warning of "No fields on this form match this source type. Add a compatible field to the form to use this mapping."

Supported Field Types

Data Mappings support a variety of field types, including:

  • Short Text
  • Long Text
  • Rich Text
  • Number
  • Currency
  • Date
  • Data Lookup (List)
  • Data Lookup (Multiselect)
  • Tables containing supported field types
  • Repeaters containing supported field types

This functionality can be used with data from:

  • Kuali Data Sharing
  • Extended Person Fields
  • External integrations with compatible field types

How it Works (for the end user)

When you select a document from a configured Lookup field, you'll see an option to apply an available mapping.

Apply mapping options

If multiple mappings are available, you can choose which mapping to apply. If only one mapping exists, the mapping can be applied directly or automatically, depending on the form configuration.

If the mapping would overwrite existing data, you'll receive a warning identifying the affected fields before the mapping is applied.

Warning on overwriting data

New Feature
5 months ago

New: Batch Actions from Document Lists

You can now take action on multiple documents at once directly from a Document List.

Managing documents one at a time can be time-consuming, especially when you need to clean up records or create copies of several documents. With Batch Actions, you can select multiple documents and complete common tasks in a single step.

What's New?

Document Lists now include selection checkboxes for each document, along with a checkbox in the list header for bulk selection.

Document List - Bulk Actions - Select Documents via checkboxes

After selecting one or more documents, you'll see available actions based on your permissions:

  • Duplicate selected documents
  • Delete selected documents

Select Documents Faster

Use the checkbox in the document list header to select all documents on the current page.

Document List - batch selecting all documents

If your filter returns documents across multiple pages, you'll also have the option to select all documents that match the current filter. The selection count updates automatically so you always know how many documents will be included in the action.

Note: Bulk actions can be performed on up to 500 documents at a time. If you need to process more than 500 documents, complete the action in multiple batches.

Duplicate Multiple Documents

When you choose Duplicate, you'll see a confirmation message showing how many documents will be copied.

Duplicating confirmation message

Because duplicating large numbers of documents can take time, the process runs in the background. You'll receive a notification when duplication begins and another when it's complete.

Duplication message confirmation

Once finished, you can access the new documents from My Documents > Drafts.

Delete Multiple Documents

When you choose Delete, you'll be asked to confirm the action before any documents are removed.

Delete confirmation message

Deleting a document will:

  • Delete all versions of the selected document
  • End any active workflows associated with the document
  • Create an auditable entry in System History

Availability

Batch Actions are available now in Document Lists for users with the appropriate document permissions. Available actions depend on your ability to create and/or delete documents within the dataset.

New Feature
6 months ago

New: Limit Availability and Access-Based PDF Exports

You can now control when fields are visible to users without removing the underlying data, along with new options for controlling how restricted data appears in generated PDFs.

The new Limit availability (sensitive data) gadget setting gives admins more flexibility to manage sensitive fields, workflow-only content, and role-based access in forms. Combined with the new Generate PDF As option for workflow Notification Steps, admins can also control whose access level determines what data appears in attached document PDFs.

Why This Matters

Previously, fields hidden through conditional visibility could also remove stored data when conditions changed. With Limit Availability, field data stays saved in the background while remaining inaccessible until the right conditions are met.  This also applies when exporting the document as a PDF, ensuring restricted data remains hidden from unauthorized users.

We’ve also added new PDF access controls for workflow notifications, allowing admins to control whose permissions determine what data appears in automatically generated PDFs.

This helps you:

  • Protect sensitive information
  • Create admin-only or workflow-only sections
  • Show fields only at specific workflow stages
  • Preserve submission data even when fields are hidden
  • Prevent restricted field data from appearing in exported PDFs
  • Control what data appears in workflow notification PDF attachments based on user access levels

What Changed

The existing conditional visibility setting has been renamed to make its purpose clearer:

  • Old label: Limit visibility based on other gadgets
  • New label: Change visibility based on other fields

This setting still controls field visibility based on form responses.

Change visibility based on other fields config

The new Limit availability setting is separate and focuses on controlling access (based on certain criteria) while preserving data.

Limit availability config options

We’ve also added a new Generate PDF As option for workflow Notification Steps when the Attach PDF of the completed document setting is enabled. This option allows admins to control whose access level is used when generating attached PDFs.

Notification Workflow Step attach PDF configuration

  • Select a user in the Generate PDF As setting to generate the PDF using that user’s permissions
  • If no user is selected, the PDF will use the access level of the first notification recipient. If the notification is sent to a role or group with multiple recipients, the first user in the recipient list will determine the access level used to generate the PDF.

This helps ensure attached PDFs only include information the intended audience is allowed to access.

How to Configure Limit Availability

To enable the setting in an app/product:

  1. Open the Form tab
  2. Select a field
  3. Turn on Limit availability (sensitive data) configuration option
  4. Select Add Condition
  5. Configure one or more conditions

Available conditions

You can make fields available based on the following criteria:

Available criteria in Limited availability

  • User’s role in app — Control field availability based on app permissions.
    Example: Only app administrators can view or edit a section.
  • User’s role — Control field availability based on group membership or assigned roles.
    Example: Only users in the Registrar’s Office Admin role can access certain fields.
  • Submission’s version number — This option appears only when Document Versions is enabled in the form. Use this condition to control field availability based on the document’s version number.
  • Submission’s workflow status — Control field availability based on the current workflow status of the submission.
    Example: Make fields available only while a submission is in Draft or In Progress.
  • Submission’s workflow step — Control field availability based on whether the document is currently editable by the end user. Choose is Form Submission when the document is in the initial draft stage or has been returned to the user for corrections in the Form Fill step. Choose is not Form Submission when the document is in any other workflow state where end-user editing is locked.

Important Behavior Details

  • Data in unavailable fields is still saved.
  • Users must still have permission to access the document through Form Permissions or Conditional Permissions. If they can access the document, fields configured with Limit Availability will remain unavailable until the configured conditions are met.
  • Restricted field data will not appear in exported PDFs for users who do not meet the configured conditions when exporting directly from the document.
  • If you’ve configured PDFs to be automatically attached in a workflow Notification Step, you can choose to generate the PDF using a specific user’s level of access so restricted field data won't be included. If no user is selected, the PDF will use the access level of the first notification recipient.
  • Fields may still appear in the document list, but only administrators can access restricted data there.
  • The workflow step condition intentionally uses simplified options to avoid confusion caused by parallel routing workflows.

When should I use Limit Availability vs. Change Visibility?

Use Limit Availability when you want to:

  • Restrict access to sensitive information
  • Preserve hidden data
  • Control access by workflow or permissions
  • Exclude restricted data from exported PDFs

Use Change visibility based on other fields when you want to:

  • Dynamically show or hide fields based on form answers
  • Create conditional form experiences tied to field responses
New Feature
6 months ago

New: Secondary Workflows

You can now create and run Secondary Workflows to support processes that happen outside your main submission workflow.

This gives you more flexibility to trigger notifications, integrations, or review steps exactly when you need them - without impacting your primary workflow.

Why This Matters

Not every process fits neatly into your main workflow. Secondary workflows let you handle additional steps—like side reviews or system integrations—before, after, or alongside your primary workflow.

What You Can Do

  • Run workflows independently of submission
    Trigger workflows manually from a document or automatically on save—without changing the document’s main workflow status.
  • Support parallel processes
    Run multiple workflows at the same time to manage different business processes in parallel.
  • Keep workflows flexible and reusable
    Create, publish, and version secondary workflows independently from your main workflow.
  • Track workflow activity clearly
    View secondary workflow activity in the Workflow Status / Document History, with indicators for in-progress or error states.
  • Test your workflow against real documents before publishing
    In addition to using the Workflow Simulator to complete a form and preview the workflow path, you can also select an existing document to simulate how the workflow will run in practice.

How it Works

  • Admins can create and manage secondary workflows from the Workflow tab in a form.
  • Once published, workflows can be:
    • Triggered manually from a document.
    • Triggered automatically on save based on defined conditions.
  • Each workflow runs independently and maintains its own history and status tracking.
  • End users will receive and act on workflow steps just like they do today—no additional steps required.

Important to Know

  • Secondary workflows do not change the main workflow status of a document.
  • Multiple workflows can run at once, but the same workflow won’t run in parallel on the same document.
  • To fully understand activity on a document, you may need to review both the main workflow status and any active secondary workflows via Workflow History.
  • A new Active Secondary Workflows column in the Document List helps you quickly identify which documents have workflows in progress.

Getting Started

To create a Secondary Workflow:

  1. Go to the Workflow tab in your form (which defaults to the Primary workflow view), then click the dropdown in the top left to open the Manage Workflows page.
    Workflow tab
  2. Within Manage Workflows, you can create, manage, enable, or disable your secondary workflows. Using the three-dot menu for each workflow, you can also Publish, Rename, or Duplicate the workflow.
    Manage Workflows
  3. Click on +New Workflow (or edit and existing from the 3 dot menu) - name the workflow and select what will trigger this workflow (either manually or if the document is saved with certain criteria):
    New Workflow options in Secondary Workflows
  4. If you selected the A change to a document trigger option, the first step in your workflow will be a Trigger Step, where you can define which field changes or document criteria will trigger the workflow to run. These workflows are triggered when a user saves the document.  You can switch the workflow trigger type between Manual and A change to a document at any time. Continue to build your workflow with the desired steps (more info in the Creating a Workflow article).
    Trigger step in Secondary Workflow
    Note: The 'Limit this workflow to a single execution across all versions of a document' configuration option allows you to limit the trigger to the first time someone saves and that attribute trigger exists; and it won't send again on every subsequent save.
  5. When ready you can validate the secondary workflow using the Workflow Simulator by selecting an existing document to test against or by completing a new document.
  6. Once validated, Publish the draft secondary workflow to make it live for automatic on-save actions or available for app and product administrators to manually trigger from a document.
    Publish draft secondary workflow
  7. Trigger a manual secondary workflow from a document using the menu options available when accessing the document from the Document List.
    Trigger manual workflow

We’re excited to see how you use Secondary Workflows to streamline your processes. As always, we’d love your feedback!

Coming Soon

You’ll soon be able to trigger secondary workflows automatically based on a specific dates or intervals within a document. You will see the greyed-out option of A specific date or interval—these will allow workflows to run automatically on scheduled timing.

Forthcoming option of A specific date or interval

Keep an eye out for an upcoming announcement when this option become available.