Giuseppe Iannacone
-
Posts
481 -
Joined
-
Last visited
-
Days Won
7
Content Type
Profiles
Forums
Enhancement Requests
Posts posted by Giuseppe Iannacone
-
-
1 minute ago, Daniel Dekel said:
@Giuseppe Iannacone, I suspect it will affect all customers that use the Date Picker. We have the fix, are testing it now and push to Live once we have a confirmation it works as expected.
Daniel.
Thank you, I will be waiting for your reply
-
16 minutes ago, Daniel Dekel said:
Hello @Giuseppe Iannacone,
We are now working on a solution, should not take long.
Will let you know when is solved.
Regards,
Daniel.
Thank you Daniel, so I expect it is affacting other customers too?
-
is there someone from Hornbill? this is a blocking issue for us
-
3 minutes ago, DeadMeatGF said:
The date selector has new Date Range fields - is it caused by these having invalid values in?
I don't know if leaving them empty breaks stuff - it didn't, but there have been updates over the weekend!
we don't use the range selection
-
in one of our progressive capture the date selector is no more available we receive a denied access, can you tell us why?
-
+1 also here
-
we have updated our Service Manager app and now we are receiving different error:
-
we have more or less the same challeges described by @Lyonel, while I do not agree on moving the choice to the customer there might be an escape using a "Global issue" tag that may change the behaviour of the timeline, hiding everything but the update provided by Service Desk agent with the approach "customer" "team" or "public.
marking a ticket as a "global issue" the information had with the customer might remain private between SD and the customer, but the connection will receive a reasonable feedback on the issue status.
-
3 hours ago, Ehsan said:
Thank you for bringing this to our attention. This has now been fixed and will be available as a Service Manager App update (build 1203 or higher) in the week commencing 16th April.
Thanks,
Ehsan
thank you for the quick reply, I appreciate it.
-
3 minutes ago, Victor said:
@Giuseppe Iannacone can you post a screenshot of the routing rule configuration for updates, please?
-
it seems like there is an issue with email routing rules. an email has been applied to a closed case even if this option is disabled (as far as i understand)
-
thank you for the reply, we were not considering this aspects. it sounds reasonable. Maybe a "Publish" (like the problem has) option may be usefull to let the service desk decide what to share with interested and impacted people. what do you think about?
-
Is there a way to let the impacted/interested user to see the request status in service portal?
as you can see i'm an interested customer but i cannot see the status of the request from the portal
-
thank you for the reply. I believe there's a different story here. let me explain better our scenario:
Team A, assigned to request 1
Team B, a member is trying to apply a new email to request 1, error received.
Team A, a member is trying to apply to request 1 the same new email, no issue
both Team are supporting the service, of course.
-
sometime we receive this error while applying an email to a request
currently the request is assigned to a specific team.
it seems like only the member of the team can apply the email. supposing we have different team working on the same service, how can avoid the error if a different team wants just to apply new emal to a request assigned to a differente team?
-
thank you for the suggestion, we will give it a try.
-
thank you for the reply. I understand with your point of view. In our environment this make sense to us because we are opening the service portal, let's say gradually. in the first phase we will give our user the portal only for having the "status update" on their request. That's because we have not yet had time to develop all the services and item (progressive capture and BPM) to let them open the request.
So our idea is having a default setting in which we can decide to have a landing page on the All Requests until the services will also be available for opening requests.
Thank you!
-
1 minute ago, Steven Boardman said:
No problem happy to help
In terms of the other request types (Problems, KE's and Releases) these don't have a Customer linked to them in the same way as Inc, SR's and Changes, so they would not currently be visible on the portal.
They request types do have a Raised By but this would be the analyst and these are deemed to be more internally facing request types which might result from an Incident or change a customer has raised but would be requests for the internal teams to manage which could result in the Change being deployed or the Incident the customer reported being fixed as a child of the internal Problem or KE.
Steve
Thank you @Steven Boardman i was supposing this was the meaning for Problems, KE's and Releaseas by design, but i wasn't 100% sure.
-
is it possible to let the customer see as default view like this (focus on All My Requests instead of All My Services):
-
thank you for the quick reply, I appreciate it.
now i've enabled the setting and as expected is working.
What about the problem, know errors and release visibility into the Service Portal? (we have not yet implemented this processess in our environment, this is for the future implementation)
-
I'm not understanding why the change requests raised for customers are not visible into the Service portal, assuming the customer is a subscriber of the service
-
4 hours ago, James Ainsworth said:
Are your updates being processed automatically using the Routing Rules? Are you wanting the request to go back to an open status if there is an automatic email update? The challenge might be identifying if the email update is a response to say that there is still an issue, or a Thank you email to say it is fixed.
@James Ainsworth currently we are not using a routing rule because it might reopen a request just because of the "Thank you " email. So we'd better sponsor the Service Portal for update (it will take time until all the customer will be trained) but just in case how can this be achieved?
4 hours ago, James Ainsworth said:For the routing rules, you are able to set the destination folder if the email is not processed. I'm guessing that yours is currently set to a folder called "unsuccessful update''. Or are you wanting to have multiple destinations for the Target Folder Failure based on different conditions?
you are correct, but i would like to have multiple destination based on conditions
-
scerario: we have a mailbox that collects the custumer's request raised via email. all our current BPM are using the 2 stages closure.
1. the email is a brand new case; current action: manually open a request
2. the email is referring to an open case; current action: the system is correctly updating the timeline (regex_match on the subject); nice to have: automatic status change if in resolved status
3. the email is referring to a closed case; current action: the system moves the email to a folder called "unsuccessful update" (regex_match on the subject); nice to have: leave the mail in inbox if in closed status or open a new request linked to the first case
thank you
-
@James Ainsworth thank you for the update
Date selector not available
in Service Manager
Posted
just my curiosity it was related to last servicemanager update?