AnsweredAssumed Answered

Is there any specific reason for not returning from decision table after a row condition is satisfied?

Question asked by divya.sandadi@cognizant.com on Aug 29, 2016
Latest reply on Sep 5, 2016 by divya.sandadi@cognizant.com

Generally in decision table once a row condition is satisfied we can return from Decision table instance, there is no need of executing all the other rows.

Is there any specific reason for not returning?

For Example:

Design: There are 100 rows in decision table.

Problem: If the condition is met at the second row still it continues to check for other rows in the table, which is not required.

Solution: Can we add a return; statement like below? Are there any performance issues or anything else impacted because of adding return.

 

Thanks in Advance

Outcomes