Out Of Box Actions

Release version: Australia

Updated March 12, 2026

3 minutes to read

Summarize

Summarized using AI

Summary of Out Of Box Actions

The Out of Box Actions provide essential functionalities for deployment, tagging, retrieval, and post-provisioning operations through Flow Designer as Integration Hub Sub-flows. These actions streamline various processes involved in the deployment and management of cloud resources, particularly focusing on Linux and Windows VM deployments in ServiceNow.

Show full answer Show less

Key Features

Deploy ACC: Deploys the Agent Client Collector (ACC) as a post-provisioning step for Linux VMs. Requires configuration of an ACC Listener on a MID Server to establish connectivity.
CCG Scan: Initiates a CCG policy scan on deployed stack items. If violations occur, the stack enters a follow-up state until resolved.
Tagging Action: Updates key values in the Configuration Management Database (CMDB) for catalog items, including StackName and BusinessService. Only fields with values are recorded.
Retrieve Windows Password: Sends the provisioned Windows VM password to the requester via email, obtained from AWS using a specified SSH key file.
Email URL for Azure Applications: Emails the end point URL of deployed Microsoft Azure applications to the requester after deployment.
Retrieve Azure Function App Host Name: Retrieves and emails the host name of deployed Microsoft Azure Function Apps to the requester.

Key Outcomes

By utilizing these Out of Box Actions, ServiceNow customers can effectively manage post-provisioning tasks, ensure compliance through policy scanning, automate email notifications for critical information, and maintain accurate records in the CMDB. This enhances operational efficiency and improves overall resource management in cloud environments.

The Out of the Box Actions comprise OOB deployment, tagging, retrieving and post-provisioning operations. All these actions are based on Flow Designer and implemented as Integration Hub Sub-flows.


Actions	Flow Designer Sub-flow Name	Description
Deploy ACC-* in post provisioning	CSC Content- Post Provisioning- Deploy ACC in Stack VMs	ACC (agent client collector) is deployed through a Flow Designer action. This is called as post-provision step for the Linux basic VM deployment catalog item. Pre-requisites: ACC Listener must be configured in any MID Server. This will generate a mid web server endpoint and a MID Server API Key. In the post provisioning operation parameters of the Basic Linux VM catalog, these two parameters – web server end point (typically in format wss://<IP_Address>:3389/ws/events) and MID Server API Keys, need to be set. Out of the box, these parameters have empty values. Note: If the generated WS endpoint URL returns the private IP of the MID Server, then that private IP needs to be replaced with public IP of the MID Server VM for the internet-based connectivity. There should be connectivity over SSH port from the MID Server to the provisioned VM. In case of any failure in installing agent on the provisioned VM, a task is created, and stack is set to a 'follow-up required' state and automatically turns active, once all the follow-on tasks are closed.
CCG Scan in post provisioning	CSC Content- Create CCG Policy Scan on Stack Items	CCG Scan with the default OOB Policy Set in CCG is called with the simple windows and Linux deployment. When a CCG scan fails owing to violation, the stack is set to a follow-up needed state. The operator must ensure that the violation is remediated and close the violation task. Once all the follow-on tasks are closed, the stack automatically turns to active state and can be used by requester.
Tagging Action	CSC Content- Post Provisioning- Update Key Values in CMDB	All catalog items have a tagging action run as post-provision step. This action only updates the key-value entries in CMDB, not in cloud. The standard tags updated are StackName, Application, CostCenter and BusinessService. Fields with empty values will not be saved as key-value records.
Retrieve Windows Password	CSC Content- Post Provisioning- Retrieve Windows Password	All windows catalogs have a retrieve password action, which emails the Administrator, the password of the provisioned windows VM to the requester. The password is obtained from AWS after the deployment is complete using a ssh key ('pem') file to decrypt the password. Follow these pre-requisite steps to set up this pem file on the Terraform Linux server: Ensure that the SSH Private Key credential to the VM with Terraform CLI installed, is associated with the credential alias named 'TFO Server Credential Alias'. This alias is already created with installation of CSC Content pack. This alias is used to SSH into the terraform server to get the windows password from output variable. Ensure that in the Catalog’s Provision variable set, the variable called 'keypath' has the default value set to the path of the management key (the key which can decrypt the password) on the terraform VM. Ensure that the requester has set up the email Note: For custom catalogs, this operation is available for use only, with Terraform Opensource- Linux based catalog items.
Email URL For Microsoft Azure Scalable Web Server Application	CSC Content- Email URL For Microsoft Azure Scalable Web Server Application	This action is added as a post provision operation in 'CSC Microsoft Azure Linux with Scalable Web Server' catalog item, which emails the deployed application's end point URL to the requester. The URL is obtained from Microsoft Azure after the deployment is complete. Ensure the requester has set up the email.
Retrieve Microsoft Azure Function App Host name	CSC Content- Post Provisioning- Retrieve Microsoft Azure Function App Host name	This action is added as a post provision operation in 'CSC Microsoft Azure Function App catalog item which retrieves the deployed function app's host name to the requester.