---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Global activities

# Global activities {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Global activities are Orchestration activities created in the global scope.  
Any activities you create in the global scope are listed in the Global category in the Packs and Custom tabs of the Workflow Editor. Abbildung : 1. Global activities

## Test Server Alive activity {#ariaid-title2}

The Test Server Alive activity determines if a target system is alive by its response
to a particular protocol.
This activity replaces an activity by the same name available in releases prior to Istanbul. If you have a workflow created in a previous version that uses the deprecated activity, your workflow will
continue to work normally after upgrading to Istanbul. However, all new workflows must use the custom version of this activity. This activity was built with the [Probe activity template](https://servicenow-prod.fluidtopics.net/W40ab_Y6gXIVHGzj0St6ZQ#t_CreateAProbeActivity "Create an activity that runs a probe on the target host that is configured to return specific information.."), which gives workflow administrators the ability to store input and output variables in the [databus](https://servicenow-prod.fluidtopics.net/8OYaonyVEUHUlQE7wAXD_w#t_ReuseDataInTheActivityDesigner "The Data tab in the Workflow Editor lists all custom activities used in the current workflow that produce data and displays that data for reuse in other custom activities.").{#test-server-alive-activity__p_DeprecationNote}

### Input variables

{#test-server-alive-activity__table_avv_xnr_3q__entry__2}

| Variable | Description |
|-|-|
| port_probes | A comma separated list of protocols to use to check for signs of activity on the target machine (example: <var class="keyword varname">wmi,wins,https,ssh,http,https,snmp,dns</var>) |
| hostname | Hostname or IP address of the target system to check. |
[Tabelle : 1. Test Server Alive input variables]

{#test-server-alive-activity__table_avv_xnr_3q}

### Output variables

{#test-server-alive-activity__table_jql_r2k_pw__entry__2}

| Variable | Description |
|-|-|
| alive | Code that indicates whether or not the server is alive. If any value but '1' is returned, the server is not alive. |
[Tabelle : 2. Test Server Alive output variables]

{#test-server-alive-activity__table_jql_r2k_pw}

### Conditions

{#test-server-alive-activity__table_nj4_v52_3w__entry__2}

| Condition | Description |
|-|-|
| Success | Activity determined that the device is running. |
| Failure | Activity failed to determine if the target device is running. Failure could be caused by a missing protocol or a device that is not accessible. |
[Tabelle : 3. Test Server Alive conditions]

{#test-server-alive-activity__table_nj4_v52_3w}