Bug #30554
openDocPro-Published Document Not Showing in the Default(AQuAPro) Folder because of Some TPM Images are published in (AQuAPro) Folder
0%
1.Login as a AQuaPro Module User
2.Navigate to Main2
3.Expand Global PI
4.Select any PI with Data
5.Open Design/Process Document/Segment
6.Publish the selected PI
7.Select the Default(AQuaPro) Folder
8.Click OK to Publish the document
9.Navigate to Documents Menu
10.Open the AQuaPro Folder
11.Observe the Result
Description
I have Published the AQuaPro Documents (Design/Process Documents/Segments) in Default(AQuAPro) Folder and Published documents is not showing in the Default folder,
TC ID: https://testlink.ewqims.net/ltx.php?item=exec&feature_id=67169&build_id=67
Files
Updated by Kirubakaran chandran about 2 months ago
- Project changed from SP 11.2.0.18 Patches to SP 11.3.2.2 Patches
- Issue Dependency changed from Docpro - TOC to Docpro - TOC Bug #27066
Updated by User Admin 7 days ago
- Status changed from Open to Resolved
- ISSUE TYPE set to NEW Due to Impact
Updated by Kiruthika G 7 days ago
- Status changed from Resolved to Not Resolved
We have Doc pro publish issue already there in the TPM pro module. That is not properly handled by the Team, so if we are fixing this issue in this version it may cause impact. So planning to move this issue to Known issue list.
Note: This is not blocking the 11.3.2.2 Release
Updated by Hakeem Abdul 4 days ago
- Project changed from SP 11.3.2.2 Patches to Known Issue
- Subject changed from DocPro-Published Document Not Showing in the Default(AQuAPro) Folder to DocPro-Published Document Not Showing in the Default(AQuAPro) Folder because of Some TPM Images are published in (AQuAPro) Folder
- Status changed from Resolved to Not Resolved
- ISSUE TYPE deleted (
NEW Due to Impact) - MODULES TPM added
- MODULES deleted (
AQUAPRO)
As per Sugesh advise, We have Doc pro publish issue already there in the TPM pro module. That is not properly handled by the Team, so if we are fixing this issue in this version it may cause impact. So planning to move this issue to Known issue list.
Note: This is not blocking the 11.3.2.2 Release