Go to the U of M home page

Thursday, June 30, 2016

Google account end of life policies

Starting June 2016, student access to email is tied to their “Active” status in Peoplesoft. Students who are active in Peoplesoft have access to email, regardless of their enrollment status.

When students are discontinued by their college, they will continue to have student email access for a period of two years. This access is contingent upon students logging into their student email account at least once every 90 days. Students who do not log in will lose access, but their data will be preserved, and access (and the associated data) can be restored upon request to the IT Help Desk.

Students who have not been reactivated at the expiration of the two year window will lose access to their student email account. However, all data in that account will be preserved and restored when the student is reactivated in Peoplesoft.

Students who do not reactivate beyond the two year window but who have an academic need for continued email access should contact their academic advisor. Advisors may then contact the IT Help Desk to request that email access for the student be extended.

A message titled, “Email: Student Access” has been added to the MyU: Advising Center.

PeopleTools 8.55 and PeopleSoft Campus Solutions 9.2 upgrade

The University has started to plan for the upgrades to both PeopleTools 8.55 in April 2017, and PeopleSoft Campus Solutions (PS CS) 9.2 in 2018.

PeopleTools 8.55 is a prerequisite of PS CS 9.2, and will provide facelifts to the user interface, such as a more contemporary look to different menus and functions. Released in December 2015, PS CS 9.2 delivers new visual guides to help casual users better navigate the system and execute activities more easily. ASR has begun the initial stages of planning for this project. Carrie Otto has agreed to lead the PS CS 9.2 upgrade project.

A rough timeline has been developed by the Administrative Computing Steering Committee (ACSC) and the Operation Advisory Steering Committee (OASC). Visit The Record blog to see the timeline »

May-June 2016

  • Preparation activities: gather, itemize, and familiarization of resources
  • Build project plan details
  • Form teams, organize project

July-January 2017

  • July-August
  • Educate IT staff and gain familiarity of PS9/T8.55
  • Review release notes
  • Release test instance, OIT
  • September-January
  • ASR fit gap kick-off, October
  • Fit gap & priority determinations
  • Review/redesign business process
  • MIDHEUG updates from other schools upgrading

January-April 2017

  • Testing of tools
  • Update documentation for tools
  • Determine tech resources for code, design, and testing

May 2017-February 2018

  • Finalize CS 9.2 design changes
  • Retrofits and coding, developers
  • Testing
  • Training, communication, documentation, and change control

February 2018

  • Go live

Application of Credits for Students Earning Graduate Degrees policy available for public comment

The Application of Credits for Students Earning Graduate Degrees policy (formerly Application of Graduate Credits to Degree Requirements) is now available for public comment on the University’s Policy Library.

There are two significant changes to this policy. One is allowing the use of graduate level courses completed as an undergraduate; previous policy required that all courses be completed post-baccalaureate. The second is the structure of the number of credits required for completion as a degree-seeking graduate student. The revised policy no longer outlines a specific percentage of courses that need to be completed as a University student (previous policy stipulated 60%) and a set number of credits that may be completed in common between two master’s degrees (previous policy was 8 credits). Rather the revised policy stipulates a “core” number of credits that must be completed as a degree-seeking graduate student and the remaining number of credits needed to complete University minimums can be fulfilled by transfer credits, non-degree, and credits in common.

The deadline for comments is Saturday, July 23, 2016. Please take time to review this policy as well as the frequently asked questions. Your feedback will help to provide clarity for where there is concern and assist the Graduate Education Council (GEC) Policy Subcommittee with creating additional FAQs to support this policy.