@Neminath

Here’s a clean way to do it without touching the locked CustomerData data flow. Use Customer Profile Designer to add a calculated field on the Customer entity called Age. In Profile Designer, create a new calculated attribute and set the expression to the year difference between current date and Date of Birth, rounded down. This makes Age available on the Customer page at run time for both real time and outbound. You can then use .Customer.Age directly in Eligibility, Applicability, and Arbitration. If you want a platform-level approach, add a non-persisted property Age on the Customer class and drive it with a Declare Expression. The Declare Expression should compute years from .DateOfBirth using a function that handles leap years and birthdays. Expose that property and reference it in strategies and engagement policies. Another safe option is to enrich in an extension strategy. In Next Best Action Designer, open the Customer extension strategy and add a Set Property to compute Age from DateOfBirth. That strategy runs every invocation and writes Age onto the Customer page for downstream shapes. For outbound, the same extension strategy is reused so you get Age consistently. If you prefer pure expressions, create a rule utility function AgeInYears(DOB) and call it from either the calculated field or the Set Property. Keep Age transient; do not persist it to the customer table. Test with edge cases like birthdays today, Feb 29, and null DOB. Cache is not needed since the math is cheap. Pick one method and standardize it across RTC and outbound so your eligibility rules behave the same.