Surpressing sending of task updates when processing timesheet upda

[Doctor Lard]

When processing timesheet updates in PWA (03), on clicking 'Update All',
relevant
schedules are opened in MS Project and the changes are applied. What also
happens is that any pending task updates get automatically sent out (the same
effect as a 'Publish New and Changed Assignments'). Is there any way of
stopping these updates being auto-sent? What I'd like to do issue these
updates selectively (much as you can when choosing 'Publish New and Changed
etc'); not being able to, means a lot of unnecessary updates get sent to
resources - net result being they take less notice of them.
Any clues?
Thanks in advance.
Kev.

 

[elgreenfield]

Email notifications can be configured by the particular user in PWA
when they log on. There is no generic way to do it project wide. it
has to be done on an individual basis.

 

[Dale Howard [MVP]]

Doctor Lard --

First of all, I strongly recommend that your PM's approve and process the
task updates for only ONE project at a time into Microsoft Project. This
will give them much more control over the updates process. Second, after
the PM processes the updates into the Microsoft Project plan, and the system
presents the dialog asking him/her to save the project, he/she should click
the Cancel button. This will stop the automatic publishing of task
assignments and will allow the PM to study the project to determine
precisely which tasks were impacted by the task updates. The PM can study
the Tracking Gantt view and make plan revisions as necessary. When the PM
is ready to publish the project changes, he/she should do this in TWO
distinct steps:

1. Collaborate - Publish - New and Changed Assignments (deselect the
"Notify all affected resources via e-mail" option, if desired)
2. Collaborate - Publish - Project Plan

This will allow the PM to take total control over the updating and
publishing process. Hope this helps.

 

[Doctor Lard]

That's very useful; thank you Dale.
Kev.

Doctor Lard --

First of all, I strongly recommend that your PM's approve and process the
task updates for only ONE project at a time into Microsoft Project. This
will give them much more control over the updates process. Second, after
the PM processes the updates into the Microsoft Project plan, and the system
presents the dialog asking him/her to save the project, he/she should click
the Cancel button. This will stop the automatic publishing of task
assignments and will allow the PM to study the project to determine
precisely which tasks were impacted by the task updates. The PM can study
the Tracking Gantt view and make plan revisions as necessary. When the PM
is ready to publish the project changes, he/she should do this in TWO
distinct steps:

1. Collaborate - Publish - New and Changed Assignments (deselect the
"Notify all affected resources via e-mail" option, if desired)
2. Collaborate - Publish - Project Plan

This will allow the PM to take total control over the updating and
publishing process. Hope this helps.