Skip to main content


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

Requirements - Completing the Parameters tab

Updated on January 18, 2022

This tab lists the parameters for the various Rule-Requirement rules on the Requirement Rules tab. The names are read-only, because the names of the parameters and their descriptions should be exactly the same as they are on the corresponding Rule- Requirement rules. You can edit the IN/OUT and Property columns. Below is a more detailed description of the columns on this tab.

This tab contains the fields described in this table.

FieldDescription
NameThe name of the Parameter used to exchange data between the Requirement work object and the parent case.
DescriptionThe description of the parameter used to exchange data between the Requirement work object and the parent case.
In/Out/Both

Accepts parameters IN / OUT / BOTH.

IN –Indicates that the parameter is passed IN to the parent case using this Requirement Set rule from the Requirement object at the time the requirement is validated.

OUT- Indicates that the parameter is passed OUT to the requirement object from the parent case using this Requirement Set rule when the requirement is created.

BOTH –Indicates that the parameter is passed OUT to the requirement object from the parent case using this Requirement Set rule when the requirement is created, and also passed IN to the parent case using this Requirement Set rule from the Requirement object at the time the requirement is validated.

PropertyThe name of the property that contains the data to be mapped between the parent case and the parameter page. This property must be a single value scalar property that is present in the Applies To class of the Requirement rule definition or an ancestor class.

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