Jump to content

Giuseppe Iannacone

Hornbill Users
  • Posts

    481
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by Giuseppe Iannacone

  1. On 10/11/2017 at 12:17 AM, James Ainsworth said:

    At the moment, a Manager can view the activities for any of their managed staff.  A manager is set on the user profile for each user.  To view the tasks for one of your managed staff you can select the User option from this menu option on the Activity View and then select the user.

    Thank you @James Ainsworth you are referring to the user profile management

    image.png

    or the team's manager?

    image.png

     

     

  2. 1 hour ago, James Ainsworth said:

    You can also use the Linked Requests option to create a new linked request under the appropriate service.  This will copy over some of the original data and maintain a link to the original request if this needs to be referenced again. 

    James

     

    i was think to this approach too, but the user will at this point receive a new notification for a new request and moreover

    if request 1 is raised against service A, then i raise request 2 linked to 1 and raised against service B, how can i make it happens that once the request 2 is resolved/closed the request 1 is resolved/closed at the same time?

  3. 1 hour ago, Victor said:

    @Giuseppe Iannacone

    It can't. You need to close the request raised against A and raise a new one against B.

    Maybe the initial diagnosis can be done differently to ensure the request is raised against correct service?

    I supposed this would be your reply, but hey we are humans... there's no backfall plan for this situation? for example the service desk manager might be able?(it's clear to me it's not possible at the moment, but maybe in the future ? :) )

  4. is there a way to manage a request opened against a wrong service? let's say i have the service A and a service B. the request was initially assumed to be of competence of the service A. after the diagnosis you discover that the request was for service B. both service have different team support.

    how can the request be moved from A to B?

  5. We have a mailbox configured for receiving customer request. Currently we have received 3 error messages. reporting Hornbill ESP Message Processing Error

    here is the content of the error message and attached you can find the files for the debugging:

    Quote
    We have detected an error during the message decoding process for the attached inbound mail message. This could be due to the MIME decoding problem in Hornbill's software, a corrupt message from the message originator or a general communications problem. You will find the original raw RFC822 formatted message as well as other useful files attached to this message in order to help you identify the message originator and aid in debugging the problem.

    Please ask the originator of the message to send it to you again. If the problem persists and you are happy that this message or its attachments do not contain confidential personal or commercial information, please contact Hornbill support or your Hornbill partner if you have a valid support contract or post the problem on Hornbill's community support forum (https://forums.hornbill.com/) in order that we can investigate this problem further.

    Thank You.

    Hornbill Development Team

    Message tracking ID: imap4-Service Desk-4609c4a686029cd6

    The error encountered was:

    Illegal byte sequence
    Quote
    We have detected an error during the message decoding process for the attached inbound mail message. This could be due to the MIME decoding problem in Hornbill's software, a corrupt message from the message originator or a general communications problem. You will find the original raw RFC822 formatted message as well as other useful files attached to this message in order to help you identify the message originator and aid in debugging the problem.

    Please ask the originator of the message to send it to you again. If the problem persists and you are happy that this message or its attachments do not contain confidential personal or commercial information, please contact Hornbill support or your Hornbill partner if you have a valid support contract or post the problem on Hornbill's community support forum (https://forums.hornbill.com/) in order that we can investigate this problem further.

    Thank You.

    Hornbill Development Team

    Message tracking ID: imap4-Service Desk-c31383addaee7339

    The error encountered was:

    Failed to add message to the inbound queue. Operation[mail::addMessageToQueue] The XMLXC request message contains invalid characters for the UTF-8 encoding scheme

    MessageRFC822__.txt

    MessageRFC822_.txt

    MessageRFC822.txt

  6. @Martyn Houghton

    Thank you, this clarifies better the SLA Topic.

    It's still not answered from my point of view the question 2 and 3

    On 10/25/2017 at 11:35 PM, Giuseppe Iannacone said:

    2. when the Service Manager uses the "ServiceDeskDefaultCalendar" and the "FeedbackCalendar"

    3. assuming that we well create additional working time calendar for each time zone we have in our enviroment (see the picture above), how this will be used by the Service Manager from a general point of view and how the 2 stages closure will use those calendars and in which relationship with the Teams' Site or /Customers' Site (if any relationship exist)

    Thank you!

  7. Hi Everybody,

    We have a global Service Desk Team, working in different time zones. At the current stage we have not yet deployed any service with an SLA, but soon we will. I understood that the SLA might be linked to a specific Working Time Calendars as described in another post (https://forums.hornbill.com/topic/9868-work-time-calendars/?tab=comments#comment-46216). We are also using the 2 stage closure which i understood is in some way using a Calendar; let me also say that potentially our teams and customers will work under this calendar:

    image.png.92191284c9c620b9748dac5b7f239f78.png

    so my questions are:

    1. in which way the Service Manager uses the Working Time Calendars and which relationships we have between Teams' Site/Customer's Site

    2. when the Service Manager uses the "ServiceDeskDefaultCalendar" and the "FeedbackCalendar"

    3. assuming that we well create additional working time calendar for each time zone we have in our enviroment (see the picture above), how this will be used by the Service Manager from a general point of view and how the 2 stages closure will use those calendars and in which relationship with the Teams' Site or /Customers' Site (if any relationship exist)

    Thank you!

  8. ok, while i was thinking at my post, I also found the answer by my self... i was looking at the wrong role.

    it is enough to create a duplicate role for "incident management user" and than I was able to remove the "close incidents" right as i was able to do with the Service Requests.

    I hope this helps other folks on the forum.

    Thank you.

    • Thanks 1
  9. @Victor Thank you for the reply. I can't use the lock action because we are using the 2 stage closure process, and I want people be able to resolve request and if necessary reopen manually incident and service request for example on a customer notification replies.

    Why there isn't a specific role like "Close Service Request" for service requests? Is there a way to create a set of rights similar to "Close Service Requests" for Incidents (Close Incidents for example)?

    image.thumb.png.00d64f96604c7b9edc4e541dab752855.png

    here fore example a custom role without the right "Close Service Requests"

    image.thumb.png.33ee2e9700fcc076f292b7515c94832f.png

  10. Hi everybody,

    we are using the 2 stages closure for all our requests (Incidents and Service Request), is there a way to avoid that a technician can manually close a request? I mean how can i remove the "Close" button once the incident has been resolved and waiting for the expire period or user's reply?

    image.png.e05dcb09d32540f226e8db59a2e0fa2d.png

×
×
  • Create New...