You can now use the same AND / OR grouping options you already know from Document List filters when building Conditional Visibility and Branch Workflow rules.

We’ve added All of the following are true and One of the following is true to form and workflow logic. These options match what’s already available when filtering documents in a form’s Document List, bringing a familiar and consistent way to build complex conditions across the product.

Why this matters

Until now, this type of grouped logic was only available in Document List filtering. In forms and workflows, achieving similar results required nested sections or embedded branches, which made configurations harder to maintain and more error-prone.

With this update, you can:

• Use the same AND / OR pattern from Document List filters in forms and workflows
• Combine multiple conditions at the same level
• Reduce deep nesting in sections and workflow branches
• Keep complex logic easier to read and manage

How to use it

• In a form, turn on Conditional Visibility for a field or section
  
  
• In a workflow, add or edit a Branch step
• Add a rule and choose All of the following are true or One of the following is true
• Add multiple conditions—just like you would when building a Document List filter
  
  

What to do next

No changes are required to existing configurations. However, if you’ve built complex logic using workarounds, you may want to review those forms or workflows and refactor them using this new approach. This can help reduce structural complexity and improve long-term reliability.

This release brings a familiar, proven filtering model into forms and workflows—so you can build powerful logic with confidence and consistency.

improvements 

• Added clarifying language in permissions to better explain how group access is applied
• Improved how Short Text gadgets display longer input to make them easier to read and use.

feature 

• Private data gadget - We’ve introduced a new Private Data gadget that allows admins to securely store and manage sensitive data directly within their apps.

fix 

• Fixed issue with affiliation dropdown being cut off in the permissions view
• Fixed issue with data not clearing when hidden behind limited visibility
• Fixed issue with user not being able to make changes to app or create new documents
• Fixed issue with calculations not working on values in hidden sections in workflow simulator
• Fixed capitalization in section display settings
• Fixed issue with limited visibility field going to a bad state when field is deleted
• Fixed issue with repeater displaying "an error occurred while saving" message
• Fixed issue with acknowledgment request remaining in action list
• Fixed multiple issues affecting attachment and PDF downloads, including errors, file naming changes, and support for special characters in file names

We’ve introduced a new Private Data gadget that allows you to securely store and manage sensitive information—such as Social Security numbers, credit card numbers, and driver’s license data—directly within your apps.  This feature is designed to help institutions meet higher security and compliance requirements while maintaining full visibility and control over who can access sensitive data.

Why this matters

Many institutions need to capture personally identifiable information (PII) but lack a secure, auditable way to do so. The Private Data gadget provides a safe, purpose-built solution that protects sensitive values while supporting everyday workflows.

Key capabilities

• Field-level encryption:  Private Data values are stored separately from other data and encrypted at the field level, adding an extra layer of protection beyond standard platform encryption.
• Flexible masking options:  Control how sensitive values appear throughout the application—including forms, emails, document lists, and PDFs. Choose from full masking or partial masking (such as showing only the last four digits).
• Controlled reveal access:  By default, saved private data is always hidden. Only users with the 'Reveal private data in this app' permission can temporarily reveal values, using a secure, time-limited reveal action.
• Audit-ready by design:  All Private Data activity is logged, including when values are entered, revealed, or when an unauthorized reveal attempt is made—giving you a complete audit trail.
• Security safeguards:  To prevent misuse, reveal actions are rate-limited per user and automatically re-mask after a short period.

Getting started with Private Data

• System Administrators must enable Private Data at the system or app level from Spaces & Settings (or System Settings for non-enterprise customers). By default, Private Data is disabled and set to None. You can enable it for all apps and products or limit it to specific apps and products, depending on your needs.
  
  
• Once Private Data is enabled for an app or product, App Administrators will see the Private Data gadget in the Advanced section of the gadget tray.
  
  
  Once added and published to a form, the field will appear to end users within the document, as shown below. Please note that the show/hide icon is available to the document initiator while the form is in an editable state, as well as to any user with the Reveal private data in this app permission.
  
  
• Within the Private Data gadget, you can configure several settings, including Data Type and Display Style which is specific to private data. The Data Type setting lets you choose between Social Security Number formatting or a generic entry for values such as driver’s licenses or credit card numbers. Display Style controls how the value appears throughout the app—whether it is fully masked or partially masked at the beginning or end of the input, with the option to specify how many characters remain visible.
  
  
• When Private Data is actively enabled in a form (or if a Private Data gadget has ever been published in the app) you’ll see a new Form Permission called Reveal private data in this app. This permission is disabled by default and must be explicitly added to the appropriate policies to allow users to view private data values.
  
  
• Lastly, we've added the below security warning messages when you enable private data from Spaces & Settings and when you add a Private Data gadget to a form to ensure users are aware of the implications.
  
  
  

We’ve improved how Short Text gadgets display longer input to make them easier to read and use.

Previously, longer text could be cut off, requiring scrolling and making the field feel incomplete. Short Text gadgets now wrap and expand to fit their content, keeping the field compact for short entries while remaining readable as text grows.

What this means for you

• Longer text is no longer cut off.
• Text wraps naturally and expands as needed.
• Short Text fields stay clean and compact when input is brief.

No action is required—this update applies automatically wherever Short Text gadgets are used.

Old Short Text Behavior

• Longer text was cut off at the edge of the gadget.
• Users had to scroll horizontally to read full content.
• The field could appear broken or hard to read

New Short Text Behavior

• Text wraps onto multiple lines.
• The gadget expands vertically as content grows.
• All text remains visible and easy to read

improvements 

• Updated currency CSV exports so the format matches what's configured in the currency gadget.

feature 

• Multiple Workflow Notification Recipients

fix 

• Fixes an issue where some calculations in tables were not persisting after document submission
• Fixes headless integrations in tables so they don't display as a blank column.
• Fixes an issue that prevented workflow nodes from being deleted in some apps.
• Fixes an issue with auto save while navigating that caused a loss of some data entered immediately after a user navigated to a new section.
• Fixes an issue where apply edits popover doesn't display when triggered from an unsaved edits alert.
• Fixes an issue that throws some false errors when publishing a form that includes conditional visibility based off of a data lookup field.
• Fixes a formatting error that cuts some read only text off if the Huge font size is used.

We’ve added several new calculation types to the Number and Currency gadgets, giving you more flexibility when working with numeric values in your forms.

These options are available now and can be configured directly when you use the Enable calculations setting in a Number or Currency gadget.  These new options make it easier to perform common calculations directly within Number and Currency gadgets—without needing workarounds or additional fields.

No action is required unless you’d like to start using these new calculation options in your forms.

New Calculation Options:

• Divide - Divides values in sequence, starting with the first number and dividing by each subsequent number.
  • Example: 10 ÷ 5 = 2
  • Results are rounded to three decimal places.
    
    
• Round - Rounds a single value to the nearest whole number.
  • Values with a decimal less than 0.5 round down.
  • Values with a decimal 0.5 or higher round up.
    
    
• Floor - Rounds a single value down to the nearest whole number, regardless of the decimal.
  
  
• Ceil - Rounds a single value up to the nearest whole number, regardless of the decimal.

We wanted to make you aware of an upcoming change to how currency data is returned when accessing Document List CSV exports via the API.

We’ve already updated the frontend so that exporting the Document List as a CSV from the UI includes currency gadget values as currency (for example, dollars). Previously, currency gadgets exported as cents in the CSV (for example, $3.10exported as 310).

What’s changing for API exports

We’re now extending this same behavior to CSV exports accessed via the API.

• The CSV export endpoint is not changing.
• The output behavior is changing from exporting currency values as cents to retaining the actual currency value in the CSV.

We’re sharing this update in advance so you have time to review any scripts, integrations, or processes that consume this endpoint and make any necessary adjustments.

Preview the new behavior

You can preview the new currency format today by adding the useNewCurrencyFormat URL parameter and setting it to true.

Below are example endpoints—replace testhost with your local domain.

Current behavior (exports currency as cents):

https://testhost/app/api/v0/apps/62796f6eb75668508d66a514/62793e95b75668508d663fe8/documents.csv

New behavior (exports currency values):

https://testhost/app/api/v0/apps/62796f6eb75668508d66a514/62793e95b75668508d663fe8/documents.csv?useNewCurrencyFormat=true

Important date

As of February 2, 2026, the CSV export endpoint will default to the new currency format. At that point, the useNewCurrencyFormat parameter will no longer be required.

If you have existing API integrations that consume CSV exports, be sure to update them to handle the new currency output format before this date.

Note: Currency values will continue to be stored as cents in the database. This change only affects how values are represented in the CSV export.

A new workflow enhancement is on the way, and it will make notification setup cleaner, faster, and much easier to maintain—without creating extra stops or complex configurations.

Why This Matters

Some notifications need to reach several different people, like the Principal Investigator, Co-Investigators, a department chair, or a sponsor contact. Until now, you had to duplicate notification stops to include each group. This created large workflows that were hard to maintain and update.

The new Guided Workflow Assignee Experience lets you choose multiple recipient types and multiple recipients within each type from a single notification node. Your workflow stays lighter, easier to read, and much easier to update.

What’s Changing

With the soon to be released guided workflow assignee experience we're introducing a simpler approach. You’ll be able to select multiple recipient types and multiple recipients within each type from a single notification node. No more duplication. 

In Notification workflow steps you'll be able to choose one (or both) of the following path options:

• User(s) specified on the form
• A specific person, email, or role in a group

💡Notice you can now add multiple recipients in each type of user selection option within a single notification.

In Approval, Task, and Acknowledge workflow steps you'll also be asked to chose one of the following paths with a single selection allowed:

• Automate route based on a field on the form
• A specific role, person, or email

Once a path selection is made you'll have additional options to make the desired user selection.

Summary of Changes

• Notification nodes will include new multi-select options so you can configure all recipients in one place.
• Approval, Acknowledge, and Task nodes will shift to a new radio-button layout to keep the experience consistent across node types.
• A streamlined UI: Recipient options will move from drop-downs to checkboxes or radio buttons.

That’s it—no more duplicating stops or syncing changes across multiple nodes.

Some things you can do to prepare:

• Review any workflows with several duplicated notification stops; these will be easier to consolidate once the update arrives.
• Plan for a lighter configuration experience—your teams will no longer need to manage multiple nodes for the same message.
• If you maintain internal documentation or training materials, you may want to note that recipient selection will change from dropdowns to the new selection controls.

This update is being rolled out next week and if you’d like feedback on your configuration design or help identifying workflows that may benefit from this update, feel free to submit a support ticket!

improvements 

• Removed "unsaved edits" alert when discarding edits 
• Close proposal modal when applying edits after exiting document

feature 

• Data Lookup based on a Table, Repeater, or Data Lookup (Multiple)

fix 

• Fixed issue with proposal getting stuck after being reassigned
• Resolved issue with a blank page appearing at the front of the pdf 
• Fixed issue with search searching more than the active frame on document modals
• Fixed issue with CSV failing to export
• Fixed issue with actions pop ups not being responsive
• Fixed issue with approval going to an error page when opening from action list 
• Fixed issue with approvers not able to download files in their action records 
• Fixed issue with proposals showing they are in draft despite being submitted to workflow 
• Fixed issue with users not being able to scroll through documents
• Fixed issue with duplicate steps appearing in action list 

You can now populate a Data Lookup (List) or Data Lookup (Multiselect) gadget using values pulled directly from a Table, Repeater, or Data Lookup (Multiselect) gadgets on the same form or a shared form. 

Sometimes a field needs to pull from options entered elsewhere on the form or brought in through an integration. With this update, you can choose the source gadget, pick the field you want to use as the selectable value, and the lookup will show those entries as typeahead options when someone completes the form. 

💡Why it matters

This lets form designers build smarter, more connected forms so when a user enters data into a Table, Repeater, or Data Lookup (Multiselect), those values can instantly become selectable options elsewhere in your form. It’s helpful anytime users need to choose from information already captured—for example, selecting a species listed on a protocol for a procedure, or choosing an approved species from a linked protocol when submitting an animal order.

⚙️ How it works

Form designers can now:

• Add a Data Lookup (List) or Data Lookup (Multiselect) gadget onto the form. 
• For Data Source - select This Form or Kuali Data (to select another shared form) 
• Choose the field from the repeating dataset (Table, Repeater, or Data Lookup (Multiselect) you want to use as the typeahead value, then click Continue.
  
  
• And if you are configuring a Data Lookup (List) select the other fields that should be available as Data Linked gadgets.  And if you want to pull any available fields onto the form turn on the Add linked auto-filled gadgets option in your configuration and drag the available fields onto your form.
  
  

End users will see the below in the form once the lookup is configured:

• The options available for selection are prefilled from data already entered elsewhere on the form (or shared form):

• Please note, if no data has been entered in the linked data source the user will see the below message for the field indicating no data is available from the selected source: