When we are tying to move an epic from Safe epic to rm Epic, Then the epic is not getting created at the alignment side. - Known Error

When we are tying to move an epic from Safe epic to rm Epic, Then the epic is not getting created at the alignment side. Description When we are tying to move an epic from Safe epic to rm Epic, Then the epic is not getting created at the alignment side.

Steps to Reproduce

Setup assumptions:

1. We assume that customer has installed all the below apps:

Agile - Scaled Agile Framework - Essential SAFe Alignment Planner Workspace (v4.0.0) Alignment Planner Workspace integrations for PPM and Agile 2.0 (v3.0.1) PPM Standard. Agile Development 2.0 2. We assume customer has an integration between alignment planner workspace and PPM, SAFe. Customer has table maps for sn_safe_epic.

Steps to reproduce:

1. Create 2 Planning Hierarchies with one having safe epic and the other having epic table maps. Have a PO each for the PH. 2. Create Safe Epic in alignment and assign the PO associated to Safe Epic PH. Verify that the Safe Epic is created in Execution. 3. In Alignment change the PO of the above epic to the PO which is mapped to rm_epic table map PH.

Expected : A new record should be created in rm_epic in execution. Actual : No record is created in the rm_epic in execution

Workaround New Business Rule named " Clear execution fields on changing PO " is introduced to handle the mentioned defect. BR will only execute when methodology of PO is got changed from previous one. In the mentioned BR execution_entity_table value and execution_entity_item value is set as empty string.3. Please find the attachment in the problem attachment link. 4. Import the attachment from by clicking the ' Import the update set from XML ' related links which is available in Retrieved Update Sets (All -> System Update Sets -> Retrieved Update Set). Test Cases:

Cases ::

1. Methodology of PO is got changed from one to other while updating the planning items.

(SAFe -> Scrum)

Observation: BR will execute. New entry should be created only in rm_epic table with new updates.

(Scrum -> SAFe)

Observation: BR will execute. New entry should be created in sn_safe_epic and rm_epic table with new updates.

(Scrum/Hybird -> empty)

Observation: Error message will be popped up saying Current planning item is not mapped to the selected Planning organization.

2. If PO is getting changed in planning items but current PO and previous PO belong to the same Planning hierarchy.

Observation: BR won’t execute. Existing entry will be updated with new changes.