1

Allow more and less than 100% Allocation on Tasks

Lindi Gerber

October 15, 2013 12:13

None

Follow

PPO allows you to import a Project Plan successfully where two resources (each with 100 % allocation) are assigned to one task.  

Once imported to PPO, the task is only assigned to the first resource on the MSP plan and reflects a 200% Allocation as it adds the two resources Allocation % together.

When a user then tries to edit the task however, it does not allow you to submit, as the Allocation % is more than 100%. 

The following error message is received:  Allocation % is a % field (1-100 allowed)

We suggest that this default functionality be amended to allow values greater than 100 to be captured through the front end of PPO.

The way the Allocation % is set up currently  does not make sense as a resource is able to work more than 100% of their Standard Working Hours.  

 

 

1 comment

• 0
  
  PPO Development October 15, 2013 13:14

  The error that you are seeing is a front-end validation message which only allows percentage values between 0 and 100 to be captured.  This validation is applied to all percentage fields in PPO, not only % Allocation.

  If we wanted to change this, we would therefore have to allow this for all percentage fields. We would also have to consider the impact of doing this. For example, a user would be able to capture an Actual % Complete on a task as 120%. At the very least this will result in the global filter for completed tasks not working (since it is expecting a value of at most 100%). A value of greater than 100% also does not make sense in this case.

  If we were to allow percentages greater than 100, we would probably also have to implement valid ranges for percentage fields (on the field edit page) so that we can prevent the scenario above.

  I therefore think this issue needs some additional investigation and a general decision on how to handle percentage fields with negative values as well as values greater than 100.