Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies replies
    2
  • Answers answer
    1
  • Subscribers subscribers
    12
  • Views views
    130
  • Users 0 members are here
Related
Options

ksc_create_project is copying staffing profile of parent project

Harvin Dy

We have a requirement for a Project to be able to spawn "child projects" via the workflow.

These "parent" projects can have staffing profiles created already before a child project is spawned.

We use the OOTB ksc_create_project command for the child project creation, however we noticed that upon creation, the child project copies the staffing profile from the parent including the fulfilled lines. Is there a way to spawn child projects without copying the parent staffing profile (or leave the positions blank at least)?

  • 0

    Just to add - looking at the resource pool, only the highlighted parent project should have a committed resource. However when a child project is spawned it also commits the resource for that project. Even the totals on the right don't seem to align.

  • Suggested Answer

    0  

    Hi Harvin,

    ksc_create_project is used to create a project from a request or proposal, and some fields will be taken from the request or proposal to project. 

    So far, there is no way to spawn a child project without copying the parent staffing profile nor leave the positions blank.

    Please submit an Idea Exchange, then we will look into it to see when we can implement it.

    Thanks,

    Sharon

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.