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 Flux users understand how TaskRay Time drives functionality in Flux Capacity.
We recommend you read the Working with a TaskRay Task: What Happens in Flux Capacity article as a pre-requisite for this article.
When a TaskRay Time record is created or edited, the following actions occur in Flux Capacity.
Time Owner & Flux Resource
Flux Capacity will attempt to match the Time Owner to an active Flux Resource based on the Flux Resource Owner. This matching drives reporting for the Flux Resource.
In the example below, you can see the match is made to the Flux Resource User (Stewie Bishop). Based on this match, the “TIME-58” Time log will now contribute to Stewie Bishop’s actual utilization reporting.
TaskRay Time & Flux Schedules
TaskRay Time records rollup to Flux Schedules, which are the cornerstone of Flux Capacity reporting.
When TaskRay Time is logged, Flux Capacity will link the Time record to a Flux Schedule based on a matching date.
For example, when Time is logged on 10/21 against a Task which has a Start Date of 10/21 and Estimated End Date of 10/23, a Flux Schedule will be present to rollup the Time (shown below).
Billable and Non-billable Time
Flux Capacity supports rollups of Billable and Non-Billable TaskRay Time logs. These are captured in separate rollup fields on the Flux Schedule record.
For example, here we see a Flux Schedule that has multiple TaskRay Time logs associated. Actual Billable Time (hrs) and Actual Non-Billable Time (hrs) are calculated separately, along with a complete sum stored in the Actual Total Time (hrs) field.
Special Situations
In some special situations, a Flux Schedule may not be present. Typically this happens when:
- Time is logged outside of the Task’s date range.
- Time is logged by someone other than the Task Owner.
Do not worry, these scenarios are fully supported by Flux Capacity. In these situations, a Flux Schedule is created so the Time rollup can be captured in Flux Capacity reporting.
These “special” Flux Schedules will have the following attributes set:
- Flux Schedule Date = TaskRay Time Date
- Flux Schedule Hours = 0
- The Task’s Estimated Time (hrs) are not distributed to these special Flux Schedules.
- Special Flux Schedules are only present to capture the Time rollup.
- Special Schedule = true
TaskRay Timer
If you are logging time via the TaskRay timer, all of the above actions still apply.
You should note that as soon as the TaskRay timer starts, TaskRay inserts a Time record into the database which is captured by Flux Capacity, even if the timer has not stopped and time has not been officially “saved”. If you do not want abandoned (ie. TaskRay Time Unsaved Time Entry = true) Time records to contribute to Flux Capacity reporting, we recommend that you delete those TaskRay Time records or finish the logging process by saving them with the TaskRay timer.