Skip to main content


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

Understanding and building the structures in Requirements

Updated on January 18, 2022

To enable reuse, the three core components of Requirement Sets, Requirements, and Documents exist as their own separate building blocks. A single type of Document can be used in different ways across multiple Requirements, and a Requirement can be used in different ways across multiple Requirements Sets.

At the appropriate stage in the process, the parent case will create a Requirement Set and the necessary subcases for each Requirement in that set. The Requirement Set structure allows the passing of parameters to and from the underlying Requirements work objects for use in processing. After each Requirement in the set is processed and satisfied, the parent process can continue.

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