Conditional Processing: Request is Contained within Expression 1

Question

I believe I have found a bug with the Process Conditional Processing logic, where "Request is Contained within Expression 1" is used.
Here are three of the buttons that I have on my page:
GET_RES_CIVIC_ADDR - This button is displayed among the Region Items (Region 2)
CRE_RES_CIVIC_ADDR - This button is displayed among the Region Items (Region 2)
ADD - Automatically created as part of a Tabular Form (Region 3 - Updateable Report).
I have a process that is conditional on either GET_RES_CIVIC_ADDR or CRE_RES_CIVIC_ADDR being run (meaning the Process has its "Conditional Processing" "Condition Type" set to "Request Is Contained within Expression 1" and where "Expression 1" is set to "GET_RES_CIVIC_ADDR,CRE_RES_CIVIC_ADDR" (without the quotes).
The problem I have encountered is that this Conditional Process also gets run if I submit the ADD Button. The reason being is that the word "ADD" is contained within the Expression 1 string "GET_RES_CIVIC_ADDR,CRE_RES_CIVIC_ADDR".
Note that if I change the REQUEST value for these two Item Level Buttons to names that do not contain the word ADD, the problem is fixed.
Is this a known bug? Or do I have to edit the value of Expression 1, so that each Button Name/Request Value is enclosed in quotes or the like?

Answer 1

Scott,
I was under the impression that the values in Expression 1 would be a list of comma delimited values (e.g. A,B,C and not ABC) and would be evaluated individually. However, you are correct. It is being evaluated as advertised.
A note for others that have this problem - the evaluation of :REQUEST is Case Sensitive, so if the Item Level Button had been named 'Get_Res_Civic_Addr' (using Camel Case) instead of 'GET_RES_CIVIC_ADDR', (Upper Case), there would not have been a match with the 'ADD' Request and therefore the After-Submit process would not have been run by the ADD button.
To prevent this in the future, we are going to standarise using the PL/SQL Expression Condition (checking :REQUEST) and also ensure that our Item Level Buttons "Request Value" is Camel Case (just an extra precaution).