When you filter data in a Quality project, you can optionally create a Decision Point process, that enables you to split the data based on the filtering condition you define. A Decision Point can be used anywhere in a process flow and lets you analyze the passing/failing rows or use only the passing rows in the following processes.
There are two ways to create a Decision Point process:
- Adding a Decision Point process . If you add a Decision Point process, it becomes a separate process branch and neither the passing nor the failing rows will be processed. The original process flow remains unchanged. Use this method if your focus is to analyze the passing/failing rows and examine the data.
- Inserting a Decision Point process . If you insert a Decision Point process, then the passing rows will become the input to the following processes and the failing rows will not be processed. Use this method if you want to process only the passing rows in addition to analyzing the passing/failing rows.
Guidelines
Note the following guidelines when working with the Decision Point process:
- The Decision Point process will split the data only to passing and failing rows. If you want to split the data to three or more groups, use the Merge/Split Utility.
- The Decision Point process is designed for batch only and cannot be deployed in a real-time environment. If a real-time project includes the Decision Point process, the process will be excluded when the project is deployed for use in real time.