If you are setting up and using exceptions from the audit in u.achieve Self-Service, here is a tip to help you avoid potential issues if you have matching pseudo course names across multiple sub-requirements.
For example, in certain X- and Y-Line scenarios, it is not unusual to use matching pseudo courses across monitored sub-requirements. When you have this situation at your institution, we recommend that you list the X-/Y-Line pseudo after the unique pseudo course.
One of the nice things about exceptions from the audit in Self-Service is that the exception screens find the appropriate pseudo course for you (you don’t have to look them up and enter them as you do in the u.achieve Client). However, it works by taking the first pseudo course it finds in a sub-requirement. If this is not a unique pseudo course name, it will likely cause your exception to behave differently than you expect.
Training To Come…
Next month (December 9-12), we will host the final workshop of 2014 on u.achieve Transfer Articulation. There are still seats left in the Cincinnati training facility, and we’d love to see you there!
Also, we are considering offering a second Intermediate workshop in 2014 in the spring, probably toward the end of April. If you would be interested in this option, please let us know by e-mail to Ch****@Co***********.com.
Got a favorite tip or trick?
Send tips about any of our products to share with your fellow users to Ch****@Co***********.com.
0 Comments