We had a production issue in PRPC 6.3 SP1 - Declare expression does not trigger in production but working in non-prod. Also,revalidate and save didn't work in production and non-prod for same declare expression.
Declare expression started working after execution of below steps.
1) Either remove that reference entirely if it is not needed, or re-root your declare-expression to be applied to the subclass of main rule class. 2) Resave the declare expression again.
But,didn't get any satisfactory answer for below questions in SR-A23881. It would be greatly appreciated if anyone provide the answers for below questions.
1) Is there a way to go back and check the old declarative network snapshot to see to identify root cause of failure?
2) Why will the product behave differently in lower and in production for same code base?
3) What is the set of rule apart from this declare expression that we need to look at?
What was the solution to the validate issue? Did you remove the reference? or re-root the rule?
I'm curious how the declare-expression originally managed to be saved with the validate issue existing. I can understand it being imported from non-prod to prod with the validate issue existing, but I'm not clear how it got saved in the first place.
The declare-expr had three input properties, which we can designate as A, B, and C, and when the decl-expr fired, it computed a new value for property D as a function of A, B, and C.
When it was not working properly, I seem to recall you said that some of A, B, and C would cause it to fire, but others of them didn't. Is that correct? Or did no changes cause it to fire?
Of course, after it started firing again, any change to A, B, or C causes it to fire.
Posted: 7 years ago
Posted: 4 May 2016 13:55 EDT
Abhishek Mishra (ABHISHEK-12)