Jump to content

Giuseppe Iannacone

Hornbill Users
  • Posts

    481
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by Giuseppe Iannacone

  1. @Gerry would you be so kind to clarify my request or address it to the right person?

    On 15/04/2024 at 11:41, Giuseppe Iannacone said:

    Can you confirm is not yet possible to update a request against its type, as far as I know you can only move from a service to another but only within the same request type.
    It often happens that a user selects a catalog item that is an incident but for us is instead a service request.
    For example the user as the password expired and enter an "error issue" catalog item which is opened as an incident while it is a service request from an ITIL perspective.
    Any idea?
    Also is there a way to open a generic request and then apply the request type after... for example after a response period a generic request taken in charge by an analyst became an incident or a service request.
    If I'm not wrong this capability is available on the Enterprise version of the platform or am I wrong?
    thanks

    image.png.80c045ad7efd8b03976502cff4b1a646.png

     

  2. I was wondering which might be the right API to call to simulate a customer update, the idea is we have a service managed by a team, the customer is for real an automated user, which collects from an external system an error log and open a ticket or update a ticket whit the relevant data from the external log.
    all is fin except that I'm unable to post an update on the timeline as customer, the idea is to get the onhold request automatically off the on-hold status (matching the substatus rule)
    image.png.0531d35926298b8ceffe2c4e4af8d7d2.png

  3. Can you confirm is not yet possible to update a request against its type, as far as I know you can only move from a service to another but only within the same request type.
    It often happens that a user selects a catalog item that is an incident but for us is instead a service request.
    For example the user as the password expired and enter an "error issue" catalog item which is opened as an incident while it is a service request from an ITIL perspective.
    Any idea?
    Also is there a way to open a generic request and then apply the request type after... for example after a response period a generic request taken in charge by an analyst became an incident or a service request.
    If I'm not wrong this capability is available on the Enterprise version of the platform or am I wrong?
    thanks

    image.png.80c045ad7efd8b03976502cff4b1a646.png

  4. @Steve Giller I've got which is the issue, I supposed the role I've assigned to the user was good enough to interact with the requests, but supposing is enough. In fact I've tried to do the same action via UI and got the answer, not enough authorization.
    Can you please help me to understand how can I address the right role (just the minimum required to create/assign/interact with the requests IN/SR), I want this user to be able to manage all the requests we have, If I'm not wrong the user has to be part of the team that supports the service and the incident/service request user role or am I wrong?

  5. @Steve G @Keith Stevenson@SamS
    in postman the sintax ":yourinstanceid" means you are defining a path variable (as far as I know), which of course I've defined to be our instance value. By the way, now I'm aware I'm using the wrong endpoint (Thank you @Steve G) so I suppose this will fix our issue.
    Also on my last check I was aware xml was the officially supported and that you were in the middle of moving against the JSON payload, so Thank @SamS I'll give a look to the reference you have posted, and I'll get back with my findings!
    Thanks all for the quick and precise advice.

×
×
  • Create New...