Users can now duplicate a version of an application, dramatically simplifying the process of building similar applications in the future. Duplicating an app will make a carbon copy of the app and can be customized following.

Read more about this feature here.

Simplify your team’s workflow processes with the new ability to customize the email notification sent out as part of an approval or acknowledge step. 

Builders can now add custom variable fields to these email notification bodies and subject lines, removing the need to add additional email steps as part of a workflow process.

Read more about customizing approval and acknowledge step notifications today.

Users who have previously saved a draft form will now be notified when a new version of the form is available. 

This update will help prevent issues with incorrect data being submitted from out-of-date form submissions, ensuring when a form is submitted, it always follows the latest and greatest your team has published.

The email subject field now allows you to customize variables in the subject line of the notification email that will be sent to your users.  By clicking “Add Variable,” builders can now populate and personalize the subject line with information from the form, such as student name, student ID, or program information.

Learn more about this feature here.

Builders can now specify a default option for users when adding a multiple choice gadget! 

After adding options, a box will show beneath the multiple-choice options in the configuration panel, allowing the builder to select the most common answer they predict form submitters will choose. This feature will automatically select this answer in the form for the user. 

Learn more about this feature here.

Kuali Days, our annual user conference, is an opportunity to learn all you can about how to use Build to its fullest. Our Kuali Build track is taking place from March 8th - 11th and includes over 20+ sessions with your stories, use cases, hands-on training, and ways to connect with each other.

Registration is FREE for the Kuali Build track.  Sign-up for as few or as many sessions as work with your schedule. Space for workshop sessions is limited (and filling up fast) so save your spot today!

Register Now

(And if you need more convincing, Joel, Kuali's CEO, would love to see you there ;):

We have recently made some changes to the Submitted By gadget due to issues being reported in Kuali Build and feedback submitted by customers. 

Some of these issues and feedback include the following. There were some instances where data contained in the gadget did not populate despite the document's metadata holding the correct value. Additionally, customers reported being confused when seeing submittedBy versus meta.submittedBy in notification variable lists and in other areas in the system.

Our hope is that these changes will reduce confusion and streamline the way metadata is used in Kuali Build applications.

We have changed the Submitted By gadget to use the value contained in the metadata. This change prevents issues with the gadget not being populated when data exists. A side effect of this change is that the gadget itself no longer has a data value, which impacts the following scenarios:    

• Conditional Visibility using the Submitted By gadget data will no longer have data to read. Customers will need to update any Conditional Visibility rules to use meta.submittedBy when referencing the submitter moving forward.
• Notifications using the Submitted By gadget data will no longer have data to read. Customers should update variables used in notifications to read off the meta.SubmittedBy data rather than the Submitted By gadget.
• PDFs generated shortly after the fix will have blank Submitted By fields. Moving forward PDFs will generate correctly. Any PDFs that have blank Submitted By fields should be regenerated.
• Anywhere where "Submitter" or "Creator" were listed to refer to the submitter will now read "Submitter - Display Name" in some areas of the system.

We have pushed out fixes for these problems, and with those fixes we have also migrated impacted data to ensure that the correct value shows up throughout customer forms. 

You can read more about these changes here. Please let us know if you have any questions regarding these recent updates.

We've recently made the Workflow Status option available in the Workflow Simulator. When testing a workflow, click the 'View Status Log' button to see the history of a form during the workflow process including step-by-step details of the document's workflow and comments made by reviewers.  

Workflow builders can use this new feature to verify their testing steps, creating an even more seamless experience throughout the testing process.

 Expand form possibilities with the recently released image gadget, empowering users to upload images as part of form submission.  

Our newly released PDF export allows you to now save completed form submissions as PDFs. 

Export form submissions with all submitted information, workflow history, comments, or a combination of any components. In addition, Build administrators can now set up integrations to trigger PDF exports in order to archive forms in campus Enterprise Content Management systems.  

Read more about this feature here.