R
Rene
Let say that I want to automate the approbation of the non-
working time actuals on MSP 2002.
We defined our admin project, assign and publish non-
working tasks and wait for team member entering time.
When they (about 400 people) enter their non-working time,
the project manager or resource manager needs to approve
(accept) the time. Doing so, the corresponding MS Project
file is opening in MSP Pro and the time is inserted into
the project. After the insert, MSP Pro ask the
following "Update on this project as been completed. You
should save the project to have the change commited. Do
you wish to save now?".
Is there a way to let MSP Pro automaticaly save and
publish without asking this question ? I would like, as a
PM, to just accept the time in PWA.
(We have a setup of about 11 non-working different tasks
multiply by 9 projects. Each 11 tasks in the 9 projects
are assigned to about 40 users. We split the admin project
in 9 different projects to reduce the number of assigned
people. At the beginning, we had 1 project with 11 tasks.
Each task was assigned to about 400 users. This was way to
long to process... this is way we split it in 9 projects)
working time actuals on MSP 2002.
We defined our admin project, assign and publish non-
working tasks and wait for team member entering time.
When they (about 400 people) enter their non-working time,
the project manager or resource manager needs to approve
(accept) the time. Doing so, the corresponding MS Project
file is opening in MSP Pro and the time is inserted into
the project. After the insert, MSP Pro ask the
following "Update on this project as been completed. You
should save the project to have the change commited. Do
you wish to save now?".
Is there a way to let MSP Pro automaticaly save and
publish without asking this question ? I would like, as a
PM, to just accept the time in PWA.
(We have a setup of about 11 non-working different tasks
multiply by 9 projects. Each 11 tasks in the 9 projects
are assigned to about 40 users. We split the admin project
in 9 different projects to reduce the number of assigned
people. At the beginning, we had 1 project with 11 tasks.
Each task was assigned to about 400 users. This was way to
long to process... this is way we split it in 9 projects)