I'd be intersted to know if anyone else has encountered this issue which appears to be a bug in OPA?
I have a rule which triggers a question during the interview where the value of the text attribute 'the proceeding matter type meaning' = "Community Care"'.
The value "Community Care" appears as a conclusion under a legend in the table named "matter type meaning" on a tab named "Matter Types".
This is derived from condition 'the proceeding matter type code' which is an input to OPA.
On the declarations tab I have an attibute, 'the community care test is applicable to the proceeding', which has the legend "community care".
The legend "community care" appears on a tab in the rule table named "Proceeding".
The values for 'the community care test is applicable to the proceeding' are derived from condition 'the proceeding name' which is an input to OPA.
When testing the rule base the question I was expecting to appear did not appear. The reason appears to be that the rule table is using the conclusions under the legend "community care" on the "Proceeding" tab as opposed to the conclusions under the legend "matter type meaning" on the "Matter Types" tab (see the excerpt from the summary in the debugger below).
The conclusion "Yes" does not appear at all under the legend "matter type meaning" but does under the legand "community care", and the fact that the legend "community care" is not capitalised, whilst the value "Community Care" is, does not make any difference.
I have resolved the issue by checking all legends against the values for the conclusions throughout the rule table, and altering those legends that have the same values as some conclusions.
Hi thanks for raising this. Yes you're right using legends that are the same as conclusions in the one excel rule document causes some ambiguous behavior but we believe this is caught by a validation error from 10.3 onwards. Can you confirm which version you are using? The latest version of OPA is 10.4.4.