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!

Announcement
3 weeks ago

Coming Soon: New Features Arriving November 2nd!

Exciting updates are on the way to Kuali! At the end of month, we're introducing new features to help you gain better insights into your data, simplify calculations, and manage permissions with more flexibility.

Here's a sneak peek at what's coming!

📊 Gain Better Insights

Simplify Calculations with Ratios

A new Ratio field and Ratio calculation type will let you enter ratios (like 1:2) and automatically apply them in calculations, helping you get accurate, consistent results.

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

Find Documents Using Table and Repeater Data

You'll soon be able to filter your Document List using values entered in Table and Repeater fields, making it easier to find the documents you need.

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

Make Better Use of Group Data

System Administrators will be able to configure standard fields across Groups, such as an Active status or Institution Unit Number. This information can then be used in forms for reporting and filtering, giving you more ways to organize and understand your data.

As part of this update, the Private Data tab in Spaces & Settings will be renamed System Data.

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

🔐 Stay in Control

Conditional Permissions for People in Tables and Repeaters

Not everyone listed on a form needs the same access. You can now set permissions for users based on a value in each person's row, such as their role, department, or another selection. That way you can keep a complete list for reporting and still control who can view or edit the record.

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

Stay Tuned!

These features are coming November 2nd! Keep an eye out for more details when they're released.

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.

Release Updates
4 months ago

June Release Update

improvements 

  • We've now released Versions and Document History for all Build users. This makes Revisions function detailed below, as well as commenting on document edit available for all Build datasets.

feature 

  • Conditional Editability builds on our recent Limited Availability release, allowing you control when certain fields are editable, and by whom even when a document isn’t in the workflow. This will let you give edit rights to a small portion of a document in Complete status, while reserving full editing rights for your Admins. We've also added more complex indented logic to Limited Availability and Editability as part of this rollout so you can setup different behaviors at different points in a document's lifecycle.
  • Inline Document Creation lets a user create a document right from a data lookup field. This will save your users time, and eliminate the need to jump back and forth between multiple apps when they need to finish a new document before linking it in their current form.
  • Auto Populate Form Fields from a Data Lookup You can now automatically populate editable form fields with data returned from a Data Lookup. This allows users to start with values from a referenced record while still making changes as needed, reducing duplicate data entry and eliminating the need to manually retype information from linked forms.
  • Bulk Action From the Document List Users can now delete or duplicate document in bulk from the document list. This allows users to duplicate all documents in a dataset for the first time, and provide a much more streamlined process for eliminating documents that no longer need to be retained in the system. 
  • Resubmit Withdrawn Documents Users can now make edits to and resubmit documents they have withdrawn from the workflow, allowing them to make necessary changes quickly and keep their documents moving through the process without starting over. 
  • Scheduled Secondary Workflows expands our new Secondary Workflow functionality, allowing you to schedule reminders when a protocol is about to expire, or drive annual form review processes. 
  • Reorder Tables and Repeaters allows users to change the order that records appear in tables or repeaters in their forms. If you need to amend the middle of your IACUC experimental design or change the order of agenda items on a committee agenda you now can with only a few clicks. 
  • Table and Repeater Calculation Footers in Document List adds calculation footers to the document list and makes them available in our Product Dashboard insights. In many cases these are critical reporting values and this expands our out of the box data export to cover a number of new use cases. 
  • Version Types and Limit Editablity allows you 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.
  • Revisions Users can now propose changes directly to existing versions, allowing them to update a version in place rather than creating a completely new one. 

fix 

Forms — filling out & editing:

  • Fixed an issue with the Data Lookup multiselect not working after four selections.
  • Fixed the checkmark/selected state showing incorrectly in the rules multiselect dropdown.
  • Fixed incorrect results when multiplying currency and number fields.
  • Fixed calculations that didn't run (or showed stale values) in view/review mode and in office‑use‑only sections.
  • Fixed an issue with the Person Lookup field showing all options in auto‑filled gadgets.
  • Fixed a currency integration displaying the wrong currency.
  • Fixed person attributes not populating when a person is linked to a document.
  • Fixed section‑level validations that blocked editing a document.
  • Fixed default values for number gadgets not displaying inside repeaters.
  • Fixed integration typeahead fields inside repeaters reverting or clearing their value on save.
  • Fixed a blank edit page when the first section was hidden by conditional visibility.
  • Fixed layout issues in the updated form UI: fields cut off on wide forms, text areas not expanding, and rules formatting.

Submitting, approvals & workflow actions:

  • Fixed inconsistent validation enforcement that could block approval/workflow actions depending on action order or section visibility.
  • Fixed unclear workflow errors (an "undefined" error on denial and a raw "[object Object]" on integration failures) so users now see meaningful messages.
  • Fixed server errors that prevented some users from submitting or opening in‑progress workflow actions.
  • Fixed the Dashboard tab being hidden from app admins and non‑admin users.
  • Fixed the "See details in context" link in document history.
  • Fixed the approval button being unreachable on mobile / narrow screens.

Notifications & PDFs:

  • Fixed external email addresses not being normalized to lowercase, which affected delivery.
  • Fixed workflow "review" buttons not rendering in some Outlook versions.
  • Fixed intermittent failures that prevented notification and reminder emails from being sent.
  • Fixed PDF export/attachment problems: blank or errored attachments, an extra blank page, text cut off at section boundaries, and export timeouts on large documents.
  • Fixed the reminder‑email "Days" field being too small to show two‑digit values.

Documents, versions, lists & exports:

  • Fixed document numbers incrementing incorrectly and duplicate document numbers.
  • Fixed the version filter unexpectedly changing after a search.
  • Fixed the "Apply Edits" button being greyed out on a saved draft.
  • Fixed a plan disappearing after a field was removed from the form.
  • Fixed CSV export failures and an incorrect calculated score in exported data.
  • Fixed versioning issues: errors creating a new version, users unable to see version changes, a date not updating on new versions, and duplicate drafts when updating to the latest form version.
  • Fixed "failed to delete document" and document export failures.
  • Fixed document‑list "Created At" sorting for duplicated documents.
  • Fixed table/repeater data not appearing in the document list and when opening a document via its list link.
  • Fixed dataset records showing a blank label in lookups.
  • Fixed budget summary totals not matching the budget list.

Admin & form‑builder experience:

  • Fixed an undo/redo layout bug in Safari.
  • Fixed permission assignments collapsing until refresh and long group/role names not wrapping.
  • Fixed edit‑comment prompts still appearing when the top‑level history setting was disabled.
  • Fixed rule changes not saving or not showing in view mode.
  • Fixed email‑variable validation incorrectly flagging valid variables as missing/invalid.
  • Fixed a search icon overlapping the search field in groups.
  • Fixed publishing/saving errors: an incorrect "field should not exist" error, a metadata‑field publication error, publish errors not pointing to the right location, a duplicate‑key error blocking further saves, and an echo‑step validation failure.
  • Fixed section description text alignment resetting when "Hide Title Header" was enabled.
  • Fixed blank names showing for service‑role users in the workflow editor.
  • Fixed a missing phone‑number metadata field and inconsistent user‑field behavior in metadata selection.
  • Fixed a crash when searching columns without labels in Data Settings.
  • Fixed workflow‑editor auto‑scroll jumping on large workflows.
  • Fixed a concatenated integration field being unavailable in Data Lookup configuration.
  • Fixed forms failing to save after moving descriptive text.
  • Fixed dark‑mode readability and display issues on the permissions screens.
  • Fixed being unable to scroll the Views list.
  • Fixed an inert placeholder‑text field in the New Rules gadget and delete/ID edits being wrongly exposed on draft forms.
  • Fixed being unable to move apps/products between Spaces.
  • Fixed duplicate echo‑field entries in the workflow variable picker.
  • Fixed preview not honoring the selected version for conditional‑visibility rules.
  • Fixed the form outline export showing internal field IDs instead of labels.
  • Fixed a help tooltip rendering behind the permissions table.
  • Fixed Data Lookup lists not showing both advanced‑settings options.
  • Fixed the catalog navigation builder dropping other curriculum item types when one was added.

Academic Ops - Catalog:

  • Fixed documents approved via Bypass Workflow not publishing, which had hidden them from the catalog.
  • Fixed catalog accuracy issues: in‑progress/denied content appearing, content bleeding in from other catalogs, broken/404 pages, incorrect content, and failed reindexes.
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.

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.