Versions Compared

Old Version 2

changes.mady.by.user Peter Atthem

Saved on

compared with

New Version Current

changes.mady.by.user Sales Rixter AB

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This guide describes how to receive a SOAP message in iHub and process that message as a issue.

Step 1.

  • Click on Inbound Integrations Incoming Webhooks on the left side menu.

...

  • Image Added

  • Click New Rule
    The rule will map what action to to run

    Image RemovedImage Added


  • Name the rule anything related to the incoming system, in our example SOAP incoming message

  • For now leave the Rule HTTP response as “No Response”

  • We will add a THEN action to this rule at step 3.

  • Click Save

Step 2

  • Click on Outbound Integrations
    Since we are going to create an issue in our Jira instance we will use an outbound integration that performs this action.

  • Click New button

  • Add a Name, e.g. SOAP to Issue

  • Select Action

  • Select a parent if you want to place this in a Group (e.g a folder), our folder is called SOAP.
    Note the Group needs to be created before the action is created.

  • Select Template; Jira Core Server

  • Select Request Template; Create Issue
    This is to get a template for an issue creation

  • Click Create

  • Now select an Authentication, for sending to Jira select a Basic auth. Our is called KG and was created before this tutorial. See Basic Authentication

  • In the body we paste in this code.
    Use tripple mustache to remove any HTML character on line 7, 8 and 10 when using the variables.
    Variables will be defined in Step 4.

    Code Block
    {
    "fields": {
       "project":
       {
          "id": "12000"
       },
       "summary": "{{{soap.example:Summary}}}",
       "description": "{{{soap.example:Description}}}",
       "priority": {
            "name": "{{{soap.example:Priority}}}"
        },
       "issuetype": {
          "id": "10004"
       }
   }
}

  • Click Save

Step 3. Modify the

...

Incoming Webhook rule

  • Click the Inbound Webhook Rules again

  • Click three dots, then Edit on the Rule created in Step 1.

  • Select the SOAP to Issue action in the THEN box

  • Click Save.
    Note that IF condition can be added to make sure the right action is triggered. In this tutorial we only have one, but as your integration grows you can add more rules and filter by URL, DATA or User.


Tip

This concludes the inbound incoming webhook part of receiving a SOAP message an passing it into an action that will create the issue.

Next up is the steps on how to parse the SOAP message to become variables used in the Action body as mustache variables. eg. {{summary}}, {{description}} and {{priority}}

...

Testing can be done from any tool or SOAP system. We use iHub to test this integration.

  • Create an Outbound Integration

  • Name it SOAP test incoming

  • Select a Basic authentication

  • Add this to the Body

    Code Block
    languagexml
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:example="http://www.example.com/soap-api">
    <soap:Header/>
    <soap:Body>
        <example:CreateIssue>
            <example:Summary>Fix critical bug</example:Summary>
            <example:Description>This is a critical bug that needs immediate attention.</example:Description>
            <example:Priority>High</example:Priority>
        </example:CreateIssue>
    </soap:Body>
</soap:Envelope>

  • Press Test button

  • Result should be a new Issue created with the summary “Fix critical bug”, description “This is a critical bug that needs immediate attention.” and Priority “High”


...