Playbook | Integration with DevOps - MVP2

Playbook's integration with DevOps via the External Task Connector has been further enhanced. Click here to learn about the previous release.

  1. Source Types and States are automatically detected from the DevOps dataset and default types are selected by Playbook. The Types and States determine what will be pulled from DevOps into Playbook and can be modified as desired.
    Jan 2023 - DevOps MVP2 - 1
  2. Playbook can see five levels deep in the DevOps Area Path structure, so a specific Area Path to pull from can be selected.
    Jan 2023 - DevOps MVP2 - Area Path - 2
  3. Tags defined in DevOps are also visible and can be selected to determine what is pulled into Playbook.
  4. When you click Next, the Field Mapping from DevOps to Playbook is displayed. Typically, no changes are necessary.
    Jan 2023 - DevOps MVP2 - Field Mapping - 3
  5. When you click Next again, the External Tasks and the default Status filters are displayed. The Status filters can be modified as desired.
    Jan 2023 - DevOps MVP2 - External Tasks - 4
    Jan 2023 - DevOps MVP2 - External Tasks - Status Filter - 5
  6. When you click Pull Now, the list of external tasks is populated with the data found in the DevOps dataset.
    Jan 2023 - DevOps MVP2 - External Tasks - Pull Now - 6
  7. When you click Ok, the external tasks are created in Playbook. External tasks are green and are displayed with a unique icon so they are readily identified.
    Jan 2023 - DevOps MVP2 - External Tasks in Playbook - 7
  8. Want to learn more? Contact a Customer Success Engineer today!