Planning and Digital Transformation

Power User Guide

Kuali Build Power Users are shaping the foundation of the automated campus at Fresno State. Creating the processes and workflows for student success and providing students with the resources they need to be successful starts here.

Request to be a Power User

 

The Basics

Before you get started, here are some general terms to remember:

App: An app in Kuali Build contains a form, the form's workflow, and the submitted responses to that form (documents). Unique permissions can be set by the app administrator. The type of access will determine how other users can interact with the app/ Permission types include: 

  • Administer, design, and pubish this app
  • Create documents in this app
  • Read documents in this app
  • Update documents in this app
  • Delete documents in this app

Document: A document is a form that has been submitted. Submitters are able to access their documents and drafts through the My Documents section located on the Home Screen. App administrators can access documents submitted for an app through the My Documents tab located within the app

Spaces: Think of a space in Kuali Build as a folder. Spaces can be used to organize aps by department or organization. A space administrator is assigned to manage permissions and space members allowing departents and organizations to have a private and secure location to design, create, and publish apps.

Role: Roles are what allow us to assign a specific task to users or a collection of users.

Group: A Group is a specific instance of an organization within the hierarchy. Only system administrators have the ability to manage groups. 

Authenticated User:  An authenitcated user is someone who is able to log in to Kuali Build via Single Sign-On. Specific app-sharing permissions can be set for this user type

Anonymous User: An anonymous user is someone who can not log in to Kuali BUild via Single Sign-On. Specific app-sharing permissions can be set for this user type. Please note when sharing an app with an anonymous user integrations can not be used for the form or workflow. 

Drag and Drop: You can click, hold, drag, and drop any of the gadgets or workflow steps into the workspace and move gadgets as needed. 

Configuration: Making changes and updating settings for a gadget on a form or the selected step in the workflow.

 

1. To get started visit: https://fresnostate.kualibuild.com/

 

2. Once you successfully log in, you’ll be redirected to the Kuali Home page.  Screenshot of kuali build home screen

When you first log in to Kuali Build the first thing you will see is the Home Dashboard. This is where all the Apps that you have created and apps that have been shared with you along with Spaces that you are a member of will appear. Please note: what you see on this page is determined by the type of permissions you have. The My Favorites space contains all apps you have favorited. The My Apps space contains all the apps you have created. The Shared with me space contains all apps shared with you. The Home Space includes apps that you have created and apps that have been shared with you.

Let’s Try adding an app to our My Favorites space:


1. Find the desired App located in the Home Space.

2. Hover over the App and click the heart icon that appears.

💡Pro Tip: You can also search for Apps using the search bar located in the Home Dashboard.Screenshot of Kuali Build favorites tab

 

For this portion of the training, we are going to submit a form from our Home Dashboard


1. Locate the Desired App

2. Click on the App to open the form. 

3. Fill out the form and click the Submit button.
 Screenshot of menu. Top choice is "discard" middle choice is "save" bottom choice is "submit"

 

4. After you click submit you will be automatically redirected to the My Documents page.

The Action List is where you will find all the documents that require action from you in a workflow. Think of the Action List as your master to-do list. A notification bubble will appear next to the Action List Label displaying how many items are currently in your action list. You can take action on a form by clicking on an entry to access the document and perform the action. 


In the Action List Dashboard, you will be able to see:

  • The type of document that requires your attention. 
  • The document number of the specified document that requires your action. 
  • The title of the document 
  • The submitter of the document. 
  • The current location of the document in the workflow. 
  • The date that the document was created. 
  • The specified action that is requested of you. Screenshot of Kuali Actions tab menu. Column headers left to right read "Document type" "Document #" "Document Title" "Submitted by" "Workflow Step" "Created on" "Action Requested"

 For this portion of the training, we will be taking action on a document from the Action List: 


1. Navigate to the Action List by clicking Action List. 

2. Click on the entry for the App

3. Review the instructions and complete the action as directed. Shows instructions in an example document within Kuali Build

 

💡Pro Tip: Before submitting, click on the Workflow Status icon to review the status of the form in the workflow. Click on the X or “Hide Workflow Status” to return to the form.  

Shows the kuali workflow status and where to access it

 

4. Select Mark Complete, then add any desired comments and click Mark Complete again to complete the task. 2 screenshots. One is the first menu which top to bottom reads "send back" "save" and "mark complete" which is highlighted. The image on the left says "add comments" with a text box and then "cancel" and "mark complete"

In the My Documents Dashboard, you can refer back to documents that you have submitted or are in the process of submitting. The My Documents dashboard has two sections, Submitted and Drafts, to keep your documents organized and easy to find. 

In the Drafts section, you can:

  • View the name of the form you are working on.
  • View the title number of the form you are working on.
  • View the date you created the draft.
  • View the time elapsed since you created the draft.
  • Click the trash bin icon to delete your draft.
  • Click on an entry to continue filling out the form or submit it. 

In the Submitted section, you can:

  • View the name of the form you submitted.
  • View the document title number on the form.
  • View the date you submitted the form.
  • View the time elapsed since your submission.
  • View the status of the form in the workflow
  • Click on an entry to view the document
Kuali Document tab Menu. Columns headers left to right read " Document type" "Title" "Date Submitted" " Time Elapsed" "Status" "Actions"

If you are filling out a form and wish to save it to complete at a later time, click the Save Button. 

A form in kuali build

 

To access your drafts navigate to the My Documents Dashboard on fresnostate.kualibuild.com. The My Documents Dashboard can be located by clicking My Documents in the navigation bar. 

The kuali build home dashboard

 

Once you are in the My Documents Dashboard you can click the Drafts button to view all your drafts. 

The Kuali Build My Documents Dashboard with the Drafts button highlighted.

 

Click on a submission to view and complete the form. 

The drafts view with a submission highlighted.

 

App Creation

An app in Kuali Build Contains the Form + Workflow + Documents combined into one module. Users must be granted the necessary permissions to create new apps within a space. If you do not see the grey New App icon it indicates you do not have permission to create new apps in that space

The following is the process of how to do so: 

1. Click the grey plus icon labeled New App in a space in which you have permission to create apps

 Kuali Build New app icon. Grayed out plus sign icon

 

2. Name your app. Please not that apps will not be able to share the same name. 

Kuali Name an app menu. Top text box titled "app name" is highlighted

 

3. Choose an app icon and color.

 create an app menu. The "app icon" section is highlighted"

 

4. Click the Create button (the button remains greyed out until requirements are met). create an app menu. "Create" is highlighted

 

Your app has been created! Upon creation, the app will automatically open in the Form Building Tab, where you can begin designing the form for your app. If you are opening an existing app, it will automatically open the Documents Tab, where you can view all the documents that have been submitted for the app. Head over to the Form Building Section of this training guide to start building your form! 

 

Form Building

Any changes you make to the form, workflow, permissions, or app will automatically be saved by Kuali.


WARNING: Do not edit forms and workflows at the same time. You may override each other’s changes. Please notify your team when editing an app. 

 

Gadgets: The fields that you can use to build your form. Kuali Build has four different categories of gadgets: 

  • Layout: Create defined sections
  • Basic: Commonly used form fields.
  • Special: Unique fields and pre-populated selections.
  • Advanced: Fields that use integration to pull data from an external source. 

Form Building Workspace: Drag and Drop gadgets into the center workspace area to begin building your form. 


Gadget Panel: The gadget panel contains all the gadgets available to you to build your form. 


Configuration Panel: The configuration panel is where you can make changes and update settings for individual sections or gadgets. 


Preview: Toggle the switch to preview how your form will look to submitters. Please note: The form can not be submitted, saved, or discarded from the preview. 


Form Settings: Adjust the form ID classification, and default font size, create individual pages out of sections, and set submission settings. 


Drag and Drop: You can click, hold, drag, and drop any of the gadgets into the form building workspace and move gadgets to the desired location as needed. 


Configuration: Making changes and updating settings for the selected gadget 

The gadget panel contains gadgets that you can drag and drop into your form, such as multiple choice questions, read-only text, or section containers (to hold groups of similar questions).

To add a gadget to your form:


Select a gadget.

adding a gadget menu

 

Drag the gadget to the form in the form building workspace. As you drag the gadget over the form, a blue rectangle will highlight to show potential locations for the gadget. Gadgets can go above, below, or next to other gadgets – anywhere on the form.


Drop the gadget in the location you desire.dragging a gadget

 

If you would like to move the gadget to a different place in the form, click and hold the gadget to drag and drop it to a new location.

Any time you’d like to edit a gadget, you’ll work in the configuration panel.

Note: If you make changes to a form in an app that’s already published, these changes will not be live immediately. You will need to re-publish your form for your changes to be live.

In the form preview in the form building workspace, click a gadget you’ve added to your form. The gadget will highlight in blue.

Once you place the gadget in the form, the panel will show configuration options to customize the gadget.

If you don’t see options for your gadget, click the gadget so it is highlighted in blue.

dropdown settings

 

As you change configuration options, the form preview will update automatically.

dropdown setting from form option

 

For a definition of each gadget, you can look at Kuali Build’s Form Builder - Gadget Definitions article.

Each kind of gadget has a different function:

  • Gadgets under "Layout" create spaces and separation throughout your formlayout gadget

 

  • • Gadgets under "Basic" are used to add individual questions and input fields to your form, such as text boxes, checkboxes, and dropdown menus. These fields can be organized within the sections created using "Layout" gadgets.

basic gadget config

 

  • Gadgets under "Special" are similar to basic gadgets, however they have a particular kind of information or interactionspecial gadget example

 

  • Gadgets under "Advanced" are similar to basic and special gadgets, but handles more complicated structures, such as drawing information from another source or containing several pieces of information in one component. These typically also require a more complex configuration than basic or special gadgets. More information about what each specific gadget does can be found in the Capturing Information accordion. advanced gadget exampleadvanced gadget configuration part 1advanced gadget configuration part 2

 

 

Gadget Guide

Layout gadgets are used to separate and organize your workflow. The three gadgets are as follows:

Section: Sections are used to organize content within the form, and can be used to create subsections or break the content into multiple pages rather than having a single, continuous form. Sections are also easily moved around within the form and will move all associated fields with them.

Read-Only Text: Read-Only Text can be used to disclose information within the form - such as additional instructions, or other relevant information that needs to be provided to users - but will not allow users to make any changes to the content within the field.

Read-Only Image: Read-Only Image can be used to display a static image within the form - such as adding logos, instructions, example images, QR codes, etc. to embed in your form.

Basic gadgets will most likely be you most used gadget. Each gadget will ask for one input from the user. These inputs can be typed, multiple choice, or an upload depending on the gadget selected. These gadgets include: 

Short Text

Long Text

Rich Text

Checkbox

Radio Buttons

Dropdown

Date

Time

Number

Email

Link

Currency

Image Upload

File Upload

For more detailed information please visit the Kuali Form Gadget Overview "Basic Gadgets" section: Click here

Special gadgets are similar to basic gadgets, but typically involve more complex inputs.

Country/State/Language: The gadget will provide a list typeahead list.

Signature: The Signature gadget is used to request the eSignature of a form submitter or reviewer during the form submission or workflow processes. Submitters or reviewers have the option to type, draw, or upload an image of their signature.

Table: The Table gadget is used to visually group data on a form into rows and columns. Rows and columns can be labeled, and a variety of gadgets can be used to create the data on the table. 

Repeater: The Repeater gadget will allow admins to group fields together that need to be repeated. When a user is filling out the form they can fill out multiple instances of the repeater field by selecting "add new". 

 

These fields allow you to connect to other data sources. They may require API integrations to be added in Build. Your IT department may be able to facilitate this for you.

Data Lookup (List): The Data Lookup (List) gadget allows the form submitter to select a single item from a dropdown menu or typeahead gadget that can reference information found within Kuali Data (people, groups, or potentially other forms) or from External Data through an integration. 

Data Lookup (Multiselect): The Data Lookup (Multiselect) gadget allows the form submitter to select multiple items from a dropdown menu or typeahead gadget that can reference information found within Kuali Data (people, groups, or potentially other forms) or from External Data through an integration. 

Data Lookup (Single Item): The Data Lookup (Single Item) gadget can be used to automatically fill in additional information on the form based on external data established with an integration.

Submitted By: The Submitted By gadget will pre-populate the field with the name of the person submitting the form. This field requires the form submitter to be logged in.

Read-Only Data: The Read-Only Data gadget can be used to add information to your form that is uneditable to submitters. This information can come from data previously entered by the submitter on the current form, or from the data that is automatically captures on the form behind the scenes (e.g. document number, submission date, submitter’s email address, etc.).

Validation: The Validation gadget can be used to add a form validation under certain criteria (beyond just "A required field is blank") to prevent submission or a workflow action.  Sometimes gadgets require a certain number of responses, or a field is only required if specific data is entered elsewhere in the form (otherwise it's optional), certain lookup selections aren't allowed, etc.  You can set any combination of desired criteria in the Validation rules to trigger when appropriate.validation example

 

Associations: Users often need visibility into how documents are connected across the system.  The Associations Gadget provides a clear view of all documents in the system that reference the document you’re currently viewing.

Virtual Field: The Virtual Field gadget allows you to combine values from other form fields and form metadata into a single read-only value. You can combine multiple variables and add text before or after each variable to control how the final value displays.

 

Configuring a Workflow

After you have created a form in your app, you’re ready to set up an approval workflow. A workflow determines what happens after a form is submitted, such as emailing the department head for approval or notifying the registrar. You can add these steps to a workflow, in any order you might need them:

  • Approval: Require a user to approve the submitted form (stops workflow)
  • Acknowledge: Allows a user to acknowledge that they have viewed a submitted form (doesn't stop workflow)
  • Task: Require a user to perform an action, e.g. add information to PeopleSoft (stops workflow)
  • Notification: Notify a user via email of the submitted form (doesn't stop workflow)
  • Branch: Set up multiple workflows that route based off conditions from the form (e.g. send the approval to the biology department OR TSS)
  • Echo: This step will repeat whatever is nested inside it for each item in a list-type gadget. This includes gadgets like Tables, Repeaters, Multi-selects, etc. 

step options

 

Require a user to approve or deny the submitted form. Approvals will pause all other steps in a workflow until a decision has been made. This step has a built-in default email that automatically gets sent out to the person or group that needs to take action. The default email can be configured and customized

approval

Step 1: Drag and Drop the Approval step to the workflow

drag and drop approval from step menu

 

Step 2: Label the step and select who will approve

  • User(s) specified by a field on the form: This step can be routed to user(s) specified on the form in person, group, or email fields. If you route to an email field, the recipient does not need to have an account in the system
  • A specific person: The recipient specified here will need to have an account in the system
  • A specific external email: The email recipient specified here will not need to have an account in the system
  • A specific role in a group: Roles can include multiple people like a committee

Labeling approval step and selecting who approves\

 

Step 3: Select what happens if the step gets denied. By default, "Do nothing" and then "Stop workflow" will be selected. This will result in the workflow ending. Once the form is approved, the workflow will be completed. The reviewer also has the option to send back the form (this ability can be disabled within the step options).

Default "if denied" sequence

 

Allows a user to acknowledge that they have viewed a submitted form. Unlike an approval, an acknowledgement does not pause the workflow until the document has been reviewed. The workflow process will continue on with any subsequent steps. This step has a built-default email that automatically gets sent out to the person or group that needs to take action. The default email can be configured and customized.

acknowledge

 

Step 1: Drag and Drop the Acknowledge step to the workflow

drag and drop acknowledge step to workflow

 

Step 2: Label the step and select who will acknowledge (You have the same options as you do for the approval step). 

That is it for acknowledgement. The main difference between "acknowledge" and "approve" is that "approve" requires someone to approve or deny before continuing, "acknowledge" allows a user to confirm they have reviewed something without delaying the workflow's progress

Require a user to perform an action, e.g. add information to PeopleSoft. When initiating this task, it will stop the workflow. This step is used to complete a task in or out of the system during the workflow. This step has a built-in default email that automatically gets sent out to the person or group that needs to take action.  The default email can be configured and customized

task

 

After dragging and dropping step to the workflow: 

Step 1: Label the step and select who needs to complete this step (you get the same options as for Approval and Acknowledge)

Step 2:  Give the user instructions as to what they need to do before the workflow can continue in the instructions textbox.

task instructions

Notify a user via email of the submitted form. This step sends out a customized email to a selected user or group. It does not stop the workflow. This is different from other step default notifications (i.e. Approval, Task, or Acknowledge). Examples of uses: customized emails for denied student requests, approved student requests, instructions to the student after a task, or additional notifications that are not pre-built into the steps. 

notification

 

After dragging and dropping to the workflow:

Step 1: Label the notification and select who will receive this notification. The same options are available for who recieves, however you are able to choose more than one person unlike the rest of the steps.

Step 2: Write the notification that will be sent as an email to everyone selected in the previous step. Include a subject and a body.

notification email

This step will repeat whatever is nested inside it for each item in a list-type gadget. This includes gadgets like Tables, Repeaters, Multi-selects, etc. 

echo

 

After dragging and dropping to the worklfow:

Step 1: Label the step and select what list-type gadget will be used for the echo step. For this example we used a repeater.

Echo Configuration

 

Step 2: Drag and drop steps you would like repeated into the echo step.

Dragging and dropping a task into the echo step

 

This step will repeat for as many of the list-type gadgets as exist in the form.

 

Step 3: Configure the step as normal. This step will now run until it has run for all instances within the list.

Configuring a task that will be echoed

Select a step in the Add Steps panel.


 steps options

 

Drag the step to the workflow in the Form Building Workspace. As you drag the step over the workflow, a blue rectangle will highlight to show potential locations for the step. The first step must be the form submission, but otherwise steps can go before or after any other step.

workflow slicked with steps and notification

 

Drop the step in the location you desire. If you would like to move the step to a different place in the form, click and hold the step to drag and drop it to a new location.

workflow notification open

 

Once you place the step in the form, the panel will show configuration options to customize the step.

notification portion open dialog box


Configure the step. You can always change this later. To save your changes, click any blank space in the preview section. The information displayed in the step will update.

configuring notification

 

Deleting a Workflow Step
Important: There is no undo! Workflow steps that are deleted are unrecoverable. 

In the workspace, click a step you’ve added to your workflow. The gadget will highlight in gray.

workflow step

 

Click Delete Step.

delete step


The step will now be removed from the workflow.

 

Your workflow can be more complex than a linear series of steps. A branch step splits your workflow into multiple routes based on how a user responds to a question in the form, leading to different steps depending on a condition. For example, depending on what college a student selects on a form, the form can be routed to that specific office.


Branches consist of a default route, Route 1, and as many other Routes as you add. The default route is the series of steps that will usually run. Each numbered route is a conditional series of steps to potentially run instead.

routes and branches with steps open
 

You can create as many branches in your workflow as you need.

Select the Branch step in the Add Steps panel.

branch step highlighted

 

Drag the branch step to where you’d like it to occur in the workflow.

drag branch step

 

Once you place the step in the form, the panel will show configuration options to customize the branch.

customize branch options

 

Under Route 1, click on the Route Here dropdown menu and select from the options available.

route dropdown menu

 

Then, click the drop down below that. You’ll see a list of questions in your form, as well as metadata Kuali Build has collected about the submission. Choose the question you’d like Kuali Build to branch on.

questions in branch dropdown


After you select a question, you’ll see a progressive series of dropdown menus. Continue choosing options until the condition is complete.

route configuration


You can also create additional conditions or routes by clicking on the gray plus sign or the blue Add Route button respectively.

adding routes and conditions

Some workflow steps require entering specific person(s). For example, the Approval workflow step requires configuration of who will approve the step.

approving step option to assign to person

When you select an option from the list, the search field or dropdown below the options will dynamically update. Click in this search field to choose the specific person(s). You have several options here, including pulling from Fresno State’s directories.

picking and searching for user



User(s) specified by a field on the form: This step can be routed to user(s) specified on the form in person, group, or eail fields. If you route to an email field, the recipient does not need to have an account in the system

A specific role, person, or email: Selecting "Person" allows you to select a person by name, but requires the user to have an account. Selecting "External Email" will allow the email recipient to not need to have an account in the system. A "Role in a group" can include multiple people like a committee

In Kuali Build, you can test the entire workflow. This will not be a live test – emails will not be sent; data integrations and changes such as posting to an API will be mocked but not actually performed. When you test a workflow, you will impersonate various users to see the workflow as that individual.


Toggle the switch on the Workflow Builder screen from Design to Test.

toggle for testing

The workflow simulator will appear. Click Run Test to begin the simulation.

workflow simulator screen

You will see a preview of your form. Click the dropdown next to the Current User to select which user you would like to impersonate. The form will update to reflect what that user will see.

current user highlighted


Fill out the form as you’d like, and click Submit.


Kuali Build will go through each step in your workflow and display a preview of what will happen. For example, if you have a notification step sending an email, Kuali Build will show you a preview of that email. No part of a test is live, the emails are not actually being sent.

email template


To go to the next step in the workflow, click Next. If your workflow contains branches, the test panel will alert you.

parallel routes screen

On a panel for parallel routes, when you click Next, Kuali Build will preview the current route’s steps based on the route logic. You cannot preview other routes because Kuali Build is accurately testing this form submission. To preview other routes, you must submit a new test form answering the form questions appropriately.

parallel route from email


When the test has gone through every step in the workflow (following the appropriate branches), the panel will alert you that the workflow is complete.

workflow complete screen


You can click Start Over to perform another test, go back to the previous step by clicking the Back button, or toggle to Design to continue editing the workflow. You can also click View Status Log to see details of what happened to the form at each stage of the workflow.

workflow status options from complete

 

Publishing and Managing Your App

Now that you built out your form and workflow, it is time to publish the app.


Go to the Publish Tab, next to the Workflow tab 
   publish tab


If there are any errors in the form or workflow they will be listed here  
  publish page


Click the Publish button  
  publish button

 

Click on Share Form
   share form button


 Click Copy in the Shareable Link to From section or highlight and copy the link shown. The Shareable Link to Form (Anonymous) allows you to share your form with users who do not have a Fresno State Single Sign-In. Please note: if your app contains integrations you will not be able to Allow anonymous submissions 
 shareable link

 

You can add this as a link or hyperlink to your website, documents, etc. The link will take them directly to the form 

Wait!! If you haven’t set permissions yet you will want to do that or users will get an error message when they go to the form. To set permissions, check out the App Options section of this training guide.

In order for your Kuali Build app to be sent to production, you must submit a ticket requesting to migrate the app. To do so, follow the following steps

Step 1: Submit a Kuali Build support ticket to TeamDynamix: Click Here

TDX Page to submit a Kuali Build Ticket

 

Step 2: Once you fill out the form and submit, you are done.

submitting a kuali build ticket

 

Now that your app is published, it is time to share your app with your department! 

1. While in your Document Dashboard click the three dots, then click on Permissions.

permissions button

2. In the All Authenticated Users role, check Create Documents in this app.

menu to allow creating docs for all users

 

3. Go to the Add Policy section and type in the name for the policy. Click the Save button. 

   add policy menu

 

4. In the created role permissions, check Read documents in the app and any other permissions you wish to give. 
   giving permission to read documents


5. Your updates will save automatically 
6. Close out the permissions view 
7. Now users are able to start using your app and submitting their forms.

The Documents tab is where app admin and delegates can view, manage, and track documents.

Search bar: Search through submissions based on keywords or phrases
Sort: sort documents by date, document name, submitter name, document number and more
Columns: customize which columns are visible
Views: save and access your customized columns to view later
Export: export submission data for further analysis.
Share: share the submission list with other authorized users.
Data Settings: adjust data displayed preferences and apply custom settings.
New: allows users to submit a new entry directly from the page.
Number: displays a unique identifier for each form submission
Submitted at: shows the date that the form was submitted.
Submitter: shows the name of the person who submitted the form.
What’s your favorite icecream?: displays the submitter’s response to the question.
Confirmation: Displays the the submitter’s confirmed response
Form: A list of submitted forms; click on any form to view additional information and details.
 documents tab options

 

Ad-Hoc Admin Actions on Documents:

 

1. If you are an administrator for the app, you will have the ability to perform ad-hoc actions on individual forms via the workflow status review. Click on a form to access the Skip, Reassign, Resend Notification, or View Step buttons.

admin status review menu


2. Skip: Skip the step in the workflow that the document is currently on and move to the next step. You can add additional comments that will display in the workflow status along with who performed the skip step. 

skipping a step


3. Reassign: Reassign the step in the workflow that the document is currently on to another individual. You can add additional comments that will display in the workflow status along with who performed the reassignment. 

  reassigning a step


4. Resend Notification: Send an additional notification to individuals who have not yet taken action on a current step in the workflow responded to the step in the workflow that the document is currently on. 

5. View Step: View the step configuration in the workflow builder to make adjustments as needed. 

Dashboard: allow users to monitor submission volume, approval times, and bottlenecks

dashboard tab 


Click on the Dashboard tab to view: 

  • Submission for the monthForms in progress
  • Forms completed
  • Form errors
  • Total submissions by status
  • Longest time on the current step
  • Recently Completed or Denied forms 

dashboard page

App Options allow you to set custom permissions for individual apps based on your needs or requirements. You will need to update permissions in order for users to start submitting the form.


PLEASE NOTE: APPS CAN NOT BE PUBLISHED OR SHARED IN YOUR WORKSPACE. ALL APPS MUST BE PUBLISHED AND MADE AVAILABLE FOR SHARING BY A SPACE ADMINISTRATOR.


In this section, we will go over how you can configure the permissions for your app.


1. Next to the app's name, you will see three dots. Click on the dots to open your App Options.  
   getting to permissions


2. Click on Permissions 

permissions button

 

3. You will see four different types of roles:

Administrators: As the creator and owner of this app you will be automatically listed as the app Administrator. You can add multiple users, groups, or roles as needed. Members of this role will have all permissions of the app.
All Authenticated Users: Permissions granted here apply to all users who are able to log in via Fresno State SSO successfully to Kuali Build. You can grant permissions as needed. For this role, we recommend using only the Create documents in this app Permission.
All Anonymous Users: Permissions granted here apply to all users who are not able to log in via Fresno State SSO successfully. These can be users such as external community members or non-Fresno State members. Integrations are not allowed for these forms.
Add Policy (Customized Role): You can create new roles and set permissions as needed


4. Next to each role, you'll see five different types of permissions:

  1. Design and publish this app: This gives the user the ability to make edits to and publish a given app.
  2. Administer this dataset: This gives the user the ability to delete an entire app.
  3. Create documents: This allows the user to submit a form in an app. (Reminder: Completed forms in Kuali Build are called Documents). Usually, this is the permission you want to extend to any end user that you want to fill out a form.
  4. Read documents: This permission gives a user access to read any documents (completed forms) for given app. It also gives the user access to the Document List.
  5. Update documents: This allows the user to make changes to any completed fields in a document (a submitted form).
  6. Delete documents: This allows the user to delete any documents (submitted form) in an app 

Advanced App Options: Data Sharing

You have the option to share data between apps that you are an administrator for. This can be used to pull data from your application into another app. For example: A student fills out their class information on App A and you can share the data to App B. Now form B can use the student's class information from A.


There are three options available:

  1. Do not share data: this is the default selection. Only the current app will have access to the data submitted.
  2. Share with ALL Build apps: please avoid using this app as important information may be shared to all campus users and admins.
  3. Share only with SPECIFIC Build apps: if you are an administrator to another app, you can search and share data between the apps.

 

Making your App Accessible

The goal of accessibility is that every person can access your app equally, regardless of how they’re interacting with it. When you finish creating your app, walk through the steps below and implement every step that you can. Any time you make major changes to your app, check the accessibility again.

~[com[7182 5 5{ "version": 5, "data": {"118dbde138724e5a434faccc74ea75d8":"600","5b66bffa84411a982e0a22b91da7a692":"https://youtu.be/xEgC1NyxRAc?si=G8NGBhSlJUdGTP2B","637b0672b3cb7dbc41ef85bee0e1634c":"Make Your Forms Accessible","c73096ede938de86053203a437967618":"100%"}}]]

When you create your section, give it a short, clear, meaningful label. Section labels tell a user what this section will be about. 

meaningful label shown in form builder


To update a section’s title: 

In the Form Design screen, click the existing section gadget. 

Existing title shown in a form

 

The gadget configuration panel will open. In the Gadget Label/Question section, enter a new clear and meaningful section label.

gadget panel open in section settings

Click anywhere outside of the configuration panel in the form to save your changes.

At the very beginning of your form, add a Heading 1 title and instructions. The title should be a short phrase describing to a user what the entire form is about. The instructions should include any information the user should know before filling out the form, as well as a contact if they need help.

showing a shirt h1 title that is focused and concise

Tip: The section gadget label is not the title! The section gadget label describes this group of question gadgets. The title describes the entire form.

 

To add a title and instructions: 

In the Form Design window, add a Read-Only Text gadget to the very beginning of the first section of your form.

read only gadget selected

 

In the configuration panel for the Read-Only Text gadget, type your title and instructions on separate lines.

Highlight your title. In the text edit menu, click Normal and change your title to be Heading 1.

highlighting where heading can be changed in the toolbar

Note: Be careful to make only your title a Heading 1. The instructions should be normal text.

Click anywhere outside of the configuration panel in the form to save your changes

All text input fields, such as long and short text entry questions, need help text. In Kuali Build, there is no way for the user to identify the input location on Text Entry gadgets, which by default look like this:

Test entry help option empty

 

How does the user answer the question? There is no visible input box, no blinking cursor, and generally no indication of where they should type - or if they even can. Instead, you want to add help text to each text entry gadget:

text entry with help description

 

To add help text to a gadget: 

1. Click a text entry gadget to open the configuration panel.
2. In the configuration panel, toggle on Description/help text.

Description help toggle

3. Enter help text, such as "Click the space below to type your response."
4. Click anywhere outside of the configuration panel in the form to save your changes.

Use description/help text, but don’t display it as a bubble. When adding description/help text, you have the option to display that help text as a bubble. Don't! Here is a comparison:

bubble description opened vs description shown

Why not display the help text as a bubble? A common accessibility aid is a screen reader, which reads the screen to the user. If a person is using a screen reader to aid them in filling out your form, the bubble text is read before the question. For example, if you have help text as a bubble as in the example, the screen reader will read to the user, "Click the space below and enter as format..." THEN it will read "What's your phone number?" It doesn't make sense!

don't check the display help bubble option

 

Use description/help text, not placeholder text. When adding description/help text, you might want to use placeholder text instead. Don't! Placeholder text disappears as soon as the user clicks inside the field. If the field had placeholder text the user needs to reference, they now cannot.

placeholder text options

 

 

Not all gadgets are accessible. A common accessibility aid is a screen reader, which reads the screen to the user. Kuali Build offers a large number of gadget types, but unfortunately, some of these gadgets are not accessible to screen readers and should be avoided. Below is a list of gadgets to avoid and suggested workarounds.


Avoid: Option Range gadget. An option range gadget presents a question to the user and a range of options, such as 1-5. 

option range in menu highlighted

Option range gadget problem 1: With option range gadgets, screen readers do not do not read the gadget label. For example, your gadget might be labeled: "How would you rate us? Choose 1, 2, 3, 4, 5" . You would expect the screen reader to read "How would you rate us?  Choose 1, 2, 3, 4, 5". However, the screen reader will only read to the user "Choose 1, 2, 3, 4, 5". If you're using a screen reader, how will you know what you are choosing 1-5 for? You won't.


Option range gadget problem 2: When the user has finished filling out the form and is reviewing the form before submission, the gadget label is not associated with the answer options. The screen reader will not read, "For the question How would you rate us?, you chose 2." Instead, the screen reader will only read, "You chose 2." What did the user choose 2 for? There's no way to know.


Option Range gadget workaround: You can use a multiple choice gadget to present the same question and offer the same options.

showing menu options to choose multiple choice

Avoid: Rich Text gadget. A rich text gadget is a gadget where the user can enter text that they can add formatting to - making their entered text bold, pink, underlined, cursive, etc. Rich text gadgets have an accessibility issue identical to option range gadgets.

showing rich text in navigation

Rich text gadget problem 1: With rich text gadgets, screen readers do not do not read the gadget label. For example, your gadget might be labeled: "What is your research proposal?" You would expect the screen reader to read "What is your research proposal? Enter text.". However, the screen reader will only read to the user "Enter text". If you're using a screen reader, how will you know what you are entering text for? You won't.


Rich text gadget problem 2: When the user has finished filling out the form and is reviewing the form before submission, the gadget label is not associated with the entered answer. The screen reader will not read, "For the question What is your research proposal?, you entered Exploring Rice Growth in Summer." Instead, the screen reader will only read, "You entered Exploring Rice Growth in Summer." What did the user enter that answer for? There's no way to know.


Rich text gadget workaround: You can use either a short text gadget or long text gadget for the user to enter text.

using short or long text options in nav shown

Avoid: Data lookup (multi-select) Gadget. A data lookup (multi-select) gadget is a gadget connected to a data source, such as a list of all users at the university or a list of all departments, where the user is presented a list of choices and can choose multiple options.

data lookup in navigation

 

Data lookup (multi-select) gadgets problem: With data lookup (multi-select) gadgets, all choices are unlabeled to screen readers, meaning a user cannot review or know what they've already selected. For example, if a user chooses Brian and Susan from the gadget, the screen reader does not read, "You have chosen Brian and Susan." Instead, the screen reader reads "You have chosen Unlabeled and Unlabeled."


Data lookup (multi-select) gadget workaround: You can have many Data Lookup (list) gadgets for as many options as the user may need.

use data lookup list not multiselect gadget shown