How it would appear on the form:
Field Types
This article describes the different field types that are can be implemented on forms within Curriculum Management.
Drop-down
Drop-downs show a list of options where only one value may be selected. (Example: Fall, Spring, Summer, etc.). A blank option can be included if needed.
Check-boxes
Checkboxes are a list of options where more than one value may be selected. A common example of this is the selection of a general education designation.
Radio buttons
Radio buttons show a list of options where only one value may be selected. This field functions similarly to the drop-down field, but displays all of the options on the form. The most common use of this field type is for "Yes/No" questions.
Note: If there are a lot options available to select from, we recommend using the drop-down field to reduce the amount of space used on the form.
Text box
A Text box field provides a small 'box' to enter a single line of text.
Note: If more than a line or simple answer is needed, consider using a "Rich text field."
Rich text
The Rich text field is a large text area that supports additional text formatting.
Outcome
The Outcome field allows for multiple individual outcomes to be added to a course or program. These can be initially imported into the system using a CSV file. Please refer to the Course Learning Outcomes Import Guide for more information.
File Upload
File Upload fields allows for the uploading of one or more files to a proposal.
Note: Files will be accessible from the proposal as it moves through workflow and after it is approved, but does not convert to the catalog item or final syllabus.
General Header
General Header is used to create sections by displaying as a large section header on the form. Text will display in all caps and is used to group fields on the form.
Date Picker
The Date Picker enables users to choose dates from a yearly calendar.
Please note: We do not recommend using a date picker field type if the purpose is to modify a system field, as date pickers will not correctly transform to a course field. In these cases, it is best to use a text box.
Course Dependencies
This field auto-populates for change and delete course proposals to inform the submitter of the relationship between the course selected for change or deletion and other course(s). Course dependencies may result from pre-requisite, co-requisite, or cross-listed course(s) relationships. This acts as notification only, just as the catalog warning pop-up does in the catalog system.
Program Dependencies
This field auto-populates on change and delete course forms to inform the submitter of the relationship between the course selected for change or deletion. If the course you are proposing to change or delete is found in a course table in a program, the field will auto-populate programs the course is associated with. This acts as notification only, just as the catalog warning pop-up does in the catalog system.
Nested Field Name/Trigger
Additional questions/fields/statements that appear only if a specific option from a drop-down, radio button, or checkbox list is selected on the form.
Please note: Drop-down and radio button field types can only trigger nested fields based on a single response option (such as "Yes" only or "Other" only). Checkbox lists can allow for nested fields to display as a result of more than one response option.
Nested Field Name: Field/Question(s) that display because of an answer from the previous question.
Answer to trigger nested field(s): Value from Options that triggers nested questions.
Required
Indicates the question is "required" in order to submit the proposal into workflow. This is usually represented by red text "*Required" and disappears when the question is populated.
What to consider:
- A submitter can save a proposal without filling out all of the required field(s).
- Required fields must be filled out before submitting to workflow.
- You cannot make fields required at certain steps.
How this would appear on the final form:
Read Only
On change or delete forms, you may want certain fields to auto populate, but not be editable, these questions are made as Read Only on the form so end users are not able to edit or change the content.
What to consider:
- Field is locked down for editing by any user
- Used in a Change or Delete Course and Program for where data auto populates and should not be changed.
How does this appear:
Character Limit
For rich text and textbox field types, a character limit can be applied. When setting character limits, consider the following points:
- Can only be applied to Textbox and Rich text fields.
- When a character limit is reached, the field will prevent further characters from being typed.
- Student Information System (SIS): If your SIS has a character limit, the corresponding field on the form should likely have one too. For example, a short or abbreviated course title.
- Internal Processes: Internal best practices might dictate certain character limits. For example, a course number should only be 3 or 4 numbers.
Workflow Trigger
Some fields may relate to your workflow. For example, if a course is designated as a general education course, the form may need to go through a special committee for approval. Branches in the workflow must have an associated field on the form to trigger the addition or omission of a step. Only drop-down or radio-button field types can be used as workflow triggers, due to the selection of only one answer.
Notes:
Admins will have access to edit specific fields on the form outlined in the following article: Editing CM Forms
All other revision requests for the form should be submitted to support@watermarkinsights.com.