Skip to content

Commit dadad84

Browse files
committed
Minor updates
1 parent 1c70d02 commit dadad84

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/platform-services/automation-service/automation-service-playbooks.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -291,11 +291,11 @@ To test a node:
291291
1. Click the **Edit** button at the bottom of the screen to make a draft of the playbook.
292292
1. Click the **Edit** button on a node.
293293
1. Click the **Test Node** toggle at the top of the **Edit Node** dialog. An **Input** panel appears to the left, and an **Output** panel appears to the right. <br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-test-node-toggle.png')} alt="Playbook Test Node toggle" style={{border:'1px solid gray'}} width="800"/>
294-
1. In the **Input** panel, enter variables to test the node. Ensure that you enter valid variables for the kind of inputs you need to test. In the following example that uses input from insights, we provide an insight ID.
295-
1. Click **SAVE & RUN TEST**. Results of the test appear in the **Output** panel.<br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-test-node-variables.png')} alt="Playbook Test Node variables" style={{border:'1px solid gray'}} width="800"/>
294+
1. In the **Input** panel, enter variables to test the node. Ensure that you enter valid variables for the kind of inputs you need to test. In the following example that uses input from insights, we provide an insight ID.<br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-test-node-variables.png')} alt="Playbook Test Node variables" style={{border:'1px solid gray'}} width="800"/>
295+
1. Click **SAVE & RUN TEST**. Results of the test appear in the **Output** panel.
296296
6. The **Output** panel shows results of the test run. Examine the results and take any action needed to troubleshoot node operation:
297297
* Click the information button <img src={useBaseUrl('img/platform-services/automation-service/playbook-test-node-info-icon.png')} alt="Playbook Test Node JSON info button" style={{border:'1px solid gray'}} width="30"/> to see information on the test run:<br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-test-node-info-button.png')} alt="Playbook Test Node info" style={{border:'1px solid gray'}} width="300"/>
298-
* Click the **JSON details** button <img src={useBaseUrl('img/platform-services/automation-service/playbook-test-node-json-details-icon.png')} alt="Playbook Test Node JSON details button" style={{border:'1px solid gray'}} width="30"/> to see the JSON output. The button toggles to a **Table details** button <img src={useBaseUrl('img/platform-services/automation-service/playbook-test-node-table-details-icon.png')} alt="Playbook Test Node table details button" style={{border:'1px solid gray'}} width="30"/> so you can return to the table view. <br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-test-node-json-details.png')} alt="Playbook Test Node JSON details" style={{border:'1px solid gray'}} width="300"/>
298+
* Click the **JSON details** button <img src={useBaseUrl('img/platform-services/automation-service/playbook-test-node-json-details-icon.png')} alt="Playbook Test Node JSON details button" style={{border:'1px solid gray'}} width="30"/> to see the JSON output:<br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-test-node-json-details.png')} alt="Playbook Test Node JSON details" style={{border:'1px solid gray'}} width="300"/>
299299
7. Continue testing the node and making changes as needed in the node's configuration. When done, click **Save**.
300300
8. Test each node in your playbook that has the **Test Node** button (action, condition, user choice, and task). In each node, enter variables in the **Input** panel and examine the results in the **Output** panel to ensure the node works correctly.
301301

-996 Bytes
Loading

0 commit comments

Comments
 (0)