I’ve a problem with doclink that changes to database link when i save a document.
A java agent creates a new response document to a main document. In the response doc, i’ve richtext field where is put a doclink to the main doc. It works till i edit manually the doc and save it again. It becomes a database link.
The richtext field is computed with a default value of “” in the form used to display the document. If i change to editable field, the problem doesn’t occur but user can modify that field and i don’t want that.
Using a controlled section isn’t a solution either in this case.
I’ve found some post talking about a bug in 6.5.4 but it happens in 8.5.1 & 8.5.2
I tried to create a second RT field computed to the initial RT field (which is left editable and hidden). No luck. The computed field messes up the links in the hidden field. The hidden field does remain intact so me thinks there is a bug in the compute logic behind that field component/object.
I’d do an SPR, but I am so far behind in my workload…
Subject: Corrupted Doclinks in computed RT fields and access-controlled sections
Hi,
I recently encountered this problem too.
My workaround is to replace the doclinks with action hotspots that use LS to get the document by key and then instantiate a uidoc.
One of the advantages of doclinks is that, if the user already has the document open somewhere, they just switch the user to that instance instead of opening a new instance. Setting the last parameter of ws.EditDocument to FALSE seems to work OK too, though.
However, when the doclinks were in access-controlled sections, I’ve had to move them, as the hotspot action won’t work in such a section if the user doesn’t have sufficient rights to modify the section.
