What are the rules to 'outdent' and 'indent' tasks on a project?
search cancel

What are the rules to 'outdent' and 'indent' tasks on a project?

book

Article ID: 35333

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Question:

What are the rules to 'outdent' and 'indent' tasks on a project?

Sometimes we see some 'PRJ' error messages displayed.  How do we manage these errors?

Answer:

Below is a list of a few common errors encountered when attempting to move tasks within the Gantt chart on a project.

If you are creating tasks within MSP, it may allow you to convert some tasks with these characteristics, but then when you save the project back into CA PPM application, you may encounter these issues as well. 

PRJ-07200: One or more of the selected tasks could not be indented or outdented.

This error could occur when selecting more than one task at a time to move using the 'outdent' or 'indent' action.

When you indent tasks under and existing task, that task becomes a summary task.  
 
The following errors could occur when you try to 'indent' a task under an existing task that that has specific properties that prevent it from becoming a summary task.
 

PRJ-07203: Invalid indent. A milestone cannot be turned into a summary task.

This error could occur when you are trying to 'indent' a task under an existing task that is marked as a milestone task.

PRJ-07204: Invalid indent. A task with assignments cannot be turned into a summary task.

This error could occur when you are trying to 'indent' a task under an existing task that already has one or more resources assigned.

PRJ-07210: Invalid indent. A task with dependencies cannot be turned into a summary task. 

This error could occur when you are trying to 'indent' a task under an existing task that has dependencies defined. 

 

It is therefore recommended that before moving tasks around you should ensure that the intended summary task does not have resource assignments, dependencies or is marked as a milestone for use in becoming a summary task. 

Additional Information:

Reference TEC1326624 : Why Effort Task cannot be a Summary Task

 

Environment

Release: ESPCLA99000-13.3-Clarity-Extended Support Plus
Component: