Support Article
Silverlight migration to server-side document generation
SA-11453
Summary
User has new functionality with generating MS Word document at server side, but still using old scheme with Silverlight.
Now the requirement is to know the procedure to migrate from Silverlight to new generating scheme.
Resolution
The explanation for this behavior is as follows:
The problem has been created by Chromium’s change of support regarding NPAPI plug-ins.
Below some information regarding which Word Generation functionality does *not*, and which Word Generation functionality still *does* make use of Silverlight plug-ins.
It turns out that the only functionality that makes use of the new ML8 server-side word document generation is the ‘Generate Application Document’ (DCO) functionality - no other other Word Merge functionality uses this.
“Document merging” refers to the ability to generate Word documents by combining the data collected during case processing with pre-defined Word templates. Document merging can be leveraged by referencing the CreateMergedWordDoc flow action at design-time. This is not to be confused with DCO document generation, which has been migrated server-side in Pega 7.1.8.
There are plans to replace all the controls but this functionality is scheduled to be resolved near future.
So unfortunately there is no PRPC way to allow users of the latest chrome version to work on the Chrome Limitation.
For Chrome 42 you can re-enable the NPAPI features that the latest chrome tried to kill off.
However, this works as a temporary measure as later versions for example Chrome 45 no longer allows this anymore.
All Pega can recommend currently to drop using Chrome and start using Firefox or IE browsers for Word Merge functionality.
Published July 23, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.