Requisitions › Resource Requisition Overview › 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:

• 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 no role can be associated with an OBS all the way up the role and OBS chains, the requisition does not get 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. But everyone with appropriate access rights sees the requisition in their list. For example, 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 different from the current Requested By user, change the Requested By field value to equal yourself. If your company has a routing chain that goes through multiple people, the facility to change is useful.

Only users in the Requested By and Booking Manager fields get notified about 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 details, contact your administrator.