Hello,
I would like to compute macro planning before the start of a projet. At this step I don't know exactly which resource will be assigned to the activities, but I know the group of resource in the way "one of the resources can work on the subject". So I used the pools of resources for this.
A tricky thing is that I created 3 kinds of pools: the large type corresponding to a team, a medium one for a type of activity (for example debug activity) and a specific one for a specialization. And I want to set the resource without the rate constraint, I want to be able to compute that a resource can work for several pools without rate constraint. So for example one day the resource could work for the activity of the pool1 and the other day the actity for the pool2 etc.
When we try to assign a resource to severa pools at 100% there is a error. But if we assign the resource at 100% and closed, and then unclosed the resource there is no error.
With this workaround, when we calculate the planning the searched beahvior (described before) is working very well.
Does this workaround will always work or does it can be removed?
Regards
Maxime
I would like to compute macro planning before the start of a projet. At this step I don't know exactly which resource will be assigned to the activities, but I know the group of resource in the way "one of the resources can work on the subject". So I used the pools of resources for this.
A tricky thing is that I created 3 kinds of pools: the large type corresponding to a team, a medium one for a type of activity (for example debug activity) and a specific one for a specialization. And I want to set the resource without the rate constraint, I want to be able to compute that a resource can work for several pools without rate constraint. So for example one day the resource could work for the activity of the pool1 and the other day the actity for the pool2 etc.
When we try to assign a resource to severa pools at 100% there is a error. But if we assign the resource at 100% and closed, and then unclosed the resource there is no error.
With this workaround, when we calculate the planning the searched beahvior (described before) is working very well.
Does this workaround will always work or does it can be removed?
Regards
Maxime