Important 
This article covers legacy Flux Capacity functionality.
- If you are in the beginning stages of setting up resource management functionality in your org, or if you are already using TaskRay Resource Management features, refer to the new Resource Management documentation.
- If your organization currently uses Flux Capacity for resource management, use this article if you need to get information on Flux functionality.
This article helps a Flux Admin understand the changes triggered when editing Flux Resources and their associated Team Members.
Batch Processing
Updates to Flux Resources and Team Members described in this article have the potential to trigger massive data operations to initialize or re-calculate Flux forecast data. Processing of these operations is accomplished via queued batches to help Flux Capacity handle enterprise data volumes while operating within Salesforce's governor limits.
Refer to this article for more details on batch processing and recommendations to perform these Flux Admin changes outside of normal business hours.
Resource Edits
| Setting Changed | Historical Records | Future Records |
|
Made Active |
Flux Schedules are established for all assigned TaskRay Tasks where End Date >= TODAY and all assigned Flux Time Away records where Flux Time Away Start Date >= TODAY. Flux Utilization records are established starting on the earliest Start Date for an assigned TaskRay Task where where End Date >= TODAY AND Archived = false, unless that date is after TODAY or there are no tasks that meet this criteria, in which case records are established beginning the day a Resource is Activated. |
Flux Schedules are established for any assigned TaskRay Tasks with an End Date >= TODAY. Flux Utilization records are established for all active Team Members through the furthest future assigned TaskRay Task in your org. Using that Task’s End Date* + the number of days specified in Flux Global Settings custom setting “Flux Utilization Future Range” (90 days by default). *MAX(TASKRAY__Deadline__c) FROM TASKRAY__Project_Task__c |
|
Made Inactive |
Flux Utilization and Flux Schedule records for prior dates remain as-is. |
Flux Utilization and Flux Schedule records for all Team Members will be removed/deleted from the day after the edit forward. As a result, some Tasks may end up missing Flux Schedules for their entire duration (ie. Tasks with Start Date before deactivation and End Date after deactivation). |
|
Name |
Record name on all Flux Team Members & Flux Utilization records, today forward, are updated to include Resource’s new name. |
|
|
Utilization Settings |
Flux Utilization and Flux Schedules records for prior dates (if present) remain as-is. |
Billable/non-billable utilization targets will be re-calculated on all Flux Utilization records from the day of the edit forward. Additionally, if the Daily Total Utilization Target is changed, Flux Schedules for future Time Away will be re-calculated with a refreshed capacity deduction rolled up to parent Flux Utilization records. |
|
Business Day Settings |
Flux Utilization and Flux Schedule records for prior dates remain as-is. The only exception would be for open Tasks with a date range in the past. For Tasks still open, the entire set of Flux Schedules is recalculated to accommodate new daily allocations. |
Flux Schedules for all open and future Tasks are re-calculated based on the new business day settings. Refreshed schedule hours are rolled up to parent Flux Utilization records. |
|
Flux Time Away Plan Added (previously blank) |
Flux Utilization and Flux Schedule records for prior dates remain as-is. Past dates in the new Time Away Plan are not added to the Resource. |
Time Away records are created for the Flux Resource for all future approved Time Away dates in the new Time Away Plan. Flux Schedules are created for each active Team Member for those Time Away dates. Flux Schedules related to in-progress Tasks that overlap with these Time Away dates are also recalculated. New capacity deductions are rolled up to parent Flux Utilization records. |
|
Flux Time Away Plan Changed (from one plan to another) |
Flux Utilization and Flux Schedule records for prior dates remain as-is. Previously established Time Away remains even though it may be part of the Resource’s old Time Away Plan. |
Time Away records and related Flux Schedules are deleted from the Flux Resource for all future Time Away dates in the old Time Away Plan. Time Away records are created for the Flux Resource for all future approved Time Away dates in the new Time Away Plan. Flux Schedules are created for each active Team Member for those Time Away dates. Flux Schedules related to in-progress Tasks that overlap with these Time Away dates are also recalculated. Re-calculated capacity deductions are rolled up to parent Flux Utilization records. |
|
Flux Time Away Plan Cleared (previously populated) |
Flux Utilization and Flux Schedule records for prior dates remain as-is. Previously established Time Away remains even though it may be part of the Resource’s old Time Away Plan. |
Time Away records and related Flux Schedules are deleted from the Flux Resource for all future Time Away dates in the old Time Away Plan. Flux Schedules related to in-progress Tasks that overlap with these Time Away dates are also recalculated. Re-calculated capacity deductions are rolled up to parent Flux Utilization records. |
Team Member Edits
| Setting Changed | Historical Records | Future Records |
|
Made Active |
Flux Schedules are established for all assigned TaskRay Tasks where Flux Team matches the Team Member's Flux Team and End Date >= TODAY, and all assigned Flux Time Away records where Flux Time Away Start Date >= TODAY. Existing Flux Schedules for Time Away related to other existing, active Team Members are recalculated based on changes to Team Allocation. Flux Utilization records are established starting on the earliest Start Date for an assigned TaskRay Task where Flux Team matches the Team Member's Flux Team AND End Date >= TODAY AND Archived = false, unless that date is after TODAY or there are no tasks that meet this criteria, in which case records are established beginning the day a Team Member is Activated. |
Flux Schedules are established for any assigned TaskRay Tasks with an End Date >= TODAY. Flux Utilization records are established for the Team Member through the furthest future assigned TaskRay Task in your org. Using that Task’s End Date* + the number of days specified in Flux Global Settings custom setting “Flux Utilization Future Range” (90 days by default). |
|
Made Inactive |
Flux Utilization and Flux Schedule records for prior dates remain as-is. |
Flux Utilization records for the de-activated Team Member will be removed/deleted from the day after the edit forward. If Resource remains active, Flux Schedules will be re-established for an active Team Member that matches a Task’s Flux Team lookup, or the Primary Team Member if no match. |
|
Primary Changed |
Flux Utilization and Flux Schedule records for prior dates remain as-is. |
Flux Schedules are re-established for any TaskRay Task with an End Date >= Today AND a Flux Team lookup that did not match the old Primary Team. These Flux Schedules are pointed at the new Primary Team Member. Re-calculated schedule hours are rolled up to parent Flux Utilization records. |
|
Percent Allocation to Team |
Flux Utilization records for prior dates (if present) remain as-is. |
Percent Allocation to Team will be refreshed and utilization targets will be re-calculated on all Flux Utilization records from the day of the edit forward. Additionally, Flux Schedules for future Time Away will be re-calculated with a refreshed capacity deduction rolled up to parent Flux Utilization records. |