Hello folks, Hope you are doing good.
Recently we encountered a client's requirement which led us to have two separate condition-services with exact same code but opposite output. In one case true and false for another. We can enhance existing behaviour by having one more attribute in the seca/eeca rule. As currently by default, the result expected from condition-service is always true. We can provide its control to the developer. For eg. <condition-service service-name="isSalesOrder" *boolean-field="true */* false"*/> This boolean-field will illustrate the expected boolean result from the available conditionReply result field in the defined condition-service. In this manner we give more control to developers and reduce duplicacy of code. Please share your thoughts on this. -- Best Regards, Suraj Khurana Senior Technical Consultant
