Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Resource Management properties

Log in to subscribe to topics and get notified when content changes.

Resource Management properties

The Resource Management application provides several properties to control allocations, schedules, and other settings.

You need the PPS admin role to access the Resource properties.

The properties page is available from the Project Administration > Settings > Properties – Resource module.

Table 1. Resource management properties
Property Description Default value
Maximum number of daily resource allocation records that should be considered in synchronous mode for confirmation and allocation.

com.snc.resource_management.plan.auto_async_threshold

Determines the maximum number of daily resource allocation records that should be considered in synchronous mode during confirmation and allocation. The property improves the system performance when the number of daily allocation records is more than the value set in the property.

The default value is 2600 which implies that the number of daily records considered for confirmation or allocation in synchronous mode is 2600. The value is equivalent to confirming or allocating 10 users on a group resource plan for 1-year duration (260 working days) or 5 users for 2-year duration, and so on. If the group resource plan contains 11 users for 1-year duration, the number of daily records are 2860. Thus the confirmation and allocation of the resource plan in this case is in asynchronous mode.

If you always want to confirm and allocate the resource plan in synchronous mode, set the value of the property to a higher number based on your requirements.

Note: If the property com.snc.resource_management.run_state_changes_async is set to true, the confirmation and allocation of resource plans is always considered in asynchronous mode.
2600
Show Week/Month toggle on resource grid interface

(com.snc.resource_management.show_week_month_toggle)

Shows the toggle button for switching between week and month in the resource grid. Yes
Maximum time duration in Resource Finder in months

(com.snc.resource_management.max_dur_resource_finder)

The maximum duration for which the resource details should be shown in the resource finder. 24
Use budget reference rates to calculate the Resource requested/allocated cost to derive hourly rate from Labor rate cards

(com.snc.resource_management.use_budget_reference_rates)

  • When the property is set to Yes, the budget reference rates [itfm_fx_rate] are used to calculate the resource requested or allocated cost.
  • When the property is set to No, exchange rates [fx_rate] are used to calculate the resource requested or allocated cost. For upgraded customers, the property is by default set to No.
Yes
Maximum number of days for which a resource plan can be created.

com.snc.resource_management.plan.max_duration

Restricts the maximum number of days for which a resource plan should be created. 3660
Default Schedule Name

(com.snc.resource_management.default_schedule)

The schedule on the instance that the Resource Management application uses by default. Resource Management Schedule
If resource_management reporting for a resource/group has value of percentage_allocation less than this value the color will be shown as green.

(com.snc.resource_management.percentage_allocation_normal)

The value that determines when the availability of the resource is shown as green on the resource report. Green signifies that the resource is not being fully utilized and is probably available to have the work allocated. 50
If resource_management reporting for a resource/group has value of percentage_allocation less than this value and greater than the com.snc.resource_management.percentage_allocation_normal, then color will be shown as orange.

(com.snc.resource_management.percentage_allocation_warning)

The value that determines when the availability of the resource is shown as orange on the resource report. Orange signifies the resource does not have much availability. 90
Average Daily FTE Hours/Hours Per Person Day

(com.snc.resource_management.average_daily_fte)

The average daily full-time equivalent in hours or number of hours per person day. This value is used as the equivalent of a full-time day if no value is specified in the Average Daily FTE Hours/Hours Per Person Day field on the user or group resource record.
Note: Capacity is not derived from FTE, but from schedules. Both FTE and schedules must be in synchronization with each other.
8 (hours)
Calendar Event Duration (Minutes)

(com.snc.resource_management.allocation_interval_minutes)

The default duration for a calendar event.

Resource allocations use this property to create allocations with a decimal value.

For example, a user is available for three blocks of time: two 30-minute blocks and one 60-minute block.
  • If the value of this property is set to 30 minutes, and 1 hour needs to be allocated to the user, the allocation is divided into the two 30-minute blocks when the user is available.
  • If the value of this property is set to 60 minutes, the allocation is given to the 60-minute block.
60 (minutes)
First Day of Week (Monday = 1, Sunday = 7)

(com.snc.resource_management.first_day_of_week)

Determines which day of the week is the first day. The resource workbench uses this value to calculate the week number.

For example, a resource is requested from October 14 (Wednesday) to October 21 (Wednesday).

If the value of this property is set to 2 (Tuesday), the allocation is made and presented in the workbench in two blocks:
  • From Wednesday October 14 to Saturday October 15.
  • Tuesday October 20.
1 (Monday)
Perform Resource Confirmation/Allocation/Cancellation in asynchronous mode

(com.snc.resource_management.run_state_changes_async)

Uses asynchronous mode when confirming, allocating, or canceling resource plans to improve application performance.

Because resource confirmation and allocation create calendar events for each resource in a group, and also consider each resources schedule, the confirmation and allocation process can take an excessively long time to complete.

In asynchronous mode, the application uses an event manager to handle errors that might occur when processing the state of the resource plan. If the property is enabled:

  • The state of the resource plan changes to Confirmation in Progress / Allocation in Progress / Cancellation in Progress.
  • If the confirmation, allocation, or cancellation does not work, the Confirm, Allocate, or Cancel UI actions appear so you can reprocess the action. If an allocation is only partially completed, you can click the Allocate UI action again to remove all previously created events for the plan and reprocesses the action.

Enable this property if you encounter errors or longer processing times when handling confirmations, allocations, or cancellations. This might occur if there are more than 25 members in a group or if the duration of the resource plan exceeds 6 months.

No
Comma separated list of resource event types which will be excluded from user's schedule to calculate available capacity and to avoid making resource allocations on the days having these events (time_off, meeting, etc.)

(com.snc.resource_management.exclude_events_from_schedule)

Specifies which events must be excluded for capacity calculations of the resources and when the system must not create events.

The events to be entered must be from the Category field in the time card table.

time_off
Show soft allocations in calendar for com.snc.resource_management.calendar_show_soft_allocations Shows the following options:
  • Resource Managers: When selected, soft allocations can be seen in the calendar by the resource managers only.
  • Everyone: When selected, soft allocations can be seen in the calendar by all users who have the PPS Resource role.
Resource Managers
Number of records fetched at a time in Resource Grid

com.snc.resource_management.number_of_records_to_fetch_at_a_time

The number of records that are fetched in resource grid in one server call.

For example, if there are 100 projects in an allocation board, only 30 are fetched in the first call. When the user scrolls down, a call is made to fetch the next 30 projects. Similarly, when the user expands a project containing, say 100 resource plans, only 30 resource plans are fetched in the first call. Upon scrolling, the next 30 plans are fetched, and so on.

30
Feedback