Bug #28241: Interface Function Matrix - Deallocating an allocated Risk value from IFM doesn't delete the created flow-down from the VOC page(please Refer the description) - SP 11.2.0.15 Patches - OMNEX ISSUE TRACKER

Actions

Copy link

Bug #28241

closed

Interface Function Matrix - Deallocating an allocated Risk value from IFM doesn't delete the created flow-down from the VOC page(please Refer the description)

Added by Vani Kunnatheri 11 months ago. Updated 10 months ago.

Status:

Closed

Priority:

Medium

Assignee:

Radhi Madhavan

Start date:

05/31/2024

Due date:

% Done:

Estimated time:

Steps To Reproduce:

1.Log into FST
2.Select Requirement Document
3.Select the Focus Element.
4.Add a function and Requirement.
5.Select IFM form the item definition.
6.Assign a Risk value against any of the child of the function and Requirement we created.
7.Go to Requirement document and observe the flow down created.
8.Goto IFM and deallocate the Risk value.
9.Go to Requirement document and observe.
10.Similarly assign a risk value again and update it with another value.
11.Go to the VOC page of the allocated element.
12.Please observe the multiple functions and requirements created

MODULES:

FST

Build Cycle:

Cycle 1

Customer:

Issue Dependency:

Dev Commitment to Resolve in::

Description

1. Deallocating an allocated Risk value from IFM doesn't delete the created flow-down from the VOC page.
2. After assigning a risk value in IFM, system creates a corresponding function and requirement in the VOC page of the child, when we update the risk value,
it again creates a new function and requirement instead of updating the existing one.

Files

Download all files

Deallocated Risk value.png (26.1 KB) Deallocated Risk value.png		Vani Kunnatheri, 05/31/2024 08:32 PM
VOC page after deallocate .png (50.5 KB) VOC page after deallocate .png		Vani Kunnatheri, 05/31/2024 08:32 PM
updated Risk values and VOC.png (137 KB) updated Risk values and VOC.png		Vani Kunnatheri, 05/31/2024 08:38 PM