Find all documentation at https://kuali.zendesk.com or click on 'Back to Homepage' above
Workflow step configuration, such as updating a custom email notification, will now auto-save all updates made by builders, following a similar experience as builders find with our Form Builder.
Users can now expect their changes to be saved without having to remember to click the pesky save button. New updates will be applied live upon publishing application changes.
The Read-only Data (Metadata) Gadget allows you to add information to your form that is uneditable to submitters.
This data may come from three different sources:
Read more about this new feature here and leave a comment here if you have any questions or suggestions!
We're excited to announce the addition of the newest Kuali Build feature: Submissions.
The new enhancement will save countless hours for form submitters who now have a unified view of all form submissions. From this view, submitters can easily view and take action on current and past submissions, including viewing the current approval status of their submission and withdrawing and duplicating previous submissions.
As a reminder: System and app administrators should be aware this new feature redirects form submitters to the 'Submissions' page after a form has been submitted. The only exception to this experience is if the app has enabled "Start a new empty form after each submission" or "Show 'Start new form' button" on the submission confirmation page," in which case the submitter will be taken to those respective pages.
Please check out the documentation to learn more about this feature.
Leave a comment here (or a reaction!) to let us know what you think of this release or any questions you have.
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.
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.
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!
(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:
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.