Skip to content

Latest commit

 

History

History
43 lines (26 loc) · 2.16 KB

quest3.md

File metadata and controls

43 lines (26 loc) · 2.16 KB
Raw

Quest 3 - Debutant's journey

< Quest 2 - 🏠Home - Quest 4 >

🌟🌟🌟 🕒 15 mins

Introduction

In this section we will tailor the playbook to our needs and adjust the properties of the adaptive card to include the SAP transaction code.

The path

  1. Check the incident details again on Sentinel. Which property contains the transaction code?

  2. Use below snippet to add it to flow step Post incident as adaptive card and wait for a response on the Logic App. Scroll till you reach the JSON entity of "titel":"Tactics" and put your change as new JSON entity as third FactSet on the adaptive card.

{
    "title": "Transaction Code",
    "value": "@{body('Parse_Incident_Custom_Details')?['TransactionCode'][0]}"
}

Note - Remember, that you need to add the third entity with a ",". Compare how the entity "title":"Tactics" is shown.

Either trigger the Logic App again from the Incident like you did before or choose a past run from the Logic App history and click resubmit. That is a nice practice during integration development to avoid waiting for new incidents during design time.

Your updated card on Teams should look like this:

Connection Details

Feel free to make further adjustments to the card in Microsoft Teams to your liking. The adaptive card designer might be a great asset to help with that. Choose the Actionable Message flavour for Outlook and verify selected host app. See more useful references on the start page.

Warning - Microsoft Teams currently supports schema target version 1.4 but the latest adaptive card release is on 1.6 in preview.

Where to next?

< Quest 2 - 🏠Home - Quest 4 >

🔝