SilkRoad Logo Print topic
 

Previous Topic

Next Topic

Rollup Considerations

Rollup considerations provide advanced settings that allow setting rollup based on specific status of the activity. By default, all child activities in a cluster are always included in their parent’s rollup unless the activities are not tracked, or the activities do not contribute at all to rollup (i.e., the activity is NOT REQUIRED). Measure Satisfaction if Active is ON by default and the activity rollup is "Always" considered unless the settings here are changed.

Rollup evaluations will not be performed if any child activity has a status of "unknown". This can be problematic when activities are skipped, suspended, or disabled. Rollup consideration settings provide a way to specify more specifically when to include a child activity if it is REQUIRED for Completed, Incomplete, Satisfied, or Not Satisfied status:

  • Always (default): The child activity always contributes to the rollup evaluation of its parent.
  • If Attempted: The child activity contributes to the rollup evaluation of its parent only if it has been attempted.
  • If NOT Skipped: The child activity contributes to the rollup evaluation of its parent only if it is not skipped at the time of the evaluation.
  • If NOT Suspended: The child activity contributes to the rollup evaluation of its parent only if it has been attempted, but NOT suspended at the time of the evaluation.
  • The "Required for Rollup" elements will have no effect on an activity that is explicitly NOT included in its parent’s rollup by defining "Tracked" or "REQUIRED" (Rollup Objective Satisfied and Rollup Progress Completion) to be FALSE.