Project

General

Profile

Actions

Bug #13794

closed

Main2: Unexpected behaviour in the Effect Column when trying to delete the added Design Failure

Added by Anonymous over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Medium
Assignee:
-
Start date:
08/29/2019
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1.Login as AQuAPro Module User

2.Click on AQuAPro Tab -> Main2

3.Select PI -> Open PFMEA Document

4.Double-Click on a Cell in the Effects Column -> Click on Design Failure option

5.Click on any of the listed Design Failure option

6.Right-Click on the added Design Failure -> Select Copy Cell option

7.Again Right-Click on the same Cell -> Select Paste Cell option

8.An Error Message will display -> Click on OK Button

9.Now Right-Click on the added Design Failure -> Click on Delete Branch option

10.After the deletion it will create a duplicate process effect -> Try to Right-Click on the duplicated process effect

11.Observe the Result

MODULES:
AQUAPRO
Build Cycle:
Cycle 1
Customer:
Issue Dependency:
Dev Commitment to Resolve in::

Description

In Main2, In the Effect Column Cell the User adding an Design Failure then Copying the whole Cell and Pasting in the same Cell then it will display an Error Message so click on OK Button and Delete the added Design Failure. The added Design Failure was deleted but it will create a duplicate Process Effect and if the User try to Delete by Right-Click on it means it will display an JS Error as "Line: 370
Error: Unable to get property 'getAttribute' of undefined or null reference
DOMGetText
LineCellObjGetXMLInfo
ContObjSetCell
DocSelect
DocMouseDown"


Files

Actions #1

Updated by User Admin over 5 years ago

  • Status changed from New to Open
Actions #2

Updated by Iyappan hariharan over 5 years ago

  • Status changed from Open to Resolved

Fixed and patches provided for Testing

Actions #3

Updated by User Admin over 5 years ago

  • Assignee changed from Iyappan hariharan to Anonymous
Actions #4

Updated by Anonymous over 5 years ago

This issue is working as expected so closing this issue on 10.09.2019

Actions #5

Updated by Anonymous over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF