LinkedIn
Copied!

Table of Contents

eForm File rules - Completing the Create or Save As form

The eForm file rules are no longer being actively developed and will be deprecated in Pega Platform 8.7. Using eForm file rules does not follow Pega development best practices. Consider other implementation options instead.

Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.

Based on your use case, you use the Create, Save As, or Specialization form to create the record. The number of fields and available options varies by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields using the following Developer Help topicsusing the following Developer Help topics:

This information identifies the key parts and options that apply to the record type that you are creating.

Create an eForm file rule by selecting eForm File from the Integration-Mapping category.

An eForm file rule has three key parts:

Field Description
Apply to

Select the name of the class the new rule belongs to. An eForm file and a corresponding eForm map rule have the same Apply to class.

File Name Enter the name of this file. Choose a name suitable for UNIX and Windows, using lowercase letters only. If you enter an uppercase letter, the resulting extracted file name is converted to lowercase letters.

Subdirectories specific to the RuleSet and version are created to hold the extracted form file.

File Type (extension) Optional. Enter the extension for this type of file, typically PDF.
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.