S
Stephan Steiner
Hi
We're currently still using Project Server 2003 but are considering an
upgrade to 2007.
We automate a lot of project tasks, including the creation of new projects,
creation of tasks, and assignments. We have a bunch of "unmanaged" projects
where we just dump assignents for smaller tasks that don't need PJM
supervision and where we have no task dependencies - just a finish date that
is being tracked.
In Project 2003, we always have to launch the Project Client to publish
these autogenerated tasks and assignments - which is rather cumbersome since
those plans tend to become large rather quickly (in a bad day, we might get
100 new lines in the project, and two days after, all those tasks have been
closed again).
I've been browsing the Project 2007 SDK documentation and found the
Project.QueuePublish method and I'm wondering what it does - the
documentation says
Moves the project from the Drafts database and saves it to the Published
database.
And there's a parameter fullPublish
If true, removes any previous data saved for this project in the Published
database before saving..
leading me to believe that if QueuePublish is called for a pre-existing and
already published project, calling QueuePublish would just publish whatever
changes have been made since the last time the project was published. And in
case of a newly created project, QueuePublish would just publish the project
for the first time (rather than having the PJM open the project and do the
first publication after creating it via PDS as we do nowadays).
Is that assumption correct? And does the publishing involve publishing of
tasks and assignments to PWA as well? I recall a discussion about the
AutoPublish feature in PDS in Project Server 2003 where one of the MVPs
indicated that the lack of a scheduling engine on the server was the reason
why AutoPublish never worked and hinted that this may be different in 2007 -
so I'm wondering if this is the wonderful method that would allow us to
publish tasks and assignments from a system without the Project client
installed.
Regards
Stephan
We're currently still using Project Server 2003 but are considering an
upgrade to 2007.
We automate a lot of project tasks, including the creation of new projects,
creation of tasks, and assignments. We have a bunch of "unmanaged" projects
where we just dump assignents for smaller tasks that don't need PJM
supervision and where we have no task dependencies - just a finish date that
is being tracked.
In Project 2003, we always have to launch the Project Client to publish
these autogenerated tasks and assignments - which is rather cumbersome since
those plans tend to become large rather quickly (in a bad day, we might get
100 new lines in the project, and two days after, all those tasks have been
closed again).
I've been browsing the Project 2007 SDK documentation and found the
Project.QueuePublish method and I'm wondering what it does - the
documentation says
Moves the project from the Drafts database and saves it to the Published
database.
And there's a parameter fullPublish
If true, removes any previous data saved for this project in the Published
database before saving..
leading me to believe that if QueuePublish is called for a pre-existing and
already published project, calling QueuePublish would just publish whatever
changes have been made since the last time the project was published. And in
case of a newly created project, QueuePublish would just publish the project
for the first time (rather than having the PJM open the project and do the
first publication after creating it via PDS as we do nowadays).
Is that assumption correct? And does the publishing involve publishing of
tasks and assignments to PWA as well? I recall a discussion about the
AutoPublish feature in PDS in Project Server 2003 where one of the MVPs
indicated that the lack of a scheduling engine on the server was the reason
why AutoPublish never worked and hinted that this may be different in 2007 -
so I'm wondering if this is the wonderful method that would allow us to
publish tasks and assignments from a system without the Project client
installed.
Regards
Stephan