August 2017 Updates

When creating an outcome, the decision needs to be made by the creator of the outcome if they would like to assess the outcome at their respective level of the organizational tree or assign the outcome downward to another unit to be assessed. When assigning an outcome down the organizational tree the unit making the request would previously never change. For example, if I create an Outcome at Demo University and then assign it to Academic Affairs to be assessed and then Academic Affairs assigns to it the College of Business the request from Academic Affairs looks like it is still coming from the root unit (Demo University).

When assigning an outcome down the organizational tree, the unit making the request would previously never change. For example, if I create an Outcome at Demo University and then assign it to Academic Affairs to be assessed and then Academic Affairs assigns to it the College of Business the request from Academic Affairs looks like it is still coming from the root unit (Demo University). In the link below you can navigate to a video to see how this works in Outcomes currently.

This is not the intended result when assigning outcomes. What should happen is that Academic Affairs should be displayed as the assignee of the outcome to the College of Business, not Demo University. This makes much more sense intuitively and logically, as now a user at the College of Business knows to follow up with the user of Academic Affairs and not the user of Demo University if they have questions.