CloudRadial supports PowerShell script generation through a few modules (Problem Reports, Service Requests, and Assessments). In these ticket-capable modules, you can use the Script functionality to generate a PowerShell script for your team that can expedite ticket resolution.
Examples of real use cases include scripts to provision licenses to users, scripts to restart service (like printer spoolers), and even scripts to clear caches.
Note: CloudRadial will never execute the scripts directly. The scripts written in CloudRadial will be sent over to the connected PSA as attachments where they must be then executed by a technician.
Accessing the Script Pane
To access the script pane:
- Navigate to one of the three area that support scripting in tickets
- Problem Reports
- Service Requests
- Begin the ticket creation process as normal
- Select the Script tab
An Example of How to Script
Using a combination of question field IDs and the Script tab under a service item, you can build out a custom script that gets attached to the ticket when submitted.
To see a simple example of this:
- Create a new service item in the Support > Request Service area
- Fill in the required fields
- Under the Question section, select a question to expand it fully
- Select Show more options... at the bottom of the specific question
- In the expanded section, locate the field for Script / JSON Field ID
- Add the word Subject to the JSON / Field ID value
- Click on the Script tab at the top of the editing page
- Enter the following script:
$val = "@Subject"
- Select Submit to finalize the ticket creation process
As the ticket is submitted, a PowerShell script attachment will be added with the content of the script.
By creating a token (denoted by the @ sign), the result is that any value entered by the ticket submitter will replace the placeholder value. Remember the two following rules to script token creation:
- The Script / JSON Field ID value in the form can be anything. Do not use the @ sign there.
- The Script itself in the ticket must match the value from step 1 with the @ sign in front
Article is closed for comments.