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 how and when to use the Refresh Resource button on the Flux Resource screen.
Batch Processing
Updates to Flux Resources, Team Members, and Time Away 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.
Refresh Resource
The “Refresh Resource” button gives the Flux Admin the ability to execute a re-calculation of Flux Capacity Utilization, Business Days, Teams, and Time Away for an individual Flux Resource.
This can be a helpful tool if errors are encountered during the processing of Flux Resource changes or in a situation where Flux data is inadvertently modified by a System Administrator or User.
Follow these steps to Refresh a Resource.
NOTE: The “Refresh Resource” button is only available to Flux Admins, those with the Flux Admin permission set.
- Click on the Flux Resources tab.
- Click the Flux Resource Name you wish to refresh.
- On the Flux Resource detail page, click the Refresh Resource button.
- The following modal window will appear.
- The Reset Date defines from which date forward the Resource’s current settings will be applied. By default, the Reset Date is set to today’s date.
- If you wish to refresh Flux Capacity data prior to today’s date, you can specify how far back you wish to go with the Reset Date. A warning message will display to clarify that HISTORICAL DATA WILL BE OVERWRITTEN WITH THE FLUX RESOURCE’S CURRENT SETTINGS as shown below.
Additionally, if the Reset Date selected is outside of your configured Lockout range, a second warning will be displayed. You should always consider the impact on historical utilization reporting when refreshing a Resource outside your lockout range.
- Click Proceed.
Behind the scenes, here is what happens when you proceed with the refresh:
- Flux Capacity gets all Time Away for this resource where Start >= Reset Date
- If the Flux Resource has an associated Time Away Plan, Flux Capacity re-generates the Time Away dates for that plan
- Existing Time Away dates for that plan are removed and replaced with fresh records.
- New Time Away dates are added according to the Time Away Plan dating back to the Reset Date.
- Flux Capacity will also find any remnant (old/inaccurate) Time Away dates related to other plans after the Reset Date and remove them.
- Flux Capacity finds any individual Time Away dates for the Resource and, along with the Time Away Plan dates specified above, collects them for processing.
- If the Flux Resource has an associated Time Away Plan, Flux Capacity re-generates the Time Away dates for that plan
- Flux Capacity finds the current max Estimated End Date for open Tasks owned by the Resource to ensure Flux Utilization records are in place between Reset Date and the max end.
- Flux Capacity gets all Tasks where Estimated End Date >= Reset Date. These records are collected for processing.
- Flux Capacity processes data for missing Flux Utilization records and collects data for additional processing.
- Flux Capacity takes all collected data, from above, and executes the Resource Activation batch process.
- The batch process collects existing Flux Schedules and updates or adds missing records against current Tasks and Time Away owned by the Resource.
- Finally, Flux Capacity upserts Flux Utilization records, then inserts any new Time Away records, then upserts modified/new Flux Schedules.
That’s quite a bit of technical information to absorb! The key takeaway is that this refresh process ensures that all Flux Capacity data for the Resource, dating back to the Reset Date, matches the Flux Resource’s current Utilization, Teams, and Time Away.
Other Helpful Articles
What is a Flux Resource Team Member?
What is a Flux Utilization Record?
Flux Resource Batch Processing and TaskRay Record Locking