Behavior of addOrCondition with search_key via REST APIIssue Actual behavior: When running script using 'CONTAINS' of addOrCondition with search_key via REST API , then it shows '=', not 'CONTAINS'. Note that it say '=' if the script is run via 'Scripts - Background', so this issue only occurs via REST API. Expected behavior: it should show CONTAINS in case of above condition. Sample reproduce steps are the followings. Steps1. In Scripted REST API, Create a new one Ex:Name: 20210914testNameAPI ID:20210914testApiid Steps2. Create Resource as below then submit to use addOrCondition with search_key Name: 20210914testResourceName Script:==========================(function process(/*RESTAPIRequest*/ request, /*RESTAPIResponse*/ response) { var search_key = request.queryParams.search_key;gs.info(typeof search_key); // search_key = String(search_key); var gr = new GlideRecord('incident');if(search_key) {var qc = gr.addQuery('description', 'CONTAINS', search_key);qc.addOrCondition('short_description', 'CONTAINS', search_key); }gs.info('query: ' + gr.getEncodedQuery());gr.query(); return []; })(request, response);========================== Steps3. In REST API Explorer , Enter「search_key / test」in Query parameters, then send. Steps4. In System Logs > System Log > Script Log Statements then see gs.info showing '=test" , not 'CONTAINS'. See the followings: query: descriptionCONTAINStest^ORshort_description=test ReleaseAll ReleaseCauseThis is current expected behavior because request.queryParams.(parameter) returns an object, which is transformed to a List - only when transformed to a String can CONTAINS be used.ResolutionUse the String for search_key such as the following. search_key = String(search_key); Here are example on this. Steps1. Comment off in line 6 of the script of Description section to use string as below Steps2. Then see the result showing 'CONTAINS' query: descriptionCONTAINStest^ORshort_descriptionCONTAINStest