Project

General

Profile

Actions

Bug #1243

closed

Issue in Publishing the document from MSA: By changing the Parent Level frequently

Added by Anonymous almost 8 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Start date:
05/19/2017
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1. Create a Level
2. Enable "In Use" for two sites
3. Go to MSA pro module
4. Set Created Level in Business Rule (Doc pro Level Selector-->Parent Level)
5. Publish the document from MSA pro module
6. Go to Doc pro module
7. Select the created Level and search for the published document
8. Observe the Result

MODULES:
MSAPRO
Build Cycle:
Cycle 0
Customer:
Issue Dependency:
636
Dev Commitment to Resolve in::
NA

Description

When the Level is created and enabled(In Use) for more than one site, Published document from MSA module not listing under the selected Level

Note:
Published document not displayed under the selected level. So user not able to view the document.
This issue occurs when changing the Parent Level frequently.

Actions #1

Updated by Anonymous almost 8 years ago

  • Subject changed from Issue in Publishing the document from MSA:By changing the Level continously to Issue in Publishing the document from MSA: By changing the Parent Level frequently
  • Description updated (diff)
Actions #2

Updated by Smitha V almost 8 years ago

  • Status changed from New to Open
Actions #3

Updated by Anonymous almost 8 years ago

  • Project changed from EwQIMS SP636 to EwQIMS SP700
  • Build Cycle changed from Cycle 4 to Cycle 0
  • Issue Dependency set to 636
  • Dev Commitment to Resolve in: set to NA
Actions #4

Updated by User Admin almost 8 years ago

  • Status changed from Open to Known Issue
Actions #5

Updated by Anonymous almost 8 years ago

This is seams to be sporadic.

Actions #6

Updated by Anonymous about 7 years ago

Issue closed in SP730 cycle 2

Actions #7

Updated by Anonymous about 7 years ago

  • Project changed from EwQIMS SP700 to EwQIMS SP730
Actions #8

Updated by Anonymous about 7 years ago

  • Status changed from Known Issue to Resolved
Actions #9

Updated by Anonymous about 7 years ago

  • Status changed from Resolved to Closed

Closed in CYcle 5 of SP730

Actions

Also available in: Atom PDF