Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Passing scalar data using parameters

Updated on January 18, 2022

In this approach, you use the Parameter tabs of the Requirement rule and the Requirement Set rule to specify the data that is passed between the parent case and the Requirement object.

Configuration

The parameter page of the Requirement Set rule, which is normally defined on the parent case class, defines the properties in the parent case that are output to or received from the Requirement object. The following figures show both tabs of the Requirement Set MortgageUnderwritingReqSet rule. The Requirement Rules tab shows that two requirements are created when this Requirement Set is processed. The Parameters tab shows that two parent case properties are mapped to or from the MortgageCreditReport requirement:

The parent case .pyWorkParty (Applicant).TaxIDNbr property is mapped out from the parent case to the SocialSecNum parameter when the requirement is created.

The Credit Score parameter is mapped in to the parent case property .CreditScore when the requirement is validated.

In an analogous way, the parameter page of the Requirement rule defines the properties in the Requirement object that is output to or received from the parent case. Continuing the example below, the Parameter tab of the MortgageCreditReport Requirement rule shows that two Requirement object properties were mapped to or from the parent case:

The SocialSecNum parameter is mapped in to the .MortgageCreditReportSSN Requirement object property when the requirement is created.

The .MortgageCreditReportScore Requirement object property is mapped out from the Requirement object to the Credit Score parameter when the requirement is validated.

Be sure that you define all these properties in the same or an ancestor class of the class in which the Requirement rule is defined.

The DistributeCreditReportData Input activity runs after you load all the input parameters into the Requirement to move the input data to individual documents of the requirement as needed for validation.

The AssembleCreditReportData Output activity runs before all the output parameters are passed back to the parent case to move the validated data of individual documents to the requirement level to be passed back through parameters.

Runtime results

As a result of the parameter settings in the Requirement Set and Requirement rules above, data is passed between the parent case and the Mortgage Credit Report Requirement object as follows. At the time the Requirement is created:

  • The pyWorkParty (Applicant).TaxIDNbr parent case property is mapped out from the parent case to the SocialSecNum parameter.
  • The SocialSecNum parameter is mapped in to the .MortgageCreditReportSSN Requirement object property.
  • The DistributeCreditReportData Input activity moves the input data to individual documents of the requirement as needed for validation.

At the time the Requirement is validated:

  • The AssembleCreditReportData Output activity moves the validated data of individual documents to the requirement level to be passed back through parameters.
  • The .MortgageCreditReportScore Requirement object property is mapped out from the Requirement object to the Credit Score parameter.
  • The Credit Score parameter is mapped in to the .CreditScore parent case property.

This results in the parent case receiving the credit score from the Requirement object at the time the requirement is validated.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us