What is use of business condition when we have already when rule present inside Pega Customer service 87 onwards ?
While When rules continue to be a powerful tool for condition evaluation in Pega, business conditions introduced in Pega Customer Service 8.7 onwards provide a more streamlined, maintainable, and user-friendly approach for defining and managing conditions. They enhance reusability, maintainability, and clarity, making them a preferred choice for modern Pega applications, especially in complex customer service scenarios.
By leveraging business conditions, you can ensure that your application logic is consistent, easier to manage, and accessible to a broader range of stakeholders, ultimately leading to more efficient and effective application development and maintenance.
Business conditions define the criteria that support consistent, personalized customer interactions across channels. The business conditions allow for the dynamic configuration of the Interaction Portal in which CSRs view the most relevant and actionable information about the customers with whom they engage.
How they are different from when conditions – Difference is in the creation and configuration only a rule created from app studio and used inside app studio works like when is called business condition . It super user friendly , it created because of citizen developer is not well equipped to understand about the when rule complexity .
So Pega promoted app studio capacity towards citizen developer also and supported this functionality.
While creation of any when rule if you want to showcase inside the app studio business conditions then just made that rule “mark as relevant” and also tag under business condition.
Business condition are made for Citizen developer basically . Which can be created from app studio also.