According to http://docs.alfresco.com/5.0/pra/1/concepts/act-processes-get-processes.html there is a sample filtering of data:
where=( startUserId='kermit' AND businessKey='55' AND variables/nameB MATCHES('elmo%') ).
This is case sensitive, request is to make the MATCHES operator case insensitive.
This would be change applicable to any REST api's that afford the use of the MATCHES operator for parameters which are string values.
- Using Share UI, start a workflow (this example I only had one in so simple test)
- Using basic FF RestClient
- get a process or task to test with for example:
- Using one of the string variables from the "processVariables" in json response to specifically search for case match
(if using tasks you can use any of the parameters that allows MATCHES operator):
- Search the same "processVariables" test case insensitive match:
- Regardless of case, the MATCHES clause should match
[MER 10/03/2016 - Please note that this expected behaviour is not correct. The expected behaviour is that the query is case sensitive. Instead a new prefix was added to the query to enable a case insensitive search. Please see the linked issue for further details]
- MATCHES clause is case sensitive
- MATCHES can only be used for string values
- (processes) http://docs.alfresco.com/5.0/pra/1/concepts/act-processes-get-processes.html
- (tasks) http://docs.alfresco.com/5.0/pra/1/concepts/act-tasks-get-tasks.html
Alex Strachan noted that when looking through the code, the class org.alfresco.rest.workflow.api.impl.ProcessesImpl calls a generic class called WhereClauseParser(). This parser class seems to do a direct comparison of objects (there is no toLower() or anything called before comparisons).