email notification when saving a project

P

patcav33

Is there a way to set up an email notification for when a project is
saved that would go to a specific person (not a resource that has
tasks assigned)? for example, on some projects, we may have more than
1 project manager going in and making changes. they want to get an
email (sent or received) when the project is saved notifying the other
project manager that changes have been made.

this is different than having the notifications turned on for tasks
that have changed that resources are assigend to them. we are
currently not using resource notifications.

i hope my questionmakes sense and i appreciate any responses.

pat c.
 
D

Dale Howard [MVP]

pat c --

There is no default method to accomplish this. Your option would be to
create a custom programmatic method for doing so. Hope this helps.
 
P

patcav33

Dale,
thank you for your response. i have another qestion on another topic
that i hope you could help me with. you seem to provide the best,
clear cut answers to questions posted on this site. the questions
deals with saving and publishing a project 2 different ways - save
as-collaborate-publish or by using the import wizard and saving the
project locally to my machine and then importing. here are my
questions:
i apologize if this has been asked and answered many times already,
but i have searched this group and not gotten a clear answer on my
question which is:
what is the difference and importance when saving a project using the
Import funtction through Tools-Enterprise Options-Import project to
Enterprise vs. using the Save As-Collaborate-Publish?

other questions i have:
1. if you go the route of using the import wizard, is it correct that
you first have to save the project on your machine locally so that
when you are in the import wizard, you can select it as the project to
import? my thinking on this is that the reason one goes to project
server is so that they dont have to save all projects locally.

2. once you save it locally and import it through the import wizard,
do you then need to go to Collaborate-Publish or does it get published
automatically?

3. you only need to import a project once and then you can use the
'Save' funciton any time you make updates to the project - you would
not use 'Save As' if you are just updating a project because that
would cause you to rename the project?

4. is the only time you would use the 'Save As' function is when you
first create a project and have to save it to your local machine or
when you are not connected to the server?

thanks for any response

Pat Cavanaugh
Click to expand...
 
D

Dale Howard [MVP]

patcav33 --

Before I would even attempt to answer your many questions, I am trying to
understand why you are saving and publishing the project in two different
ways. In the process, you are probably creating double assignments for all
of the resources in both projects. Can you give me more information about
what you are attempting to do? If you need two versions of a project, you
should be using the Versions feature of Project Server instead. Please
explain more about your situation.
 
P

patcav33

Dale,
Thank you for replying and I will try to clear up what I mean here.
Somebody told me that I should always use the Import Wizard when i
want to save a project to the server and have it visible on PWA (after
publishing it of course). I was told that if I use the 'Save'
directly to the server method (as opposed to 'Save As File' to local
directory and using the import wizard), then Collaborate/Publish that
there is a chance for potential loss of data or some kind of mess up
down the road as the number of projects in the database gets larger.
is there truth to this?

Example using a new project of what we do :
Proj Mgrs open MSFT Project and hit the connect button to connect to
project server. when they are ready to save, they choose File/Save
and type in the project name. then they hit save. then they choose
collaborate/publish to make the project viewable in PWA.

is this process any different or any more/less secure than using the
import wizard? if yes, what is the difference and should i now save
all the project we currently have on a directory and import them
through the import wizard?

sorry for the confusion and i hope i have cleared up my situation and
process for you.

pat c.
 
D

Dale Howard [MVP]

Pat C --

Someone has misled you. When the PM opens Microsoft Project Professional
and connects to Project Server, and then creates a project, they need only
to click the Save button to save the project in the Project Server database.
At no point should the PM click File - Save As and then save the project as
an .mpp file.

The Import Wizard is used to import previously-existing projects that were
saved as .mpp files prior to your Project Server implementation. So, if you
have any projects saved as .mpp files before you started using Project
Server, and those projects need to be in the Project Server database, then
you should import them individually using the Import Wizard. Using the
wizard will allow you to "synch up" all of the information in the .mpp
project with your Project Server standards, such as mapping resources in the
project with enterprise resources in the Enterprise Resource Pool.

Hope this explanation helps.
 
Top