SOM Portfolio Help

Training and resources for SOM Portfolio

Enhancements

  • Archive icon: All activity entries are able to be archived, which is like a soft delete. We received feedback that this terminology, in the context of activity entries, posed some confusion. To address this, we have updated these buttons to “Delete” and “Hide.” The associated action remains the same. If an activity entry is already imported into the activity table, users can now use a Delete button to perform the soft delete. If using the bulk-import search tool for Publications, and viewing import options, users will have the option to Hide entries they no longer wish to see. Both of these actions, Hide and Delete, are still reversible.
  • Remove unnecessary confirm dialogs: Portfolio has several alert messages throughout the system letting the user know when an action has been successfully executed. A few of these were a bit extraneous, and let a user know when a page had successfully loaded. Since page reloading is a standard action, we have taken out those alerts so as to provide a more efficient experience.
  • Inactive faculty on performance dashboard: If a faculty member has been marked as “Inactive” by an Org Admin, they will be hidden from the evaluation tables on the Performance Dashboard page. Should an Org Admin, Supervisor, or Chair need to review the evaluation, or historic evaluations, of an inactive faculty member for any reason, they have the ability to toggle on “Include Inactive Faculty” from the Performance Dashboard page, and so show those faculty members that are initially hidden.
  • Manage inactive users: Similarly to the Performance Dashboard, Org Admins have the ability to reveal inactive faculty members in the User Management tool. Once marked inactive, faculty accounts will be hidden in User Management. Org Admins will now see an option to “Include inactive users”, which will allow them to see and manipulate records of faculty that are currently marked as inactive.

Bugs

  • Hidden save button on goals: If an evaluation submission was attempted, but then a user went back to add a goal, the Save button on the goal entry pop-up would be hidden. This has been fixed.
  • Max length for goals: If a goal was saved with a description over the max allowable length, Portfolio would display an error message. We have updated this process so that the description field stops accepting text when the character limit is reached.
  • Lecture hours value: We have updated the Lecture Hours field to accept numbers over 4 digits long.
  • Faculty field drop down ordering: Users in a Supervisor, Chair, and Org Admin role have a drop down “Faculty” field on all evaluation pages, allowing them to choose which evaluation to view. We have made this drop down list faculty alphabetically.
  • Supervisor update when evaluation is in completed state: If an evaluation has already been completed (Agreed or Acknowledged), and a Supervisor assignment is updated for a faculty member, the previously completed evaluation comments should not be attributed to them. This behavior was correct in most instances, but we did find and fix one instance where this was not the case.
  • Supervisor decline instant notification: We updated the wording and recipient of this instant notification. Now, if a Supervisor declines the evaluation assignment of a faculty member, the Org Admin of that department is notified directly, and the faculty member is cc’ed.
  • Encoding errors on generated documents: Certain characters used in the Description field of an Appointments activity entry caused unnecessary characters to be added in the text when displayed on a generated document, such as a CV. This has been fixed.
  • Replacing a Chair assignment: It is not appropriate in the Portfolio system to have multiple Chairs assigned to the same department or division. We have updated User Management replace the current Chair if a new one is assigned.
  • Search user hang-up: In User Management, there is a Search User tool to find new users and add them to Portfolio. In some instances, if no data was entered into the search field, but the Search button was selected, the page would enter a state of forever loading. This has been updated.

Leave a Reply

Your email address will not be published. Required fields are marked *