on - edited by
Luis Ataide
SAFE HARBOR / DISCLAIMER: This article describes a proposed solution to support this use case. Please note that ServiceNow may offer an out-of-the-box solution for the issue described below in the future.
The proposed solution requires configuration, as such, there is no liability for ServiceNow to provide support, apply changes, fix defects and review impact during future upgrades.
Customers are responsible for evaluating and deciding whether to implement this solution.
What problem does this solve?
A current product gap does not provide the conversion of Demands to EAP Items. This is a hinderance for processes of demand conversion already established for SAFe and/or Agile 2.0 items.
This guide will walk you through configuring the platform to enable a workaround for converting Demands to EAP Items (Epic & Feature) until this capability has been developed natively in Product.
To streamline the efforts for this, we have created and supplied XML records to be imported, while also detailing those configuration records in this document.
Prerequisites
- Demand Managers (it_demand_manager) require the role 'sn_apw_advanced.eap_user' for selecting the EAP Team and then creating it when the Demand is ready.
- SAFe and/or Agile 2.0 plugin must be installed
- Due to a current dependency for financials and resource records on ‘task’ (rm_epic or sn_safe_epic), these must be present for those records to move from the Demand.
- Planned by EOY ‘25 is the removal of that dependency
- Strategic Planning Integration(s) must be configured for rm_epic and/or sn_safe_epic
- Scope: Portfolio Planning with PPM, Agile 2.0, and SAFe
- Navigate to Strategic Planning > Integrations
- If SAFe and/or Agile 2.0 plugins installed, you should simply need to click ‘Generate Default Mapping Configurations’.
Manual Steps
- See Highlighted sections/steps if wanting to include EAP Team for Story (OOB story is available, but no EAP Team)
- Add a new Type of Demand 'Choice' for EAP Feature. Important to define the value as ‘core_feature’, it will be used to filter the available teams in next step.
- Scope: Global
- Demand field: Type[type]
- Choice: Add 'new'
- Dependent value: Strategic
- Add a new Type of Demand 'Choice' for EAP Epic. Important to define the value as ‘core_scrum_epic’, it will be used to filter the available teams in next step.
- Scope: Global
- Demand field: Type[type]
- Choice: Add 'new'
- Dependent value: Strategic
- Create a new field called EAP Team in Demand[dmn_demand]
- Create a new reference field in dmn_demand
- Scope: Global
- Label: Team
- Name: u_eap_team
- Type: Reference
- Table: Enterprise agile team [sn_apw_advanced_eap_team]
Advanced View- Reference qual: javascript:'eap_configuration.work_types_allowedCONTAINS'+current.type;
- OMIT Reference qual if Story is needed
- Create a new reference field in dmn_demand
-
- Add new Team field to Demand form
- Add the column of ‘Enterprise agile team type’ to Enterprise agile teams List (Scope: Strategic Planning)
- Add new Team field to Demand form
- Create a new field at Demand to refer to the converted EAP record
*Move the new field to under Story in the Default view- Scope: Global
- Label: EAP Record
- Name: u_eap_record
- Read-only: True
- Type: Reference
- Table: Planning Item (sn_align_core_planning_item)
Advanced View- Reference qual: javascript:'eap_configuration.work_types_allowedCONTAINS'+current.type;
- Reference qual: javascript:'eap_configuration.work_types_allowedCONTAINS'+current.type;
- Create a new field at EAP planning item (sn_align_core_eap_planning_item) to refer to the converted Demand
- Scope: Portfolio Planning Core
- Label: Demand
- Name: u_demand
- Type: Reference
- Table: Demand (dmn_demand)
- Add new field to the following views on Epic (sn_align_core_scrum_epic) & Feature (sn_align_core_feature):
- APW Default (Details section)
- Scope: Portfolio Planning (Epic)
- Scope: Strategic Planning (Feature)
- EAP Default (Details section)
- Scope: Strategic Planning (both)
- <Any other Applicable EAP Configuration View(s)>
(e.g. EAP Essential Configuration, EAP Portfolio Configuration, etc.)
- APW Default (Details section)
- Set Active Epic (sn_align_core_scrum_epic) Investment Entity, deactivate all other Epics. (This allows for the Financials to be transferred to the new EAP Epic when converted.)
**Deactivate others FIRST, then Activate EAP Epic or error will prevent the switch. - If Story is needed, an update to the CSM Table Map ‘Demand to Story’ will need to include the following:
- target.eap_team = source.u_eap_team;
- target.eap_team = source.u_eap_team;
- If Benefit Plans are needed, the two Client Scripts on the Demand (dmn_demand) table need to be modified for the Related Lists to display when Type = EAP Epic ('core_scrum_epic').
- Hide related list on demand
- ShowOrHideBPlanRelatedListOnTypeChange
- Hide related list on demand
XML Provided configuration
- Create UI Policy & UI Policy Action to make field Team [u_eap_team] visible and mandatory when Type is for Epic, Feature or Story
This will also clear field when EAP Epic or EAP Feature is not selected- For story, this would need to be manually added to the UI policy provided
- Example XMLs provided
- 1_sys_ui_policy_SN_Make_Team_field_visible_hidden
- 2_sys_ui_policy_action_SN_Make_Team_field_visible_hidden.xm
- Create UI Policy & UI Policy Action to make field EAP record [u_eap_record] visible when not null to be consistent with other types.
- Example XMLs provided
- 3_sys_ui_policy_SN_Make_EAP_record_field_visible_hidden
- 4_sys_ui_policy_action_SN_Make_EAP_record_field_visible_hidden
- Example XMLs provided
- Create mapping at CSM Table Map[csm_table_map] to define the fields mapping between Demand and Feature
- Example XML provided
- 5_csm_table_map_Demand_to_EAP_Feature.xml
- If additional field mappings are required, the code should be updated in the highlighted area
- Example XML provided
- Create mapping at CSM Table Map[csm_table_map] to define the fields mapping between Demand and Epic
- Example XML provided
- 6_csm_table_map_Demand_to_EAP_Epic.xml
- If additional field mappings are required, the code should be updated in the highlighted area
- Example XML provided
- Create a new system property to record the CSM Table Map sys_id
- Example XML provided
- 7_sys_properties_spm_custom_eap_csmtablemap.xml
- Example XML provided
- Create a new 'SNEAPUtil' Script Include to manage the conversion to EAP record
- Example XML provided
- 8_sys_script_include_SNEAPUtil.xml
- Script will create a new EAP Feature OR EAP Epic
- Copy field values based on CSMTableMap
- Copy attachments
- Copy demand score (Scoring Framework in SPW)
- Copy Goals
- Update demand investment record
- Set demand as converted
- Example XML provided
- Create ACL for locking down Category, Type, and EAP Team fields ONLY after EAP Record field is populated (aligns to other Types).
- User MUST have elevated role (security_admin) to apply ACLs
- Example XML provided
- 9_sys_security_acl_demand_u_eap_team.xml
- 10_sys_security_acl_demand_type.xml
- 11_sys_security_acl_demand_category.xml
- For story, this would need to be manually added to the EAP Team ACL (9_sys_security_acl_demand_u_eap_team.xml) provided
- || (current.getValue('type') == 'scrum_story' && current.scrum_story_record.nil())
- Create UI action to convert demand to EAP Feature
- Example XML provided
- 12_sys_ui_action_Create_EAP_Feature.xml
- Example XML provided
- Create UI action to convert demand to EAP Epic
- Example XML provided
- 13_sys_ui_action_Create_EAP_Epic.xml
- Example XML provided
- Create a Business Rule to trigger the copy/transfer of demand data to Epic planning item
- Example XML provided
- 14_sys_script_SN _Copy_info_to_Epic.xml
- Transfer records from “execution entity” (SAFe Epic or Scrum Epic) to “planning item” (EAP Epic) by calling the SNEAPUtil
- Cost Plans / Breakdowns
- Resource Assignments
- Resource Plans
- Investment Budget
- Benefit Plans / Breakdowns
- Example XML provided
