Student Learning & Licensure Release Notes for March 05, 2024

To enhance the overall user experience and create a more cohesive workflow, we will be transitioning all administrator functionality to Academics & Offices. In April, the following tabs in Classic Admin are scheduled for removal: Standard, Rubric, Template, and Admin. To assist with this transition, we have recently reorganized our help center articles, so that you can clearly identify the resources for Academics & Offices and resources for Classic Admin.

Updated the Bulk Placement Import Logic

With this release, imports in New Placement Management are successfully loaded if no file errors are present. Previously, partial imports were allowed to be successful for rows without errors. This enhanced functionality prevents duplicate record creation when a file has rows that need to be corrected for a successful upload. Now, when a placement coordinator imports placements, the system will verify all rows individually. If any errors are identified, the import process will be paused, and all errors must be addressed in the CSV before the import can proceed. This ensures that the import only takes place once the CSV is error-free.

Updated Errors Messaging for Bulk Placement Import

With this release, in New Placement Management, detailed error messaging will be available. Previously, only row numbers with errors were available; now specific field error messages will be displayed by row, prompting the user to make changes in the appropriate column.

The list of errors:

1. "This is a required field."
   1. <’field name’> is a required field.
      1. Ex; ‘Course Code’ is a required field.
2. "Please enter a valid email format."
   1. Invalid input. Email must be formatted correctly.
3. "Section {group_name}

   does not exist. Please use an existing Section name."

   1. Section could not be found. 
4. "Section member {email}

   's account is suspended. Please use an active user's email address."

   1. Email account has been suspended. 
5. "Section {name}

   is closed. Please use an open section name."

   1. Section has been closed. Only open sections are accepted values. 
6. "Please enter an existing course code."
   1. Course code could not be found.
7. "Please enter an End Date that is after the Start Date."
   1. Unexpected input. End date must occur after the provided Start Date. 
8. "Email does not exist in the current system. Please use existing User email."
   1. Email address could not be found for any users within the provided section. 
9. "Provided Term Code does not exist. Please provide a valid term code."
   1. Term code could not be found. 
10. "Section name, course code, email and term code is required." 
    1. <’field name’> is a required field.
11. "Please enter a valid site id."
    1. Site ID could not be found.
12. "Please enter valid grade levels."
    1. Invalid input. Accepted values are ‘Pre-Kindergarten’, ‘Kindergarten’, ‘1’, ‘2’, ‘3’, ‘4’, ‘5’, ‘6’, ‘7’, ‘8’, ‘9’, ‘10’, ‘11’, ‘12’, or ‘Adult Education’.
13. "Please enter valid section, course,term details and intern." 
    1. <’field name’> could not be found.
14. "Mentors must not be same as supervisors."
    1. Invalid input. Mentor and supervisor must be unique values.
15. "Has common members with other roles in the group."
    1. Invalid input. Mentor and supervisor can’t belong to other roles within this section.
16. "Is too long (maximum is 500 characters)." - valid for notes field
    1. ‘<column name>’ can’t exceed X characters.
17. If a user enters an incorrect email address for a student, the system should display an error message: Email address could not be found for any users within the provided section.
18. For the combination of “Term Code”, “Course Code” and “Section Name” if anyone is mismatched a common error message will be displayed
    1. Invalid Section Details. Confirm that the “Term Code”, “Course code” or “Section Name” fields are correct.

Align category type with parent node categories

The category type of the parent will also be displayed within the category type of the child nodes. This ensures that time log data associated with the parent node's category type is appropriately linked.