Parent-child rollup task calculations

  • Release version: Xanadu
  • Updated August 1, 2024
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Parent-child rollup task calculations

    Parent-child rollup task calculations in ServiceNow enable automatic aggregation of dates, states, and value metrics from child tasks to their parent tasks and projects. This feature ensures that project managers have an up-to-date, consolidated view of task progress, durations, efforts, costs, and states without manual updates to parent records.

    Show full answer Show less

    Key Features

    • Date Rollups: Planned start/end dates, actual start/end dates, and planned duration fields on parent tasks become read-only and automatically reflect the earliest or latest dates derived from child tasks.
    • Duration and Effort Rollups: Summation of planned and actual durations and efforts from all child tasks into the parent task. Actual values roll up only when all child tasks are marked Closed Complete. Actual effort can include time card data if the time card effort update property is enabled.
    • Cost Rollups: When the costing add-on is active, estimated and actual costs of child tasks roll up to parent tasks and projects. Actual costs are derived from expense lines linked to time cards and labor rates, supported by configurable rate models or rate cards. Cost rollups require enabling specific system properties and settings within Project Administration and Cost Management.
    • State Rollups and Roll Downs: Parent task states automatically update based on child task states (e.g., Work in Progress and Closed states roll up). Parent states are read-only to prevent manual overrides. Conversely, changing a project’s state to closed cascades closure to all child tasks, and reopening a project or parent task updates child task states accordingly.

    Practical Considerations for ServiceNow Customers

    • Parent task dates and states are controlled by child task data and cannot be manually edited, preserving data integrity and consistency.
    • Ensure the time card property com.snc.timecard.update.effort is enabled to include time card effort in actual effort rollups.
    • Activate cost rollups by enabling the Enable project cost rollup option and configuring related cost management properties to accurately propagate expense lines and actual costs through task hierarchies.
    • Use the Advanced view on Project and Project Task forms to access expense lines details supporting cost calculations.
    • Understand how state rollups and roll downs work to effectively manage task and project lifecycle states.

    Date changes, stage changes, and value calculations roll up from child tasks to parent tasks.

    • Date changes involve modifying the planned start or end date of a parent task based on those values in child tasks.
    • State changes involve modifying the state of the project record or parent task records when all child records are set to a certain state.
    • Calculations involve summing the values of child tasks and then automatically updating the parent to reflect a new total.
    The following fields change on rollup tasks:
    • Planned Start date: Set to read only for parent tasks. Remains editable for the project record (also considered the top-level task).
    • Planned End Date: Becomes read only.
    • Planned Duration: Becomes read only.
    • Actual Start Date: Becomes read only.
    • Actual end date: Becomes read only.
    • State: Becomes read only.

    Duration Rollups

    Rollups are calculated for the following items:
    • Planned duration and planned effort: the sum of all planned duration and planned effort values for all child tasks.
    • Actual duration and actual effort: the sum of all actual duration and actual effort values. Actual duration and actual effort values are calculated when all child tasks are in the Closed Complete state. Actual effort values can include rollups from time cards.
    Note:
    Verify that the time card property com.snc.time_card.update.effort is enabled. Navigate to System Properties > All Properties to enable this property.

    Cost Rollups

    Cost calculations roll up when the costing add-on is active.
    • Estimated cost: The sum of all cost estimates at the beginning of a project. Estimated costs of child tasks roll up to parent tasks and to the project.
    • Actual cost: By default for the project, the sum of all costs of all the expense lines, and are typically associated with a time card and a labor rate. To track costs, you can derive rates using any of the following options:
      • Associate a rate model to the project.
      • Define rate cards for the task and labor expenses.
      • Associate rate at the resource plan level.

      These rates automatically generate expense lines showing actual expenditures, which are associated with the projects. If rate cards are defined, the task expense lines are generated as each project task closes, and labor expense lines are generated when time cards are approved. Expense lines are visible in the Expense Lines related list, which requires the Advanced view on both Project and Project Task forms.

    To ensure actual costs of child tasks correctly roll up to the project and added to project expense lines, the following must be true:
    • The com.snc.project.rollup.cost property must be set to true. To enable this property, navigate to Project Administration > Settings > Preferences - Project and select the Enable project cost rollup check box.
    • The glide.cost_mgmt.process_task_top_task property must be set to false. Go to the costing properties in the Cost Management application. Check the When creating a task expense line should the system also create expense lines for the task's top task box is not checked.
    • The glide.cost_mgmt.calc_actual_cost property must be set to true. Go to the costing properties in the Cost Management application. Check the For planned tasks types, calculate the actual cost field using the total of expense lines for the task box.

    Project State Rollups and Roll Downs

    Project task states roll up. The state of parent tasks becomes read only, and changes automatically when you change the states of child tasks.
    Project task states can roll up if:
    • The state of the child task is manually changed and there are no other conditions on the parent task.
    • The state of the child task is changed to Work in Progress or Closed. These states roll up to the parent. Pending and Open do not roll up to the parent task.
    Project states can also roll down. If you change the state of a project to closed, all tasks under it change to the default closed value (Closed Complete). If a closed project or closed task is reopened, all tasks under it change as follows:
    • Project or parent changed from closed to Pending or Open: Child tasks change to Open.
    • Project or parent changed from closed to Work in Progress:
      • Child tasks with a Start on date that has passed are changed to start ASAP and the state is changed to Work in Progress.
      • Child tasks with a Start on date that has not yet passed retain the same start on date but the state is changed to Open.