CreateTicketJSON Mapping issue

[FormulaHack]

Hello everyone,

Im working on a EasyVista Connector ITSM For ticketing (CreateTicketJSON Specifically) and im facing a problem of mapping on the right attributes, here is an exemple of the easyvista attributes :

REQUEST_ID: Request ID, i've thought of mapping it on  ars_request.id or ticketID
CATALOG_CODE : (Exemple :V2VS11U) 
RFC_NUMBER: (Exemple :S2091018_004)
RECIPIENT_IDENTIFICATION : i've thought of beneficiary.employeeID
STATUS_ID : (Exemple :8 )
CATALOG_REQUEST_PATH : (Exemple :Demand of service/join, leave, move of employee/join/xoxo - Annonce of join of a new employee )
TITLE_ENG: (Exemple :xoxo-Annonce of join of a new employee)
SUBMIT_DATE_UT: i've thought of ars_request.REQUESTDATE

Anyone have an idea of the right attributes for the mapping please?

Best Regards

[rushikeshvartak]

• Requested By ${com.saviynt.ecm.identitywarehouse.domain.Users.get(task?.requestedBy).email}
• Request ID ${task.requestKey?.processinstanceid?.substring(task.requestKey?.processinstanceid?.indexOf('.') + 1, task.requestKey?.processinstanceid?.length())}
• employee id ${user.employeeid}
• request date ${task.requestKey?.requestDate}

[FormulaHack]

Hello rushikeshvartak, 

Thanks for the response, I've made some changes on the attributes to be send, now im using those one's :

Catalog_code(static), Urgency_ID(static), Severity_ID(static), Recipient_Identification(dynamic), requestor_mail(dynamic), Origin(static), Description(static) 

Im hardcoding them just to be sure that the request is sent succesfully, but its not the case here, im getting a error msg : Error in getting Ticket Number...response: {"type":"about:blank","title":"Internal Easyvista Error","status":590,"message":"An internal error occurred.\r\n Please try again later or contact the system administrator.","

Here's my code:

{

  "call":[

     {

        "name":"call1",

        "connection":"acctWriteAuth",

        "url":"https://xxx/api/v1/50004/requests",

        "httpMethod":"POST",

        "httpContentType":"application/json",

        "unsuccessResponses": {

          "message": "Failed"

        },

        "httpParams":"{\"Catalog_Code\":\"Test51\",\"Urgency_ID\": \"2\", \"Severity_ID\": \"2\", \"Recipient_Identification\": \"03000772\",\"requestor_mail\": \"tester@xxx.com\",\"Origin\":\"7\", \"Description\":\"this is a test\"}",

        "httpHeaders":{

           "Authorization":"${access_token}"

        },

        "statusCode":[

          200,

          201,

          204,

          205

          ]

     }

  ]

}

I've done the tests with postman and everything works, i will be very grateful if you can help me with this problem and the attributes to be mapped to Recipient_Identification, requestor_mail

Best regards

[rushikeshvartak]

Could you kindly provide a detailed snapshot of the information extracted from the logs, encompassing errors and other pertinent functionality details encountered during the execution of this process? Your assistance in furnishing this information would greatly aid in the analysis and resolution of any issues .



‼️‼️⚠️Do not upload any attachments that contain sensitive information, such as IP Addresses, URLs, Company/Employee Names, Email Addresses, etc.⚠️‼️‼️

[FormulaHack]

Here's the logs

[rushikeshvartak]

Share in text format

[FormulaHack]

Hello,

While investigating the problem, i think i know from where it comes, Saviynt requires a Ticketid Number, and im not giving it in my code, have you an idea on how to implement it?

[rushikeshvartak]

Refer https://forums.saviynt.com/t5/identity-governance/servicenow-as-ticketing-system-multiple-call-in-cr...

[NM]

@FormulaHack ID password provided in connection json are those valid?? 

[FormulaHack]

Hello NM,

Yes the connectionJSON is working fine