

Resource Requisitions › How to Manage Resource Requisitions › Requisition Routing and Notification
Requisition Routing and Notification
When a requisition is created, it is routed to the appropriate booking manager based on the following logic:
- If a default booking manager is defined for the resource or role. If no default booking manager is defined, then staffing requirement OBS is combined with staffing requirement role to determine the booking manager.
- If a booking manager mapping does not exist for a specific role and OBS, then look up the role chain. If not found, look up the OBS chain until found. Role chain refers to roles that have parent roles. For example, an Automation Engineer can have QA Engineer as a parent role.
- If a role cannot be associated with an OBS all the way up the role and OBS chains, the requisition is not routed.
- Both the project manager (requisition creator) and booking manager (resource manager) are notified of status changes in requisitions. If no booking manager is selected, no notification is sent.
- Users with appropriate access rights can view the requisition in their list by filtering on unassigned requisitions.
- The Booking Manager field can be changed at any time to reflect another resource manager. The facility to change allows resource managers to route the requisitions again.
- The Requested By field value on the Requisition Properties page defaults to the requisition creator. If you are not the current Requested By user, change the Requested By field value to equal yourself. Change this value as needed, especially if your company has a routing chain that goes through multiple people.
- Only the users in the Requested By and Booking Manager fields receive notifications that pertain to open requisitions. Requested and booked resources are not notified. Resource notification happens when the resource is added to the project as a staff participant. The notification can be set to occur automatically when the resource is hard-booked. For more details, contact your administrator.
The following table shows the parties that are notified when the requisition status changes:
|
Requisition Status Changes
|
Requested By
|
Booking Manager
|
|
Created
|
|
|
|
From New to Open
|
Notified
|
Notified
|
|
From Open to New
|
Notified
|
|
|
From Open to Propose
|
Notified
|
Notified
|
|
From Proposed to Booked
|
Notified
|
Notified
|
|
From Open to Book (if requisition, approval is not required)
|
Notified
|
|
|
Booking Manager changes
|
Notified
|
New and old Booking Manager are notified.
|
|
Requested By changes
|
|
|
|
Closed
|
Notified
|
Notified
|
|
Deleted
|
|
|
Notes:
- As a user, you can determine your requisition notification format, message layout, and delivery method from the Account Settings: Notifications page.
- As an administrator, you can set up an automated process to identify the different stages in the lifecycle of a requisition. You can also automatically issue notifications at every stage.
Copyright © 2015 CA Technologies.
All rights reserved.
 
|
|