|
Q: What's the difference between a Routing
Group and an Approval Group?
A: An Approval Group is tied to
a UDAK. When an Approval Group has been defined for a given UDAK,
then special approval is required whenever this UDAK is used in
a funding distribution. Any subsequent action on the form affecting
this UDAK will reset the approval group to pending, ensuring that
no action is submitted without the knowledge and approval of the
people in charge of that UDAK.
A Routing Group is similar to a distribution list,
with a twist. When a Pear is routed to a Routing Group containing
user1, user2 and user3, the Pear will appear in the inbox of all
these users. If one user of the group edits and completes the Pear,
it will automatically disappear from all user inboxes.
Q: What's a Pear Officer Routing Group?
A: It is a routing group whose individuals are
the primary Pear Officer and his/her back-up Officers. Routing groups
are visible for all UMS users regardless of their location in the
organization structure. When routing across department or colleges,
the use of Pear Officer Routing Groups ensures that all internal
business procedures are adequately followed in every department
involved.
 Q:
What's the advantage of using Routing Groups as opposed to routing
a Pear to a specific user?
A: When a Pear is routed to a specific user, it
will stay in the user's inbox until processed or removed by the
sender. The user may be absent, or even no longer in charge of the
same job duties. Routing a Pear using Routing Groups ensures that
it will get processed in a timely manner by the appropriate individuals
(person usually in charge, or whomever is set as a back-up). You
also don't need to know who does what within another department.
Pear Officers can easily re-direct the request accordingly. The
use of Routing Groups, especially at the Pear Officer level, ensures
timely transaction processing and leverages the campus-wide resources.
|
