Actions
Bug #9847
closedD VDA: In Design FMEA Click on the Component Element (Item/ Interface) column getting an JS Error. Please see the Description
Start date:
11/22/2018
Due date:
% Done:
0%
Estimated time:
Steps To Reproduce:
1.Login as AQuA Pro Module Administrator
2.Click on AQuA Pro Tab and click on Main Menu
3.Expand the Global PI and select the PI
4.Click on Design Documents Menu and click on AIAG VDA DFMEA, new tab will open
5.Click on AIAG VDA Design tab and click on Design FMEA Menu
6.Click on the Below mentioned Following Column
2.Click on AQuA Pro Tab and click on Main Menu
3.Expand the Global PI and select the PI
4.Click on Design Documents Menu and click on AIAG VDA DFMEA, new tab will open
5.Click on AIAG VDA Design tab and click on Design FMEA Menu
6.Click on the Below mentioned Following Column
- Click on the Component Element (Item/ Interface) column
- Click on 3. Function of Component Element or Intended Output column
- Click on 3. Requirement of Component Element or Characteristic Column
- Click on 3. Failure Cause (FC) Column
- Click on Filter Code (Opt.) Column
- Click on Revision Date Column
- Click on AP Column
MODULES:
VDA
Build Cycle:
Cycle 1
Customer:
Issue Dependency:
IMPCAT Area If any ::
Impcat Verifed:
Description
The Above issue occurs in the below mentioned following columns.
1. Click on 3. Function of Component Element or Intended Output column
2. Click on 3. Requirement of Component Element or Characteristic Column
3. Click on 3. Failure Cause (FC) Column
4. Click on Filter Code (Opt.) Column
5. Click on Revision Date Column
6. Click on AP Column
Files
Updated by Reng Raj over 6 years ago
- Assignee changed from Anonymous to Iyappan hariharan
Updated by Iyappan hariharan over 6 years ago
- Status changed from Open to Resolved
this issues is already fixed on 8.1.0.1 patch but I am not able see the changes so I have moved those changes into the $\EwIMS\BuildFiles\Build_8.5.0\Sprint2\27th Nov. Kindly verify after this sprint2 build installation
Updated by Shankar Narayanan over 6 years ago
- Status changed from Resolved to Fixed with Hotfix
Updated by Shankar Narayanan over 6 years ago
- Status changed from Fixed with Hotfix to Resolved
Updated by Shankar Narayanan over 6 years ago
- Status changed from Resolved to Closed
Closed in SP820 on 17-12-2018
Actions