Planning State in Portfolio Planning Workspace - interaction with Demand records

[taileigh]

In the Portfolio Planning Workspace there is a 'Planning State' field. One of the drop down options within the planning state field is 'cancelled'.

Does anyone have an understanding of any possible interaction between this planning state and a demand record itself? For example, if a planning state of cancelled is selected for a demand within the portfolio planning workspace, will this/can this reflect somewhere on the demand record and indeed the demand workbench? 

We are trying to ascertain the best way of working between the portfolio planning workspace, demand records and demand workbench.

Thank you!

[shiwan_agrawal]

@taileigh Any changes in the "Planning State" will not update anything on the respective execution table like dmn_demand and pm_project.

However, any change on the field "State", by default have an integration between the alignment and execution tables and when state gets updated in alignment table, a Business Rule "Set Planning state on state change" automatically updates the value of "Planning State".

If this helps answering your question, please mark this as "Accepted Solution".

-Shiwan Agrawal

[Jennifer Yiu]

@taileigh Great question!  We did find that when the "Planning State" is updated in one portfolio plan, that same planning item on a different plan also reflects that change.  Not sure that I saw this detail in the planning item form documentation, but I did note the mention that planning state needed to be set to 'prioritized' for items to display on the roadmap.

@shiwan_agrawal May you please provide a little more detail on the business rule you mentioned, particularly the intended use case?  Meaning is it out of the box where the "State" field is editable on the SPW/alignment side such that it automatically updates the value of "Planning State"?  Thanks ahead!

Here is what I see in our instance:

[shiwan_agrawal]

@Jennifer Yiu  For "State" field, there is an OOTB integration which allows to sync up the values from execution table (dmn_demand) to alignment table (sn_align_core_demand).

When a persona like Demand Manager, progresses the demand (Not in SPW/PPW) through legacy demand form (Example: Moving demand from screening to qualified), "State" field also gets updated in SPW/PPW due to the existing integration.

Due to the state change in SPW/PPW demand, business rule "Set Planning state on state change" gets triggered and updates the "Planning State". To understand the logic of how Planning State vs State values are mapped, you can review the BR's script. Example: When demand's State is "Completed", "Planning State" should automatically get updated to "Done"

If you find this answer helpful, request you to mark this as correct answer.

-Shiwan Agrawal