Add long running integration link to description files (#37867)

* Add long running integration link to description files * revised text per Shahaf * added microsoft teams file * added rn --------- Co-authored-by: sbenyakir <[email protected]>
demisto · Jan 5, 2025 · 323651f · 323651f
1 parent 58fefe8
commit 323651f
Show file tree

Hide file tree

Showing 28 changed files with 83 additions and 15 deletions.
diff --git a/Packs/EDL/Integrations/EDL/EDL_description.md b/Packs/EDL/Integrations/EDL/EDL_description.md
@@ -3,6 +3,7 @@
 If you have several Generic Export Indicators Service integration instances, make sure to use **different listening ports** to separate the outbound feeds.
 Note: After a successful configuration of an instance, if the 'test button' is clicked again, it may result in a failure due to an incorrect assumption that the port is already in use. Nevertheless, it is important to highlight that despite this issue, the instance will continue to function correctly.
 
+The Generic Export Indicators Service is a long-running integration. For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>
 
 <~XSIAM>
 ### Access the Generic Export Indicators Service by Instance Name (HTTPS)

diff --git a/Packs/EDL/ReleaseNotes/3_3_7.md b/Packs/EDL/ReleaseNotes/3_3_7.md
@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### Generic Export Indicators Service
+
+Improved configuration documentation and instructions.
diff --git a/Packs/EDL/pack_metadata.json b/Packs/EDL/pack_metadata.json
@@ -2,7 +2,7 @@
     "name": "Generic Export Indicators Service",
     "description": "Use this pack to generate a list based on your Threat Intel Library, and export it to ANY other product in your network, such as your firewall, agent or SIEM. This pack is built for ongoing distribution of indicators from XSOAR to other products in the network, by creating an endpoint with a list of indicators that can be pulled by external vendors.",
     "support": "xsoar",
-    "currentVersion": "3.3.6",
+    "currentVersion": "3.3.7",
     "author": "Cortex XSOAR",
     "url": "https://www.paloaltonetworks.com/cortex",
     "email": "",

diff --git a/Packs/GenericWebhook/Integrations/GenericWebhook/GenericWebhook_description.md b/Packs/GenericWebhook/Integrations/GenericWebhook/GenericWebhook_description.md
@@ -6,7 +6,7 @@ We recommend that you use Cortex XSOAR server rerouting when using this integrat
 </~XSOAR_ON_PREM>
 
 
-**Note**: The **Listen Port** needs to be available, which means it has to be unique for each integration instance. It cannot be used by other long-running integrations.                                      
+**Note**: The **Listen Port** needs to be available, which means it has to be unique for each integration instance. It cannot be used by other long-running integrations.For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>
 
 #### Security
 - We recommend using the authorization header, as described below, to validate the requests sent from your app. If you do not use this header it might result in incident creation from unexpected requests.

diff --git a/Packs/GenericWebhook/ReleaseNotes/1_1_5.md b/Packs/GenericWebhook/ReleaseNotes/1_1_5.md
@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### Generic Webhook
+
+Improved configuration documentation and instructions.
diff --git a/Packs/GenericWebhook/pack_metadata.json b/Packs/GenericWebhook/pack_metadata.json
@@ -2,7 +2,7 @@
     "name": "Generic Webhook",
     "description": "The Generic Webhook integration is used to create incidents on event triggers.",
     "support": "xsoar",
-    "currentVersion": "1.1.4",
+    "currentVersion": "1.1.5",
     "author": "Cortex XSOAR",
     "url": "https://www.paloaltonetworks.com/cortex",
     "email": "",

diff --git a/...tGraphTeams/Integrations/MicrosoftGraphTeams/MicrosoftGraphTeams_description.md b/...tGraphTeams/Integrations/MicrosoftGraphTeams/MicrosoftGraphTeams_description.md
@@ -26,4 +26,6 @@ Chat.ReadWrite - Delegated
 ChatMember.Read - Delegated 
 ChatMember.ReadWrite - Delegated 
 ChatMessage.Read - Delegated 
-ChatMessage.Send - Delegated
+ChatMessage.Send - Delegated
+
+This is a long-running integration. For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>
diff --git a/Packs/MicrosoftGraphTeams/ReleaseNotes/1_1_10.md b/Packs/MicrosoftGraphTeams/ReleaseNotes/1_1_10.md
@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### O365 Teams (Using Graph API)
+
+Improved configuration documentation and instructions.
diff --git a/Packs/MicrosoftGraphTeams/pack_metadata.json b/Packs/MicrosoftGraphTeams/pack_metadata.json
@@ -2,7 +2,7 @@
     "name": "MicrosoftGraphTeams",
     "description": "O365 Teams (Using Graph API) gives you authorized access to a user’s Teams enabling you to facilitate communication through teams as that user, or read conversations and/or messages of that user.",
     "support": "community",
-    "currentVersion": "1.1.9",
+    "currentVersion": "1.1.10",
     "author": "Joachim Bockland",
     "url": "",
     "email": "",

diff --git a/Packs/PingCastle/Integrations/PingCastle/PingCastle_description.md b/Packs/PingCastle/Integrations/PingCastle/PingCastle_description.md
@@ -7,6 +7,8 @@ When PingCastle is run, it generates an XML report. One of the options PingCastl
 - The parameter `longRunningPort` specifies the unique port on which the integration will listen. This port must not be used by any other instances or integrations.
 - The parameter `API Key` is the Key __PingCastle__ must use when sending a report. This key must be generated by the user - a random string of at least 20 characters is recommended.
 
+For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>
+
 
 ### Running PingCastle
 #### This section explains how to run PingCastle in such a way that it sends its report to the integration.  

diff --git a/Packs/PingCastle/ReleaseNotes/1_0_11.md b/Packs/PingCastle/ReleaseNotes/1_0_11.md
@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### PingCastle
+
+Improved configuration documentation and instructions.
diff --git a/Packs/PingCastle/pack_metadata.json b/Packs/PingCastle/pack_metadata.json
@@ -2,7 +2,7 @@
     "name": "PingCastle",
     "description": "Active directory is quickly becoming a critical failure point in any big sized company, as it is both complex and costly to secure. PingCastle is a Windows-based utility to audit the risk level of your AD infrastructure and check for vulnerable practices. The Integrations and Playbooks in this allows you to listen for PingCastle reports, create an incident based on that report, upload the XML Report to the War Room as a file, and so on",
     "support": "community",
-    "currentVersion": "1.0.10",
+    "currentVersion": "1.0.11",
     "author": "soarxperts",
     "url": "",
     "email": "",

diff --git a/Packs/PublishList/Integrations/PublishList/PublishList_description.md b/Packs/PublishList/Integrations/PublishList/PublishList_description.md
@@ -8,7 +8,8 @@ For Cortex XSOAR 6.x only:
 1. Navigate to  **Settings > About > Troubleshooting**.
 2. In the **Server Configuration** section, verify that the value for the ***instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add *instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>* and set the value to *true*. See the following [reference article](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
 
-**Note**: The ***Listen Port*** needs to be available, which means it has to be unique for each integration instance. It cannot be used by other long-running integrations.
+**Note**: The ***Listen Port*** needs to be available, which means it has to be unique for each integration instance. It cannot be used by other long-running integrations. For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>
+
 
 #### Security
 - We recommend using the authorization header, as described below, to validate the requests sent from your app. If you do not use this header it might result in information leakage from unpermitted requests.

diff --git a/Packs/PublishList/ReleaseNotes/1_1_5.md b/Packs/PublishList/ReleaseNotes/1_1_5.md
@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### Publish List
+
+Improved configuration documentation and instructions.
diff --git a/Packs/PublishList/pack_metadata.json b/Packs/PublishList/pack_metadata.json
@@ -2,7 +2,7 @@
     "name": "Publish List",
     "description": "The Publish List integration is used to publish XSOAR lists for external consumption.",
     "support": "community",
-    "currentVersion": "1.1.4",
+    "currentVersion": "1.1.5",
     "author": "landonc",
     "url": "",
     "email": "",

diff --git a/Packs/SimpleAPIProxy/Integrations/SimpleAPIProxy/SimpleAPIProxy_description.md b/Packs/SimpleAPIProxy/Integrations/SimpleAPIProxy/SimpleAPIProxy_description.md
@@ -8,7 +8,7 @@ For Cortex XSOAR 6.x only:
 1. Navigate to  **Settings > About > Troubleshooting**.
 2. In the **Server Configuration** section, verify that the value for the ***instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add *instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>* and set the value to *true*. See the following [reference article](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
 
-**Note**: The ***Listen Port*** needs to be available, which means it has to be unique for each integration instance. It cannot be used by other long-running integrations.
+**Note**: The ***Listen Port*** needs to be available, which means it has to be unique for each integration instance. It cannot be used by other long-running integrations. For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>
 
 #### Security
 - We recommend using the authorization header, as described below, to validate the requests sent from your app. If you do not use this header it might result in information leakage from unpermitted requests.

diff --git a/Packs/SimpleAPIProxy/ReleaseNotes/1_0_5.md b/Packs/SimpleAPIProxy/ReleaseNotes/1_0_5.md
@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### Simple API Proxy
+
+Improved configuration documentation and instructions. 
diff --git a/Packs/SimpleAPIProxy/pack_metadata.json b/Packs/SimpleAPIProxy/pack_metadata.json
@@ -2,7 +2,7 @@
     "name": "Simple API Proxy",
     "description": "This pack provides a simple API proxy to restrict privileges or minimize the amount of credentials issued at the API.",
     "support": "community",
-    "currentVersion": "1.0.4",
+    "currentVersion": "1.0.5",
     "author": "thimanshu474",
     "url": "",
     "email": "",

diff --git a/Packs/Syslog/Integrations/Syslogv2/Syslogv2_description.md b/Packs/Syslog/Integrations/Syslogv2/Syslogv2_description.md
@@ -6,3 +6,5 @@
 - **Important**: Only TCP/TLS is supported. UDP is not supported.
 - **Important**: Supported log formats: RFC3164, RFC5424, RFC6587 (with RFC3164 or RFC5424)
 - The integration **does not support** encrypted private keys.
+
+For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>
diff --git a/Packs/Syslog/ReleaseNotes/2_0_21.md b/Packs/Syslog/ReleaseNotes/2_0_21.md
@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### Syslog v2
+
+Improved configuration documentation and instructions.
diff --git a/Packs/Syslog/pack_metadata.json b/Packs/Syslog/pack_metadata.json
@@ -2,7 +2,7 @@
     "name": "Syslog",
     "description": "Use the Syslog pack to send messages and mirror incident War Room entries to Syslog, or listen to incoming Syslog messages.",
     "support": "xsoar",
-    "currentVersion": "2.0.20",
+    "currentVersion": "2.0.21",
     "author": "Cortex XSOAR",
     "url": "https://www.paloaltonetworks.com/cortex",
     "email": "",

diff --git a/Packs/TAXIIServer/Integrations/TAXII2Server/TAXII2Server_description.md b/Packs/TAXIIServer/Integrations/TAXII2Server/TAXII2Server_description.md
@@ -1,7 +1,7 @@
 ## TAXII2 Service Integration
 
 This integration provides TAXII2 Services for system indicators (Outbound feed).
-You can choose to use TAXII v2.0 or TAXII v2.1.
+You can choose to use TAXII v2.0 or TAXII v2.1. TAXII2 Service Integration is a long-running integration. For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>
 
 ## Configure Collections
 Each TAXII collection in the integration is represented by a Cortex XSOAR indicator query.

diff --git a/Packs/TAXIIServer/Integrations/TAXIIServer/TAXIIServer_description.md b/Packs/TAXIIServer/Integrations/TAXIIServer/TAXIIServer_description.md
@@ -1,6 +1,7 @@
 ## TAXII Service Integration
 
-This integration provides TAXII Services for system indicators (Outbound feed).
+This integration provides TAXII Services for system indicators (Outbound feed). TAXII Service Integration is a long-running integration. For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>
+
 
 ## Configure Collections
 Each TAXII collection in the integration is represented by a Cortex XSOAR indicator query.

diff --git a/Packs/TAXIIServer/ReleaseNotes/2_1_1.md b/Packs/TAXIIServer/ReleaseNotes/2_1_1.md
@@ -0,0 +1,10 @@
+
+#### Integrations
+
+##### TAXII Server
+
+Improved configuration documentation and instructions.
+##### TAXII2 Server
+
+Improved configuration documentation and instructions.
+
diff --git a/Packs/TAXIIServer/pack_metadata.json b/Packs/TAXIIServer/pack_metadata.json
@@ -2,7 +2,7 @@
     "name": "TAXII Server",
     "description": "This pack provides TAXII Services for system indicators (Outbound feed).",
     "support": "xsoar",
-    "currentVersion": "2.1.0",
+    "currentVersion": "2.1.1",
     "author": "Cortex XSOAR",
     "url": "https://www.paloaltonetworks.com/cortex",
     "email": "",

diff --git a/...bFileRepository/Integrations/WebFileRepository/WebFileRepository_description.md b/...bFileRepository/Integrations/WebFileRepository/WebFileRepository_description.md
@@ -18,3 +18,4 @@ To access the File Management UI by instance name, make sure ***Instance.execute
    - (For Cortex XSOAR 8 or Cortex XSIAM) `https://ext-<tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>`
    -  (In Multi Tenant environments) `https://<cortex-xsoar-address>/acc_<account name>/instance/execute/<instance_name>/`
 
+For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>
diff --git a/Packs/WebFileRepository/ReleaseNotes/1_0_28.md b/Packs/WebFileRepository/ReleaseNotes/1_0_28.md
@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### Web File Repository
+
+Improved configuration documentation and instructions.
diff --git a/Packs/WebFileRepository/pack_metadata.json b/Packs/WebFileRepository/pack_metadata.json
@@ -2,7 +2,7 @@
     "name": "Web File Repository",
     "description": "Simple web server with a file uploading console to store small files.\n",
     "support": "community",
-    "currentVersion": "1.0.27",
+    "currentVersion": "1.0.28",
     "author": "Masahiko Inoue",
     "url": "",
     "email": "",
Original file line number	Diff line number	Diff line change
Expand Up		@@ -18,3 +18,4 @@ To access the File Management UI by instance name, make sure ***Instance.execute
		- (For Cortex XSOAR 8 or Cortex XSIAM) `https://ext-<tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>`
		- (In Multi Tenant environments) `https://<cortex-xsoar-address>/acc_<account name>/instance/execute/<instance_name>/`

		For more information about long-running integrations, check out the <~XSIAM>[Forward requests to long-running integrations](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations) article.</~XSIAM> <~XSOAR_SAAS>Forward Requests to Long-Running Integrations article: [Cortex XSOAR 8 Cloud](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Forward-Requests-to-Long-Running-Integrations) or [Cortex XSOAR 8 On-prem](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.7/Cortex-XSOAR-On-prem-Documentation/Integration-commands-in-the-CLI) documentation.</~XSOAR_SAAS>