This content has been marked as final. Show 6 replies
The first item is expected behavior and not a bug. This is the normal behavior for field propagation. The first occurrence of the field is editable, but all the subsequent locations simply receive a "copy" of the content and are not editable.
The second one does sound like a bug, if I understood your situation correctly. If the MLT is set for paragraph selection only and No Ediing, then all the pages should be protected.
As a side note, the MLT with paragraph selection will only activate from the first page and not when you click on that field on subsequent pages. I'm just drawing the connection to your first situation where only the first occurrence is where the editing must begin.
Thanks for your response. For the first item, this is a unique field that just happens to end up on the second page. It's not a field propagation situation. I've opened up a support ticket for both issues as they both appear to be bugs.
Please provide the service request ticket number(s).
The service request ticket number is 3-6952044051
Since the previous reply, it has been proven that the subsequent pages could become editable even though the Paragraph selection definition was set to allow no such editing. I suspect the correction will appear in a future patch.
This turned out to be BugDB item 16312899. https://bug.oraclecorp.com/pls/bug/webbug_print.customer_preview?c_rptno=16312899 and it looks like it has been patched in up coming releases.