Apply logic to data import fields
Valid from Pega Version 7.3.1
When importing data from an external system, you can translate data fields into values that can be read by Pega® Platform. From the Import wizard, you can do the following actions:
- Apply a decision tree or decision table to the data that is imported for a field.
- Use imported data for a field to look up a value in another record. For example, you can look up the key of a record that uses an external identifier to populate a foreign key field.
- Create templates that contain business logic, which eliminates the need to handle data transformations manually during preprocessing.
For more information, see Transforming data during import.
Ability to map JSON to clipboard properties by using a data transform
Valid from Pega Version 7.3.1
You can now map the entire JSON file or individual properties to and from the clipboard by using a data transform. Using a data transform makes it faster and easier to connect your Pega® Platform to your system of record.
For more information, see Data transforms.
Data validation before importing
Valid from Pega Version 7.3.1
Data imported into a data type is now validated before it is imported. Validating data before importing it ensures that the data is valid and reduces the amount of time required to manually analyze and validate your data.
For more information about importing data into a data type, see Importing data for a data type.
Enable different REST service rules for distinct resource URIs
Valid from Pega Version 7.3.1
You can now specify different service REST rules for distinct resource URIs. This functionality provides different processing options, request handling, and response handling for each distinct resource URI. Additionally, it eliminates the need to develop and maintain complex logic to handle all possible resource URI paths.
For more information, see Distinct URI specification for service REST rules.
Use fast processing option does not work
Valid from Pega Version 7.3.1
The Use fast processing option on Connect REST and Service REST rule forms does not work unless you obtain the HFix-43000 hotfix from Global Customer Service.
Use the following data model guidelines when using fast processing:
- The JSON property names and the clipboard property names must match.
- The JSON tree structure and the clipboard tree structure must be similar.
- The scalar arrays in JSON must be mapped to the clipboard as page lists.
- Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.
In addition, page groups, value groups, and Java objects are not supported by fast processing.