Kanbanize Integration

Last modified on 2022/05/28 10:50
Contents

About this integration

IntegrationIntroduction

You can integrate third-party systems with Service Manager in many ways. The method you select will depend on business requirements, architectural and security constraints as well as the characteristics specific to each third-party application or service.

This document describes an integration process that has already been implemented in a customer context. 

To find out more about this integration (e.g. scripts to be used), please do not hesitate to contact your EasyVista contact, or your service provider and integrator.

Integration Summary

Kanbanize is a SaaS Project Portfolio Management tool inspired by Toyota’s Kanban method. 

You can perform 2 types of integration between Product name - ev itsm.png and Kanbanize:

  • Carry out actions in Kanbanize from an Product name - ev itsm.png workflow or business rule. Open url.png See Integration Process no. 1.

         Example documentation icon EN.png  

    • Validation of a change in the SAP software, in a change management Product name - ev itsm.png workflow step, entails creating a new card in Kanbanize, used by the Design and Development division, containing the change request number in a Validated SAP Change Requests column from a SAP Development Follow-Up board.
  • Carry out actions in Product name - ev itsm.png using Kanbanize. Open url.png See Integration Process no. 2.

         Example documentation icon EN.png  

    • Creation of a new card in Kanbanize in a New training courses list from a New training catalog board used by the Human Resources department entails creating an Analyze new training service request within Product name - ev itsm.png with the description of the Kanbanize card.
    • Dragging a card in Kanbanize (card created from Product name - ev itsm.png through Integration Process no. 1), in the column DONE results in closure of the incident / request (service or change) corresponding in Product name - ev itsm.png (using the field rfc_number used as unique identifier).
Data Integration Flow (direction) Authentication Type Integration Connector Options

Product name - ev itsm - big.png

Down arrow.png

Logo - Kanbanize.png
  • Personal API Key for the Kanbanize REST API (EN)
  • Basic Authentication for the REST API Product name - ev itsm.png

Product name - ev itsm.png SaaS

Product name - ev itsm.png On-premise

Check icon.png

Check icon.png

SaaS Version of Third-Party Product

On-Premise Version of Third-Party Product

Check icon.png

N/A

Step-by-Step Integration Process

Documentation

Open url.png See the wiki

Open url.png See Kanbanize Documentation (EN)

Open url.png See The Rates


Requirements

  • You must have a Kanbanize subscription. Otherwise, you can begin by assessing Kanbanize free of charge.
  • You have Administrator access rights to Kanbanize.
  • You must have an account to access your platform Product name - ev itsm.png with a profile and sufficient access and editing rights to create or change a workflow, access the Administration menu and the menus you need, such as Operation and Transition for example.
  • To use names of employees in the Product name - ev itsm.png directory in Kanbanize, such as the name of the person in charge of a card (assignee), you must ensure that the value of the names of employees in Product name - ev itsm.png and of the names of users in Kanbanize is identical. Otherwise, the default value None is displayed in Kanbanize.
     

Before performing this integration, depending on your needs you must also:

1. Create one or more types in Kanbanize

          Open url.png see How to Manage Types? (EN)

     Example documentation icon EN.png  

  • Creating an EVSM Exchange Request type enables it to be assigned to a new card created in Kanbanize from Product name - ev itsm.png (by creating a new change request)
  • Other types: EVSM Service Request, EVSM Incident

          Prerequisites - Step 1 - Board Settings.png
         Prerequisites - Step 1 - Types creation.png

2. Create one or more Custom Field fields in Kanbanize

          Open url.png see How to Manage/Add Custom fields in the card? (EN)

     Example documentation icon EN.png  

  • Creating a Custom Field field called EVSM_RFC_number enables the change request number (RFC_Number) created in Product name - ev itsm.png to be stored and displayed in the card created in Kanbanize
  • Other types: EVSM_Recipient, EVSM_Requestor

Note: The Custom Field fields can be used in a Runtime Policy (EN). In this way, a Custom field field such as that created to store the number of the change request (RFC_number) can also be used to update incidents / requests (service, change) from Kanbanize.  Open url.png See Integration Process no. 2.

          Prerequisites - Step 2 - Custom Field.png

3. Add the new Custom field fields to the table concerned in Kanbanize

          Prerequisites - Step 3 - Custom Field Added.png

4. Create an API key through the My Account Panel (EN), useful for step 1 of Integration Process no. 1

          Prerequisites - Step 4 - Generate API Key.png

Process no. 1: ev|Service Manager to Kanbanize

 Process no. 1: Use a Kanbanize REST action in an Product name - ev itsm - big.png workflow or business rule to carry out actions in Kanbanize

Documentation

Open url.png see the wiki

Open url.png see Kanbanize Documentation (EN)

Step 1: Create a new service

Note: Kanbanize will soon be available as an integrated service (built-in (ev)) in Product name - ev itsm.png.

          Process 1 - Step 3 - Edit Rest Service.png

Step 2: Create a new connection to the Kanbanize service or use an existing connection

Note: The values of the name/value pair of the key to be used to log on to the Kanbanize service (to customize the header of the HTTP requests made to the Kanbanize API) are apikey and the value of the API Key generated through the My Account Panel (EN) respectively. Open url.png See Prerequisites > step 4.

          Process 1 - Step 2 - Edit Rest Connection.png

Step 3 : Create a new resource of the Kanbanize service according to your needs

Note: The resource will soon be added to Product name - ev itsm.png as a built-in resource (built-in (ev)).

     Example documentation icon EN.png  

  • You want to create a card in Kanbanize corresponding to a new change request created in Product name - ev itsm.png. 
  • In the Kanbanize card you want to display: the name of the requestor, the name of the recipient, the request number (rfc_number).
  • You want the recipient of the change request to be the manager of the Kanbanize card (assignee).

          Process 1 - Step 3 - Edit Rest Resource.png

Value of the field Content:

{"boardid":"11","title":"{rfc_number}","description":"{comment}","priority":"Average","assignee":"{assignee}","type":"EVSM Change Request","column":"Backlog","position":"0","EVSM_RFC_Number":"{rfc_number}","EVSM_Recipient":"{Recipient}","EVSM_Requestor":"{Requestor}"}

Step 4: Add and configure a REST action using the log on and resource created previously

          Process 1 - Step 4 - Edit step Workflow.png

Step 5: Verification and test

     Example documentation icon FR.png  

  • Creation of a change request in Product name - ev itsm.png
  • Creation of a corresponding card in Kanbanize with:
    • the EVSM Exchange Request type
    • the number of the request (rfc_number) as the title of the card
    • the comment (justification) as the description of the card
    • the names of the requestor and recipient and the name of the recipient as responsible for the card (assignee)

          Process 1 - Step 5 - Verification ev SM.png
         Process 1 - Step 5 - Verification Kanbanize.png

Process no. 2: Kanbanize to ev|Service Manager

 Process no. 2: Carry out actions in Product name - ev itsm - big.png from Kanbanize

Note: This process is currently on hold pending an improvement under development at Kanbanize to achieve the integration of Kanbanize with Product name - ev itsm.png.

Tags:
Powered by XWiki © EasyVista 2022