Professional Services Automation Data Dictionary

Utilization__c

Label: Utilization

Field NameField LabelCreated in VersionDescriptionTypeDefault Value
Assignment_Batch_Size__c Assignment Batch Size Pre-Spring 2018 The number of assignments to process in a single batch when calculating utilization

Number(4,0) 100
Batch_Deletion_Cutoff__c Batch Deletion Cut-Off Point Spring 2019 When deleting previous utilization calculations, sets the maximum number of child records above which a batch deletion is used instead of cascading deletion.

Number(5,0) 99000
Calculate_Cross_Products__c Calculate Cross Products Pre-Spring 2018 Allows the calculation of cross product combination of region, practice and group. Such as Region by Practice, or Group by Region

Checkbox false
Calculate_Held_Resource_Request_Time__c Calculate Held Resource Request Time Pre-Spring 2018 If true, calculate the amount of scheduled time for held (unassigned) resource requests.

Checkbox false
Calculate_Summary_By_Role__c Calculate Summary By Role Pre-Spring 2018 Checkbox false
Calculate_Unheld_Resource_Request_Time__c Calculate Unheld Resource Request Time Pre-Spring 2018 Checkbox false
CustomFiltersforUnheldRRUtilization__c Custom Filters for Unheld RR Utilization Pre-Spring 2018 Controls the fields on the Resource Request object to include for utilization calculations of unheld resource requests. This setting accepts field values in SOQL queries. You can add custom Resource Request fields as valid values to this setting. For example, Staffer_Approval_Required__c = true AND Update_Related_Resource_Requests__c = true AND Custom_Approval__c = true. If not defined, unheld resource request utilization calculations use default criteria.

TextArea
Default_Opportunity_Probability__c Default Opportunity Probability Pre-Spring 2018 Percent(3,0)
Deletion_Batch_Size__c Deletion Batch Size Spring 2019 When batch deleting previous utilization calculations, sets the maximum number of utilization calculation records to process per batch.

Number(4,0) 10
Deletion_Child_Record_Batch_Size__c Deletion Child Record Batch Size Spring 2019 When batch deleting previous utilization calculations, sets the maximum number of utilization detail and summary records to process per batch.

Number(4,0) 9000
Historical_UTE_Work_Cal_Start_Day__c Historical UTE Work Cal Start Day Pre-Spring 2018 When true, historical utilization uses the start day based on the work calendar instead of the user's locale.

Checkbox false
Minimum_Opportunity_Probability__c Minimum Opportunity Probability Pre-Spring 2018 Percent(3,0)
Resource_Batch_Size__c Resource Batch Size Pre-Spring 2018 Number(4,0) 20
Resource_Request_Batch_Size__c Resource Request Batch Size Pre-Spring 2018 Number(4,0) 100
Target_Utilization_Approach__c Target Utilization Approach Pre-Spring 2018 For a value of “LAST” only the Utilization Target at the end date of any Time Period is used for the Utilization Detail result for that period, multiplying it with the calendar hours. For a value of “WEIGHTED” (default) between each Resource Change, the effective Target Utilization for each segment between Resource Change is multiplied with the calendar hours for that segment, and the resulting subtotals from each segment are summed (across both Historical and Scheduled periods) to arrive at Utilization Target Hours.

Text(20) "WEIGHTED"
Timecard_Batch_Size__c Timecard Batch Size Pre-Spring 2018 The number of timecards to process in a single batch when calculating utilization

Number(4,0) 100
Timecard_Statuses__c Timecard Statuses Pre-Spring 2018 A comma delimited list of timecard status values that are used to determine which timecards are used for utilization calculations.

Text(255) 'Submitted,Approved'
Uncheck_Master_Based_On_Time_Parent__c Uncheck Master Based On Type/Parent Pre-Spring 2018 Determines whether the "Is Report Master" flag is reset based on the Calculation Type and Parent object (checked) or based on the Utilization Calculation Name (unchecked).

Checkbox false
Use_Last_Date_on_Resource__c Use Start Date and Last Date on Resource Pre-Spring 2018 When true, utilization details do not calculate before the Start Date or beyond the Last Date on the resource.

Checkbox false
Use_Utilization_Engine_TOD__c Use Utilization Engine for Shift Mgmt Pre-Spring 2018 If true, the Utilization Engine is used for calculating utilization with Shift Management. The default is false.

Checkbox false
Use_Utilization_Engine__c Use Utilization Engine Pre-Spring 2018 Checkbox false
Utilization_Engine_Batch_Size__c Utilization Engine Batch Size Pre-Spring 2018 Number(18,0) 25
Utilization_Engine_Max_Range_TOD__c Utilization Eng Max Range Shift Mgmt Pre-Spring 2018 Specifies the number of days into the future to maintain real time utilization data for Shift Management. The default value is 30.

Number(18,0)
Utilization_Engine_Max_Range__c Utilization Engine Max Range Pre-Spring 2018 Maximum number of days into the future for which to maintain real time utilization data

Number(18,0) 365
Utilization_Engine_Start_Range_TOD__c Utilization Eng Start Range Shift Mgmt Pre-Spring 2018 Specifies the number of days prior to the current date to calculate real time utilization data for Shift Management. The default value is 5.

Number(18,0)
Utilization_Engine_Start_Range__c Utilization Engine Start Range Pre-Spring 2018 Defines the number of days prior to the current date to calculate real time utilization data. Set to 0 to start calculation from the current date. The default value is 50.

Number(18,0) 50


© Copyright 2009–2023 Certinia Inc. All rights reserved. Various trademarks held by their respective owners.