Scoring Framework in SPW from demand to project

[Nathan Arp]

Hi - 

When we use the Scoring Framework on a Portfolio Plan Demand, and then convert the execution item to a Project, the SPW Demand is closed and is no longer visible in the Portfolio Plan, but we can now see the project.  However, the scoring doesn't migrate to the new SPW Project.

Is there a way to migrate this OOTB?

Thanks!

[Ramandeep Kaur]

Hi @Nathan Arp , 

Not sure if you have been able to get the expected result.

I came across another community post while I was looking for a solution to similar requirement.

Synch Scoring in Strategic Planning Workspace with... - ServiceNow Community

Thanks to @TroySasso for the explanation.

Hope it would be helpful for future visitors.

Kind Regards,

Raman

[TroySasso]

Before proceeding to sync scoring data make sure your customer fully understands the difference between scoring Demands and Scoring planning items >> A demand score assesses the feasibility and value of a new proposal (e.g., risk, cost, strategic value) to determine if it should be approved. A planning item score (or portfolio item score) prioritizes approved initiatives (projects, epics, demands) using standardized frameworks to optimize resource allocation.  

Assuming your execution items are the aligned planning item to core forms such as Demand and Project;

dmn_demand = sn_align_core_demand

pm_project = sn_align_core_project

Basic info:

1. When a planning item (Demand, Project, Epic) is scored in Strategic Planning Workspace the scores are stored in variables.  The variable table is called; sys_variable_value.  Regular Demand scores are not.

2. When you perform a .list command on the sys_variable_value table (sys_variable_value.list) the 'ID' column in the list matches the sys_id of the planning item (Demand/Project/Epic) from the Planning item scoring framework. 

3. There is a field on the sys_variable_value table called 'execution URL it has the core Demand/Project sys_id built onto the end of the URL

4. ***A planning item sys_id DOES NOT match the sys_id of a Demand/Project from the core side so use caution if you want to write workflow to sync answers you'd have to possible match the project/demand friendly name from the ID column or extract the core sys_id from the execution url

Hope this is helpful to some of you.