Bug #12145
closedIE & Chrome: Main Asynchronous Publish Message is not same like the Main2 Asynchronous Publish Message
0%
1.Login as AQuAPro Module User
2.Click on AQuAPro Tab -> Main2
3.Select PI -> Open PFMEA Document
4.Do the Asynchronous Bulk Publish or Single Publish -> View the Message
5.Open Main Menu -> Repeat the Step 3 & 4
6.Observe the Result
Description
Main2 Asynchronous Publish Message is displaying as Paragraph but for Main Asynchronous Publish Message is displaying with huge space and comparing to the Main2 its not looking same.
NOTE: Message/Content is same but the look and feel is not same
Files
Updated by Iyappan hariharan almost 6 years ago
- Status changed from Open to In Progress
Updated by Iyappan hariharan almost 6 years ago
- Status changed from In Progress to Resolved
fixed and patches provided for testing
Updated by Anonymous almost 6 years ago
- File Replicated Issue No 12145 for Main2 on 14.05.2019.jpg Replicated Issue No 12145 for Main2 on 14.05.2019.jpg added
- Status changed from Resolved to Not Resolved
This issue is not fixed so changing the status as Not Resolved on 14.05.2019 in Cycle-9
NOTE: The Issue is for Main its displaying only the Document is queued for publishing but its not displaying remaining Paragraph of "NOTE".
Updated by Iyappan hariharan almost 6 years ago
- Status changed from Not Resolved to Resolved
Fixed and patches ready for testing
Updated by Anonymous almost 6 years ago
- File Document Asynchronous Publish Issue on 21.05.2019.jpg Document Asynchronous Publish Issue on 21.05.2019.jpg added
- Status changed from Resolved to Not Fixed with Hotfix
The reported issue is not fixed and for Main2 by doing the Asynchronous Publish its displaying the Alert Message like this "No documents published<publish oc="obc2" oi="obi01220535" reason="Test123" chgs_reqd="Test123" keywords="Test123" changes="2" paginate="1" pubfrom="mvc"><di id="dci219" /></publish>--Object reference not set to an instance of an object."
Updated by User Admin almost 6 years ago
- Status changed from Not Fixed with Hotfix to Closed
Updated by User Admin almost 6 years ago
- Status changed from Open to Fixed with Hotfix
Updated by User Admin almost 6 years ago
- Status changed from Fixed with Hotfix to Not Fixed with Hotfix
Updated by User Admin almost 6 years ago
- Status changed from Not Fixed with Hotfix to Closed