The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Attaching two Workplan to project based on the need.

Highlighted
Mahen M
Honored Contributor

Attaching two Workplan to project based on the need.

Hi,
We are having a requirement in which a project can be linked with any one of the two predefined Workplans Template.
The linking of the workplan should occur only after the second decision step exit and it should be automatic, I hope we can use 'ksc_create_workplan' Command in this.
The Workplan name should be got from the end user by a field parameter at the exit of first Decision step(After not submitted status). We should NOT see the Workplan template links for attaching the template to the project in the Project Summary Tab of the Project.
Please let me know how we can achieve this condition.

Regards,
Mahendran M

Regards,
Mahendran M
6 REPLIES
Erik Cole
Honored Contributor

Re: Attaching two Workplan to project based on the need.

Execution step using ksc_create_workplan should work. You can pass it a workplan template ID based on the request field.
Mahen M
Honored Contributor

Re: Attaching two Workplan to project based on the need.

Hi Erik,
This is OK, What about 'We should NOT see the Workplan template links for attaching the template to the project in the Project Summary Tab of the Project.'

Please advice

Regards,
Mahendran M

Regards,
Mahendran M
Erik Cole
Honored Contributor

Re: Attaching two Workplan to project based on the need.

That part I do not know how to accomplish, except if instead of creating a project directly you use a Proposal and create the project via execution step. That way you can have both executions occur one right after the other.
Mahen M
Honored Contributor

Re: Attaching two Workplan to project based on the need.

Hi,
We dont need a Proposal here. Is this is possible? Till Workplan creation it is Proposal and after workplan creation it is a Project. But the mandatory thing is that we should have only one ID.

WE Should not have 2 different ID's for Proposal and Project.

Regards,
Mahendran M
Łukasz Czech
Collector

Re: Attaching two Workplan to project based on the need.

Hi,

Erics solution seems to be the only one. I'm not sure why can't you use proposal - if you need one ID both for proposal and project you could create your own ID which will be copied from proposal to project. It will not be the main ID of the proposal/project but you could use it for identification purposes anyway.
The only other thing you can do is to erase workplan template in Project Type so the link to create Project from this template will not be displayed in Project summary page, but it will be possible to create blank workplan anyway.

Best regards
Lukasz Czech
Mahen M
Honored Contributor

Re: Attaching two Workplan to project based on the need.

Hi,
This is not our clients requirement. We are doing this because we are having problem with 'add tasks to Workplan' webservice.

If we introduce Proposal it will make things complex, The original requirement is to simplify the current existing Process.

Regards,
Mahendran M

Regards,
Mahendran M
//Add this to "OnDomLoad" event