S
Steve Scott
I need to be able to group projects in PWA with attributes such as "Project
Code"; "Programme Code"; "Programme Name"; "Director Name" etc but I want to
avoid individual PMs having to continually update all of these in their
plans. Can I for instance have a "nested" arrangement that means when the PM
selects a project code it selects the Programme Code as well? Is it best to
use Outline codes for that? If at a later date the project then comes under
a new programme, can we in the backend make the change or must it be done in
a checked out plan?
Finally if the heirachy of the outline code itself needs to change how does
that affect existing data?
Code"; "Programme Code"; "Programme Name"; "Director Name" etc but I want to
avoid individual PMs having to continually update all of these in their
plans. Can I for instance have a "nested" arrangement that means when the PM
selects a project code it selects the Programme Code as well? Is it best to
use Outline codes for that? If at a later date the project then comes under
a new programme, can we in the backend make the change or must it be done in
a checked out plan?
Finally if the heirachy of the outline code itself needs to change how does
that affect existing data?