We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

ServiceNow SPM can clone an existing Demand in a manner similar to Jira’s clone functionality?

Triveni Alasyam
Tera Contributor

if Demand is cloned with UI action button, what data elements can be:

  • Safely cloned
  • Excluded by design (e.g., system IDs, workflow state, audit fields)

can we identify implications for:

  • Subprojects
  • Subtasks
  • Related records (high‑level only)
  • Production processing speed and stability
1 REPLY 1

Tanushree Maiti
Tera Patron

Hi @Triveni Alasyam 

 

These fields are generally copied to ensure the demand retains the context of the original
  • Description & Scope: Short Description, Description, Business Case, Portfolio, Program.
  • Categorization: Demand Type, Category, Subcategory.
  • Financials/ROI: Business Value, Risk, Size, ROI, Capex, Opex (if applicable).
  • Assignment/Stakeholders: Requestor, Assigned to, Assignment Group, Steering Committee.
  • Dates: Due Date, Start Date.

When we clone demand in sub-prod, we do not exclude anything  for demand in cloning profile.  ( it is as per our requirement)

 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti