Below are the steps needed to add fields to the smart PDF. During this process I uploaded a smart PDF to Pega but I was unable to extract fields. I uploaded the smart PDF to a tool (online) PDF Escape and then downloaded the PDF (making no changes or using any function from PDF Escape). When I uploaded the smart PDF to Pega for the second time, I was able to read the fields in Pega.

Pega EForm Creation Example

1. Upload your smart PDF form via the EForm Wizard
2. Select > Designer Studio > Integrations > Tools > PDF for EForm Wizard

1. Select the Class for the PDF
   1. The Class is Applied To your Case you created. In this example we are applying the PDF to the class OJ7XGI-Universal-Work – this is the lowest level in the Class Structure meaning any Cases built higher in the structure can inherit/reuse the PDF.

IMPORTANT: Note the Class the configuration applies to for use later in the configuration

1. Choose the PDF to import a. Name the PDF Form

1. On the next screen Select the fields from the PDF you wish to populate with information from your Case.

1. Map the fields to properties from you Case.
   1. Open the App Explorer in the left Tool Column
   2. Expand Data Model > Properties to view the available properties
   3. In the Property Name Field, place your cursor and Click the Down Arrow to

display case properties. If the Properties do not display, enter a period “.”then the property name (ex: the LastName property == .LastName)

Note: If after creating the form the fields are not mapped properly you can return to this screen and adjust the mapped properties

1. Accept the default information and make note of the Rule-File-eForm Form Name and Class for use when configuring the PDF execution step.
2. In the Case Explorer Select you Case to configure the Life Cycle

1. Open the Process
2. Add a Utility Shape

1. Open the Utility Shape
   a. Enter a Name for your Rule (ex: JimsEFormCreation)
   b. Select the Configuration Icon to the right of the Rule name

1. See an Activity is ready for configuration
2. In this Activity, we will work with the Page & Classes, Parameters, and Steps tabs
3. Select > Pages & Classes tab
   1. Enter the Page Names as displayed below
   2. For the Page Names EFormPage and PDF2 the Class == Code-Pega-eForm
   3. For the pyWorkPage page name the Class == the same class level you identified for the PDF you mapped above

1. Select > Parameters tab
2. Select > Steps tab
3. Expand Step 2 -- Property-Set
   1. Enter the PropertiesName and PropertiesValue as defined below

1. Enter the Parameters as defined below
2. Save your work

1. Enter the 7 steps as Displayed below
2. Step 3 == “Call GetEFormFromRuleFileEForm” without the parenthesis

1. Expand Step 3 -- Call GetEFormFromRuleFileEForm

1. ClassName == ...Enter the Class the PDF is applied to
2. FileName == ...the PDF name you defined above
3. FileType == PDF

1. Expand Step 4 -- Call GenerateEForm
2. Expand Step 5 -- Property Step

1. MapPurpose == ...the PDF FileName identified Step 3
2. TargetEFormPage == PDF2 (the page name identified in the Pages & Classes tab

1. Enter the PropertiesName and PropertiesValue as defined above
2. Expand Step 6 -- Call AttachEForm

1. 23. Method Parameters
2. Save your Work
   25. Close the Edit Activity Tab 26. Save the Process
   27. Save the Case Life Cycle
   28. Test the EForm Configuration

1. PageName == pyWorkPage (defined in the Pages & Classes tab)
2. InsHandle == .pzInsKey (this defines the Case ID)
3. FileName == ...the PDF FileName identified Step 3
4. eFormPage == PDF2 (defined in the Pages & Classes tab)
5. pyNote == enter a short description to be Displayed as the Attachment Name, for Auditing purposes, and to become part of the attachment metadata