Jump to content

Martyn Houghton

Hornbill Users
  • Posts

    4,028
  • Joined

  • Last visited

  • Days Won

    86

Posts posted by Martyn Houghton

  1. The Request List displayed within the Service Portfolio > Service screen only displays request of Incident, Service and Change Requests types. It is not showing Problem, Known Error nor Releases, so appears to be hard coded to the original three Request Types. I have checked I have access to the Full Access role for the request types and request existing under the service (which I can see in the normal Request List).

    Can this be looked as please.

    Cheers

    Martyn

    image.png.8318716ff24547a5778859d07971fdd4.png

    image.png.1cceedf92fdca5c0ed81face6562a130.png

    image.thumb.png.db109e7155a0e383a93181f2e3844978.png

  2. Linked to @Jeremy post below, can we raise an enhancement request for additional custom fields types using the same common selection of data type and lengths as available at the request entity.

    Subsequently the Get Request Information > Service Details node would need to be updated to support these, plus the propose enhancement to allow updating of Service Custom Fields from the request as well.

    Cheers

    Martyn

     

     

  3. Can we raise a enhancement request to have the ability to set the Status and Sub-Status of a Routing Rule - Update Request action. 

    We are trying to build Enterprise Service Management (ESM) interactions for both logging and updating existing requests based on incoming emails. Having the ability to communicate intelligently with the request using status/sub status changes would wold make the ESM integration much more flexible and deeper.

    Cheers

    Martyn

     

     

  4. @Hayley Gladden

    On 5/9/2022 at 7:30 PM, Hayley Gladden said:

    We also have the following setting turned off, which is being ignored and emails are still moving to the deleted items folder. Is this a known issue? Has anyone else experienced it?

    image.png.55ea3cc050bf398304eececda98635a1.png

    Try turning this on. It sounds wrong, but it should mean the other setting where you have told it to move it to Inbox will then be activated.

    Cheers

    Martyn

  5. @Steve G

    I trying to import Known Errors into to Service Manager but hitting an issue with how I import their published status. Looking in the database there is a separate table h_itsm_published_requests which sits over Problem and Known Errors. As part of the import I need to be able to pass a flag to indicate whether the request being imported should be published.

    Is there anyway to currently do this as I am on a tight timetable to migrate the data from a system which has to be decommissioned very soon.

    Cheers

    Martyn

  6. Currently there are only two Known Error specific BPM options to Get Information and Update Known Error, so appear to be very limited in terms of automation.


    image.png.6ecdedea8b5500599dd54829c34cac3f.png

     

    We are trying to automate the creation and publishing of Known Errors on the portals but in order to do this we need the ability to undertake the same actions as the Publish Action in the user app, i.e. set the 'Include Workaround' and update the Status between Draft and Published.

    image.png.4e87e798706ec9f8a8cb72313e7b6dda.png

    Cheers

    Martyn

     

     

×
×
  • Create New...