Skip to main content


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

Flow-based requirements

Updated on January 18, 2022

Some business needs involve more than document validation. They may involve performing business processes that include multiple steps and multi ple users, external integrations, complicated process branching, and so on. In this case, the application launches a requirement on a process flow written specifically to meet the business need. This allows a requirement to support complicated business processes in addition to document validation.

Configuration

In the Requirement above, there are no document entries at all. Instead, the Processing Flow Class and Processing Flow Name fields indicate that when this Requirement rule is instantiated as a Requirement object, it will be launched on the following flow in order to be satisfied.

Runtime results

At runtime, the Requirement rule shown above creates a Requirement object and launches it on the specified flow. Then, you receive the first assignment of the flow.

The Where Am I screen shows that you are currently on the first assignment of the specified flow.

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