+3
There was a Use case where numeric calculations has to be applied for resulting field based on the case conditions in Rules.
In the Rules engine, Utilizing the calculation field inside the case expression field is not possible.
So we have created multiple result fields with numeric calculations required in a transformation and used the case expression in the next transformation to utilize the created result fields in case condition.
+2
There was a Use case where numeric calculations has to be applied for resulting field based on the case conditions in Rules.
In the Rules engine, Utilizing the calculation field inside the case expression field is not possible.
So we have created multiple result fields with numeric calculations required in a transformation and used the case expression in the next transformation to utilize the created result fields in case condition.
Yup,Good one Satya.
I have already posted similar one, may be we need to upvote either of us.
https://community.gainsight.com/cs-ideas-21/can-we-have-functions-inside-case-statement-for-a-rule-36964
This will significantly reduce the number of transformations in a rule. This is something really useful and really basic necessity.
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
