Generated Text not displaying

[ptc-5157108]

We are facing an unusual issue, we have FOSI for showing generated text. It is working fine when we are updating existing tags, however, when we insert new tags then we are not able to see the generated text corresponding to those new tags. Also, we have observed that after inserting new tags, if we delete some text in some other tag and then undo (Ctrl+Z), we are able to see the generated text for the newly inserted tags.

We have gentextautoupdate as "full" and gentextautoupdate as "on". Please advise.

[JerryA.Tippie]

Hi Pawan,

This sometimes happens when the document is quite big and RAM resources are being stretched to the limit. When Editor notices RAM is running low, it switches mode and doesn't always display gentext automatically. Various actions force it to update generated text anyway. With large documents, it is often good to take extra measure to preserve memory. Turning off graphic display and generated text are two popular techniques to conserve memory.

If you regularly work with large documents, it would be good to increase RAM for the computer.

Try setting gentext=on. Here is a link to an article that discusses this very thing:

https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS113952

Regards,

Jerry Tippie

[ptc-5157108]

Thanks Jerry for replying, but that doesn't answer why it works when we edit something else and do Ctrl-Z. Also, if the tag is already existing (in our case, generated text is tied to the presence of tag so generated text is also existing) and we just update the tag info the generated text also gets updated.

Also, btw, gentext is "on", did not mention it previously.

Regards,

Pawan

[ptc-5157108 · Accepted solution]

Here is what got it working, we ran the following two commands

set gentext=on

set gentextautoupdate=on

Before running these commands the values of gentext as well as gentextautoupdate were "on" anyways, yet we were not able to see the FOSI text. However, setting them again as "on" got them working. Weird behavior by Arbortext, but we are fine on this one for now.