Skip to content

ServiceNow Integration - Search Tickets is unable to pass a sysparm_ parameter successfully #4957

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 13, 2025
Merged

ServiceNow Integration - Search Tickets is unable to pass a sysparm_ parameter successfully #4957

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d2b5e3b
Updated service now integration
mahendrak-sumo Jan 13, 2025
a46a28f
Merge branch 'main' into CSOAR-2745
mahendrak-sumo Jan 13, 2025
39d5488
Updates from review
jpipkin1 Jan 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 16 additions & 15 deletions .../platform-services/automation-service/app-central/integrations/servicenow-v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl';

<img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/servicenow-v2.png')} alt="servicenow" width="100"/>

***Version: 2.5
Updated: May 31, 2024***
***Version: 2.6
Updated: Jan 13, 2025***

ServiceNow V2 SaaS is for technical management support - create, update, and gather ServiceNow ticket information.

Expand Down Expand Up @@ -44,26 +44,26 @@ Query used to filter the result set.

Building the query:

Syntax: sysparm\_query=&lt;col\_name&gt;&lt;operator&gt;&lt;value&gt;.
Syntax: `<col_name><operator><value>`

* &lt;col\_name&gt;: Name of the table column to filter against.
* &lt;operator&gt;: Supports the following values:
=: Exactly matches &lt;value&gt;.
!=: Does not match &lt;value&gt;.
^: Logically AND multiple query statements.
^OR: Logically OR multiple query statements.
LIKE: &lt;col\_name&gt; contains the specified string. Only works for &lt;col\_name&gt; fields whose data type is string.
STARTSWITH: &lt;col\_name&gt; starts with the specified string. Only works for &lt;col\_name&gt; fields whose data type is string.
ENDSWITH: &lt;col\_name&gt; ends with the specified string. Only works for &lt;col\_name&gt; fields whose data type is string.
* &lt;value&gt;: Value to match against.
* `<col_name>`: Name of the table column to filter against.
* `<operator>`: Supports the following values:
* `=:` Exactly matches `<value>`.
* `!=`: Does not match `<value>`.
* `^`: Logically AND multiple query statements.
* `^OR`: Logically OR multiple query statements.
* `LIKE`: `<col_name>` contains the specified string. Only works for `<col_name>` fields whose data type is string.
* `STARTSWITH`: `<col_name>` starts with the specified string. Only works for `<col_name>` fields whose data type is string.
* `ENDSWITH`: `<col_name>` ends with the specified string. Only works for `<col_name>` fields whose data type is string.
* `<value>`: Value to match against.

All parameters are case-sensitive.

Queries can contain more than one entry.

For example: sysparm\_query=&lt;col\_name&gt;&lt;operator&gt;&lt;value&gt;[&lt;operator&gt;&lt;col\_name&gt;&lt;operator&gt;&lt;value&gt;]
For example: `<col_name><operator><value>[<operator><col_name><operator><value>]`

For more info please check the official API doc: &lt;https://developer.servicenow.com/dev.do#!/reference/api/sandiego/rest/c_TableAPI#table-GET&gt;
For more information check the [ServiceNow API documentation](https://developer.servicenow.com/dev.do#!/reference/api/xanadu/rest/c_TableAPI#table-GET).

**Create Ticket**

Expand Down Expand Up @@ -92,3 +92,4 @@ Ticketing System
* June 30, 2023 (v2.3) - Integration code improved.
* April 5, 2024 (v2.4) - Fixed an issue that prevents the resource testing to work correctly.
* May 31, 2024 (v2.5) - Fixed an issue in actions **Create Ticket** and **Update Ticket** in which the JSON Query field was not visible.
* Jan 13, 2025 (v2.6) - Modified hint of the **query** field as it was misleading.
Loading