Project

General

Profile

Actions
Copy link

Bug #11297

closed

Website & Existing DB: Operation Flow Chart, By Clicking on Print Diagram option its displaying JS Error

Added by Anonymous about 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Medium
Assignee:
Iyappan hariharan
Start date:
03/07/2019
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1.Open the Browser
2.Enter the URL
3.Enter the Username and Password
4.Click on Login Button
5.Click on Module icon
6.Click on AQuAPro
7.Click on Main Menu
8.Select the PI -> Click Diagrams
9.Open Operation Flow Chart Diagram
10.Right-Click to Select Print Diagram option
11.Observe the Result

MODULES:
AQUAPRO
Build Cycle:
Cycle 4
Customer:
Issue Dependency:
Website Testing, Existing DB
Dev Commitment to Resolve in::

Description

Operation Flow Chart, By Clicking on Print Diagram option its displaying JS Error as

In Main1:

"Line: 18
Error: 'contextMenu' is undefined"

In Main2:

"Line: 759
Error: Unable to get property 'toSVG' of undefined or null reference"

Files

Download all files
Main 2 Print Diagram Issue in Operation Flow Diagram.jpg (233 KB) Main 2 Print Diagram Issue in Operation Flow Diagram.jpg Anonymous, 03/07/2019 06:38 PM
Main 1 Print Diagram Issue in Operation Flow Diagram.jpg (347 KB) Main 1 Print Diagram Issue in Operation Flow Diagram.jpg Anonymous, 03/07/2019 06:38 PM
Actions
Copy link
 #1

Updated by User Admin about 6 years ago

  • Status changed from New to Open
Actions
Copy link
 #2

Updated by Iyappan hariharan about 6 years ago

  • Status changed from Open to In Progress
Actions
Copy link
 #3

Updated by Anonymous about 6 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #4

Updated by Anonymous about 6 years ago

  • Status changed from Resolved to Not Fixed with Hotfix

This issue is fixed in Main 2 but it is replicating in Main.

Actions
Copy link
 #5

Updated by Iyappan hariharan about 6 years ago

  • Status changed from Not Fixed with Hotfix to Resolved

Main1 Issue is also resolved and it is working now

Actions
Copy link
 #6

Updated by Anonymous about 6 years ago

  • Status changed from Resolved to Fixed with Hotfix

This issue is fixed in Main and Main2 so changing the status into Fixed with Hotfix on 27.03.2019

Actions
Copy link
 #7

Updated by Anonymous about 6 years ago

  • Status changed from Fixed with Hotfix to Resolved
Actions
Copy link
 #8

Updated by Anonymous about 6 years ago

  • Status changed from Resolved to Closed

This issue is verified in BLANK DB and its working fine so closing this issue in Cycle-6 on 01.04.2019

Actions
Copy link

Also available in: Atom PDF