Question
Belvnesheconombank
BY
Last activity: 22 May 2020 2:43 EDT
Word merge functionality not working (8.3)
Hi guys!
I have two different servers: first with 7.1.9 version and second with 8.3 version of Pega (Server with version 8.3 is upgraded server from 7.1.9 version so rulebase are the same). On the 1st server documents are generate good but on the 2nd server I see Word Template with blank fields and I can see field codes thru menu. In other words all of the tags {pega:reference} don't work as expected on 2nd server. I use "Pega-Sample CreateMergedWordDoc" approach.
I already tied to do following:
1. I'm sure that I read all of the posts here in collaboration center and all of help articles
2. I added server address to trusted sites in IE security settings
3. I reinstalled Silverlight and pre-requisites
4. I checked values in registry for silverlight
5. I granted full access to temp directories for my user (but I work as administrator on my PC)
Maybe you have any advice to resolve this issue?
Accepted Solution
Updated: 22 May 2020 2:43 EDT
Belvnesheconombank
BY
Hi guys! Here is the solution from MSP. And it works:
Perform the following local-change:
- Verify the Location Records > SysAdmin > Dynamic System Settings (DSS).
- Filter under Owning Ruleset Pega-Engine.
- Search for the prconfig/initialization/advancedSession/default Setting purpose.
- If the Setting purpose is unavailable, create it and set its value as False. If the Setting purpose is already available, then change its value to False.
- Save the settings.
- Log out and restart the Pega server.
- Clear the browser cache and Temp files from the user's system.
Search for the WordMacroManagerDot.dot file name from the client system and delete it. Retest the scenario.
Pegasystems Inc.
US
This could also be environment related. Is it setup similarly? Especially with respect to security? For example does this newer environment use a later version of TLS? I'm assuming you are not seeing any obvious errors, right? (e.g. Failed to re-attach server session)
Can you try network tracing this and checking if there are any error codes, and if not, inspect the cookies and compare them with what is seen in the working environment?
Belvnesheconombank
BY
Hi and thanks for your answer! Yes, I think you are thinking in the right direction with one exception: I've got a little different exception (it replaces all of the pega:reference tags in generated document): Failed to (re)attach Process Commander session. Unfortunately I didn't find any articles or discussions about this error.
Then I thought that this error might appear due to IE security settings and I added my https link to trusted sites list. After this pega:reference tags was blank.
It's very strange for me but now when I deleted my server link from trusted sites list (to get a screenshot of document for this post) and when I added link back to trusted sites list I see "Failed to (re)attach Process Commander session." error anyway.
Pegasystems Inc.
US
This definitely sounds security/environment related. If you are unable to find key differences between environments or through network traces/cookies this will probably require a deeper investigation through a support case (INC).
Belvnesheconombank
BY
Look, here is generated document thru CreateMergeWordDoc on server which connected by HTTP instead HTTPS (there is no certification validation). On this screenshot you can see that merge functionality didn't work as expected (I turn on "Show field codes" option after generation)
Accepted Solution
Updated: 22 May 2020 2:43 EDT
Belvnesheconombank
BY
Hi guys! Here is the solution from MSP. And it works:
Perform the following local-change:
- Verify the Location Records > SysAdmin > Dynamic System Settings (DSS).
- Filter under Owning Ruleset Pega-Engine.
- Search for the prconfig/initialization/advancedSession/default Setting purpose.
- If the Setting purpose is unavailable, create it and set its value as False. If the Setting purpose is already available, then change its value to False.
- Save the settings.
- Log out and restart the Pega server.
- Clear the browser cache and Temp files from the user's system.
Search for the WordMacroManagerDot.dot file name from the client system and delete it. Retest the scenario.