Hi Hermy,

I haven't tried this yet - but I took a look at the source code of the Engine Class used to call PD4ML  - and it looks like we might actually over-ride any PageInsets within the engine with a call like this:

aConverter.setPageInsets(new Insets(20, 10, 10, 10));

aConverter.setHtmlWidth(950);

In fact: looking back at this - I'm not sure whether your Local Change can be having any effect on the resultant PDF here ? (maybe the other settings such as 'print actual size' etc are the parameters that are causing the end-effect here?).

So it looks like (unfortunately) that will not be able to achieve what you need to do with HTMLTOPDF at this point....

As an alternative - you could consider generating a WORD file ?

You could look into using PRPC correspondance rules here - or you could try the suggestion below.

I googled for a starting point and found this:Make address guesswork a thing of the past | VA Pro Magazine

Which just creates a Text Box in the WORD file - where you can position your address for the Windowed Envelope.

I then saved the document in 'Word 2003 XML Document' format (a single-page XML format :Microsoft Office XML formats - Wikipedia, the free encyclopedia -it's an older system now superceded by Open Office - but still useful sometimes).

The resulting XML contains quite a bit of stuff (some of which I was able to trim-out without affecting the resultant document - such as document author etc) - the important bit is this fragment:

<v:shape id="Text Box 1" o:spid="_x0000_s1026" type="#_x0000_t202" style="position:absolute;
margin-left:-18.65pt;
margin-top:19.75pt;
width:282pt;
height:102pt;z-index:1;visibility:visible;
mso-wrap-style:square;mso-wrap-distance-left:9pt;mso-wrap-distance-top:0
;mso-wrap-distance-right:9pt;
mso-wrap-distance-bottom:0;
mso-position-horizontal:absolute;mso-position-horizontal-relative:text;mso-position-vertical:absolute;mso-position-vertical-relative:text;v-text-anchor:top"  strokeweight=".5pt">
<v:textbox>
                                <w:txbxContent>
                                    <w:p wsp:rsidR="00A6337B" wsp:rsidRDefault="00A6337B" wsp:rsidP="00A6337B">
                                        <w:pPr>
                                            <w:contextualSpacing />
                                        </w:pPr>
                                        <w:r>
                                            <w:t>John Doe,</w:t>
                                        </w:r>
                                    </w:p>
                                    <w:p wsp:rsidR="00A6337B" wsp:rsidRDefault="00A6337B" wsp:rsidP="00A6337B">
                                        <w:pPr>
                                            <w:contextualSpacing />
                                        </w:pPr>
                                        <w:r>
                                            <w:t>Pegasystems,</w:t>
                                        </w:r>
                                    </w:p>
                                    <w:p wsp:rsidR="00A6337B" wsp:rsidRDefault="00A6337B" wsp:rsidP="00A6337B">
                                        <w:pPr>
                                            <w:contextualSpacing />
                                        </w:pPr>
                                        <w:r>
                                            <w:t>Corporate Headquarters</w:t>
                                        </w:r>
                                    </w:p>
                                    <w:p wsp:rsidR="00A6337B" wsp:rsidRDefault="00A6337B" wsp:rsidP="00A6337B">
                                        <w:pPr>
                                            <w:contextualSpacing />
                                        </w:pPr>
                                        <w:r>
                                            <w:t>One Rogers Street</w:t>
                                        </w:r>
                                    </w:p>
                                    <w:p wsp:rsidR="00A6337B" wsp:rsidRDefault="00A6337B" wsp:rsidP="00A6337B">
                                        <w:pPr>
                                            <w:contextualSpacing />
                                        </w:pPr>
                                        <w:r>
                                            <w:t>Cambridge, MA 02142-1209</w:t>
                                        </w:r>
                                    </w:p>
                                    <w:p wsp:rsidR="00A6337B" wsp:rsidRDefault="00A6337B" wsp:rsidP="00A6337B">
                                        <w:pPr>
                                            <w:contextualSpacing />
                                        </w:pPr>
                                        <w:r>
                                            <w:t>U.S.A</w:t>
                                        </w:r>
                                    </w:p>
                                </w:txbxContent>
                            </v:textbox>
</v:shape>

And just to prove it (almost!) fits a real envelope:

It should be possible to dynamically replace the address components with the values of PRPC Properties here.

How to render this to WORD ? You could use XSLT (PRPC has an activity for this already: "XSLTranslate") to 'plugin' the values you need; or you could use a HTML Stream Rule - and use Pega JSP TAGS to do the value-replace.

If you need to deliver the File to the end-user (ie, they need to download it) - you will probably need to set the MIME type correctly in the HTTP headers.

There is an Activity "Rule-Obj-HTML|ViewExcelData|Pega-WB:07-10-01" (I'm looking at a PRPC 7.1.7 here) which does a similar thing for downloading EXCEL files, which does this:

ClipboardPage objHeadersPage = tools.findPage("pxRequestor").getProperty(".pyHTTPResponseHeaders").getPageValue();

objHeadersPage.putString("contentType" ,"application/vnd.ms-excel");

objHeadersPage.putString("ContentDisposition" ,"attachment;filename=ExportData.xls");

"

I think (from here for instance: Office 2007 File Format MIME Types for HTTP Content Streaming - VSOfficeDeveloper: Known Problems, Bugs, and Fixes - Sit…) that the contentType will need to change to "application/msword" or one of the others (2003 format is not listed here explicitly actually...)