You can now configure a Table Gadget as an output in an integration.  This will allow you to pull data via an integration to display in a table gadget on a form.  Tables are now an option to select when configuring an integration output and upon selecting a Table Gadget as an Output you'll need to configure json for the table into the Table Config box:

Here is an example of the format that we would expect when configuring integration data to display in a table and what you would put in the Table Config of the output:.

[  {    "formKey": "N6TZ976AN6",    "id": "a5FD9TgPi",    "label": "Example Number Gadget",    "type": "Number"  },  {    "formKey": "G89eMQD5YY",    "id": "kbo16yrfs",    "label": "Example Text",    "type": "Text"  } ]

This is a flat array of objects. Each object in the array represents a different gadget/column within the table.
Keys breakdown:

formKey: this is the key you'll end up storing the data for this gadget on. Must be unique.
id: Similarly must be unique, this one is more for internal things to work correctly.
label: Optional, this is the text that shows up at the top of the associated column.
type: This must be a valid gadget type (IE: "Text", "Url", "Number", etc).

And in this example, this is how the data should be formatted when you send to our integration services for the integration to read the data correctly.  In this example the returned data is 2 filled out rows. You'll notice that within the first data key is an array of 2 objects. Each of these objects represents a row, and in each row object there's an id key as well as a data key that has a formKey for each of the gadgets you outlined above, followed by an assigned value that is associated with that gadget on that row.

{  "data": [    {      "data": {        "N6TZ976AN6": "42",        "G89eMQD5YY": "First row example"      },      "id": "B8vj6XWz9m"    },    {      "data": {        "N6TZ976AN6": "9001",        "G89eMQD5YY": "Second row example"      },      "id": "_uintwu6RF"    }  ] }

More information can be found in the Outputs section of the Create an API Integration article.

feature 

• Allow form configurer to indicate certain fields that should be cleared when a new version is created.
• New Limit Selectable Dates Configuration Based on Other Date Fields
• New Sort Option for Apps and Products (by Creation Date or Alphabetically)

fix 

• A number of accessibility improvements applied across the platform.
• Fixes a Database related performance issue
• Fixes an issue that prevented documents from updating to a new template version in some situations.
• Fixes issue where attachments couldn't be uploaded in the workflow simulator.
• Fixes an issue that caused an error when uploading files to some documents.
• Fixes an issue that caused an error when files were uploaded to anonymous forms.
• Fixes an issue that caused a delay in some documents appearing in the Document List.
• Fixes an issue where changing a Group name didn't display in Workflow Permissions.
• Fixes a false error that displayed on some Task steps.
• Fixes an issue where users could not enter 0.00 in currency gadgets.
• Fixes an issue preventing Conditional Visibility based on portions of a Group Name.
• Fixes a formatting error in mobile view that caused unintented color overlap with the Edit and Workflow status buttons.
• Fixes an issue when bulk loading data that includes attachments via API.
• Fixes an inappropriate Invalid Data Shape error when chaining Kuali User API calls

For those customers that have Document Versions and have the Allow resubmission of documents to workflow option enabled in the Workflow Settings of a form, you'll now see a new gadget configuration option. Each gadget and section now has the configuration option of Clear field when creating a new version:

There are certain fields that need to be completed on each new version of a document. Examples include questions about a specific amendment, or the transaction type on a new Award. Currently, when creating a new version the user needs to manually wipe these fields out, which can be easily missed. This makes it impossible to validate if a field has been addressed on the most recent version.  Now, when the Clear field when creating a new version configuration is selected and a document in this form or dataset is updated via the 'Create New Version' option the data in the selected field is cleared out automatically. This option is defined by the template the new document version is upgraded to, not the originating version, so the clearing will begin working as soon as a new template is published, even if older documents are not using the template.  

Please be aware of the following:

• This option can be applied to Sections and it will affect all gadgets within the section.
• This option can be applied to a repeater or table and will affect all gadgets within the table or repeater, as well as eliminating all rows in the table or repeater.
• This option can be applied to individual gadgets in a table or repeater and will leave all rows for the table or repeater in place, but will wipe out the impacted fields or section.

We've added an option for end users to sort the tiles on their Kuali portal, individual spaces, or any of the left navigation options, by Create Date or Alphabetically.  To change the sort of the listed apps or products you can select the menu option on the page you're actively on to select the Sort By option.  This will then allow you to sort all apps/products on that page by either Created Date or Alphabetically (the default selection is Created Date):

If you select Alphabetically each category of tiles (Products, Apps, Links) will change order to match the selected option. The browser session will store which selection was made and when a user returns to that space it will continue to display their desired sort.  If they login in a different browser it will display the default sort order.

Additional information can be found in the Navigating Kuali article.

You can now configure a Date gadget to restrict the dates a user can select based on other Date gadgets in the form.  For example, preventing a user from selecting an end date that's before a start date or requiring an event date be between a given project start/end date).

Within the Date gadget the Limit selectable dates configuration now has the option of 'Based on a field'.  Once selected, you can then add logic that this date gadget must fall between other date gadget fields within the form (plus or minus a certain amount of days): 

For example, let's say you have Start and End date gadgets within your form and you want to put in logic to not allow a Start Date to be after the End Date (and vice versa).  First, you would set up the configuration as below for the Start Date (notice you would leave the first criteria blank and only fill out the second between criteria):

Second, you would also configure the End Date field to not be before the Start Date (notice you complete the the first between date criteria but leave the second between criteria blank):

Once configured if a Project Start Date is entered then the user cannot select anything before that date in the Project End Date Field (the options will be greyed out).  The same would be true if you enter the Project End Date first then the user would not be able to select any date after that date for the Project Start Date.

Note: You don't have to set both between date criteria if you don't need to limit based on a secondary date field; like in this example where we only want to make sure the start date is before the end date (and vice versa) we leave either the first or second section blank.  But you could put in both criteria if you want to make sure a date is within two other form date fields (for example, maybe an event date must be within the project start and end date fields).

improvements 

• Unified Spaces System Settings 
• Integrations Now Available in Anonymous Forms 
• Make All Gadgets Available in Workflow Integrations (PLT-1849)
• Accessibility improvements including clearer labels, stronger keyboard navigation, and better contrast and responsive layouts to further align with WCAG 2.2 AA

feature 

• Skip workflow step when group is empty option

fix 

• Fixes issue where unsaved edit banners showed incorrect label text (e.g., “eBd/GN”) in some environments
• Fixes issue where some workflow notifications incorrectly stalled at "Awaiting Response" despite receiving server replies
• Fixes issue where impersonation information was not displaying in the Workflow Status
• Clarifies the message that appears asking for confirmation when discarding document edits.
• Fixes issue where notifications were displaying KUALI BUILD instead of the form title.
• Fixes issue where sometimes fields in a repeater that are hidden by progressive disclosure still triggered submit validation.
• Updates navigation to the Spaces and Settings screen so the user stays in the same space/suite context when entering and leaving the settings screen.
• Fixes issue with some older integrations that disapear if Spaces functionality is turned on.
• Fixes issue where some searches for Groups were not pulling all appropriate results.

Starting today (7/30/2025) the System Settings menu will now allow system administrators to manage their Space Administrators and Space Members, as well as allowing them to manage their existing Links. This change will only impact schools that have not purchased the Spaces functionality - schools that have already purchased the Spaces functionality will not see any change. 

How Does It Work? 

• Schools that have already purchased the Spaces functionality will not see any change. 

• For schools that have not purchased the Spaces functionality but have 1 or more product suites, 

  • System administrators will now be able to manage their Space Administrators and Space Members
  • System administrators will also be able to move items (integrations, links, and apps) between suites and spaces and manage existing links that have been added to their product suites during implementation. 

Please note, if an institution does not have Spaces turned on they will not be able to create new spaces or new links.

You now have the option to add integrations in anonymous forms that point to external data sources.  Please note, you cannot pull information from Kuali Users, Groups, or other App data in anonymous forms for security reasons.  

Once you enable the 'Create documents in this app' permission for All Anonymous Users in App Permissions you'll see that the Advanced Data Lookup gadget options in the Form designer are locked down and must be enabled:

Upon clicking 'Enable' you'll get a warning message alerting you of the risks utilizing integrations in anonymous forms.  It's important to understand that an anonymous form runs without a logged in user. That means that all backend API calls that the anonymous form makes are accessible to anyone on the internet who can determine what those urls are - sensitive data should never be shared in anonymous forms, even in the lookups.

By default, if a workflow step (Approval, Task, or Acknowledge) is set up to use groups, and a group is selected that doesn't have any users configured, the workflow step will go to error.  An app/product admin needs to manually act to keep the document moving through the approval workflow:

Now, if a group option is selected as the recipient within an Approval, Task, or Acknowledge workflow step, you'll have the new 'Skip this step if there are no users in the role' configuration option:

improvements 

• Fully Invisible Sections!
• Add Filter Options Back to Column Headers in Document List
• Updated App Permissions Experience
• Data lookup (Multiselect) improvements

feature 

• New Internationalization Options
• Bypass Workflow Option

fix 

• Fixes issue where GraphQL never finished loading in some circumstances.
• Fixes issue where numbers alway displayed with commas automatically in notifications.
• Fixes issue where in some cases an inappropriate error message displayed when a document was sent back to submitter.
• Fixes issue where integrations with no bearer prefix were going to a 401 error.
• Updates spacing on integration gadgets to match the drop down gadget for consitency.
• Fixes an issue where some screen headers had inadequate contrast in dark mode.
• Fixes issue with some nested paths in integrations.
• Fixes issue where meta.link wasn't properly populating in some integrations.
• Fixes issue where Created by - First Name and Created by - Last Name tokens didn't display in workflow simulator notifications.
• Fixes issues caused by Document list Date/Timestamp filters not shifting for the institution's time zone.