Your application can create a Portable Document Format (PDF) file from the output of a summary view or list view report and attach it as a file attachment to a work object. 5.5 GRP-306
This can occur automatically, through a flow, or on user request, through a flow action.
1. Create and test the summary view or list view rule.
2. Create an activity in your application's work class with three steps:
Action
parameter to Prepare
.3 . If you want the report output to be saved as an attachment automatically at a point in a flow, add a utility shape that calls this activity.
4. If you want the activity to run upon user request, create a local flow action that captures relevant parameters, such as those required by the list view or summary view report, as property values. Identify your activity in the After this action... area of the Action tab of the flow action.
5. Test.
The Rule-Obj-ListView.AttachAsPDF activity accepts five input parameters:
DefinitionPageName
— The name of the clipboard
page containing the list view rule.DataPageName
— The name of a
Code-Pega-List page that contains report output, produced
by the execution of the ShowView activity.AlternateStream
— Optional. Identify the Stream
Name key part of an HTML rule that is to be applied to the
contents of the DataPageName
page before conversion to
PDF format.PDFName
— Identify a file name for the
generated PDF file. Start the name with a letter and use only letters
and digits, followed by a period and the file type suffix
pdf.InsHandle
— The internal key
(pzInsKey property value) of the work objectSee Pega Developer Network article PRKB-25635 Generating PDFs and attaching them to a work object or viewing them in a web browser.
These related activities (all Final rules ) are also available:
These facilities use the PublicAPI method
getPDFUtils()
, which calls upon JTidy, CSSToXSLFO, Apache
FOP, and XSLT facilities to convert HTML to PDF.
Understanding
work object attachments
About List View rules About Summary View rules |