AndyG
-
Posts
106 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Enhancement Requests
Posts posted by AndyG
-
-
Hi @Estie, We have fixed the following defect. Please look out for it in an upcoming Service Manager application release.
"PM00178848 - Inconsistent behaviour of summary & description text in intelligent capture"
-
2
-
-
Hi @Ashley, please see my answer on another thread. Hopefully it can help you too.
-
@Ketan.lakhani, Please check your service configuration. If your "Resolution Category Level" is set to a level with no categories below it then there will be no categories to choose on resolution. If you have also configured resolution categories to be required (i.e. turned this app setting on: "servicemanager.request.closureCategory.default.required"), then you will not be able to resolve requests for the service. There was some inconsistent behaviour that enabled you to resolve a request without a resolution category when you had resolution category configured as required. This inconsistencey was fixed in the last release of Service Manager.
-
Hi @Jeremy, This has been fixed and released (some time ago now). Just wanted to let you know, in case you hadn't realised.
-
1
-
-
Hi @Jeremy You might find this extension for the chrome browser useful..
https://chrome.google.com/webstore/detail/gofullpage-full-page-scre/fdpohaocaechififmbbbbbknoalclacl-
1
-
-
Stefania's question answered here:
-
1
-
-
I think these are the 1s you are looking for...
GREEN: guest.com.hornbill.servicemanager.portals.servicePortal.home.requestView.details.resolve.working
RED: guest.com.hornbill.servicemanager.portals.servicePortal.home.requestView.details.resolve.broken -
Hi @Berto2002, You don't have to reload the page; You just need to click on the "Resolve" tab header to select it; This will then show the buttons.
You are correct though; This can be improved so that the tab is automatically selected. Look out for the following defect fix in an upcoming release of the Service Manager application.
PM00176350 - Request details action tab is not automatically shown in employee portal
Cheers,
Andy
-
1
-
-
@Luke, There is also a Service Manager application setting that you might find useful:
app.request.update.site.showAllSites
If you turn this on, you will get the full list of sites in request details.
-
Hi @Luke,
The sites are filtered based on the company that is set against the request. The company set against the request will most likely be one that is associated with the customer at the point the request is logged. This will not necessarily be the customers "home organisation".
If you frequently want to choose a different site. i.e. A site that is not associated to the company set against the request; You could use the following "Hornbill Automation" in your business process or via a custom button/autotask:
Service Manager > Entity > Requests > Update Request > Site
-
This issue is no longer reproducible since asset history improvements (CH00165714) were released to LIVE in Service Manager Build 2789 on 12th January 2023.
-
1
-
-
Hi @Hayley Gladden, We decided to patch the above defect so you don't have to wait for the next SM release; Merry Christmas. Your instance should now have been updated although you may need to clear your browser cache. Please let us know if this is working for you.
Many thanks,
Andy
-
Hi @Hayley Gladden, The following defect has been resolved:
PM00175335 - Pagination not working in intelligent capture forms.
This is likely to be included in the first Service Manager release of 2023. -
Hi @Teresa Ward
The "Raise Request" button in the Live Chat application will use the IC listed under the following Service Manager application setting:
app.itsm.progressiveCapture.newRequest
-
Hi @Salma Sarwar, I am trying to work out why your expectation is not being realised.
If you finish the capture with "No" in dropdown1, then any value that might have been selected in dropdown2 will not be shown in the details of the resulting call. This has been fixed for a while now.
I wonder if you are looking at some old calls that were logged before the fix ? These will not have changed unfortunately.
Or perhaps you are selecting "yes" and "upgrade", then "no", then "yes" again without finishing the capture? In this case, dropdown2 will have retained "upgrade". Is it at this point you expect the value to have been cleared ? -
Hi @QEHNick, Where exactly are you finding the hyperlink? Could you possibly provide a screen grab please ?
-
Hi @QEHNick, The following defect has been resolved and is likely to be included in the Service Manager release after next.
- PM00174095 - Error when updating "Draft" bulletin
-
Hi @Berto2002,
The following defect has been resolved and is likely to be included in the Service Manager release after next.
- PM00173985 - Notices don't always refresh when updated on Requests
-
1
-
Hi @CraigP,
To hide unanswered questions, you can search for hideUnansweredQuestions within Service Manager Application Settings and turn on the related settings.
-
Hi @Gavin James - SDDC, To hide the whole service, set it's Portfolio Status value to "Retired".
-
Hi @Gavin James - SDDC, If you "retire" a catalog item (through service portfolio) then it will not be avaialble for new requests, but existing open requests should still be visible. Would that meet your requirement ?
-
Hi @Smurfy,
If you look in the Service Manager Configuration under Customize > Translations, the key you are looking for is: user.view.pcapture.assets.placeholder
-
2
-
-
Hi @Ann,
The following changes to the "Linked Entities" > "Linked requests" section on asset details will be included in the next release of the Service Manager application:
- Excluded cancelled and closed requests by default
- Added toggle to allow closed/cancelled requests to be included if switched to on
- List now sorted by log date, so the most recently logged requests are at the top
-
Hi @Adrian Simpkins, This will be fixed in the next release of the Service Manager Application.
-
1
-
Amendments to Layout of Priority / Urgency in Incidents
in Service Manager
Posted
Hi @JAquino, I'm not able to see any issues with setting and amending priorities on requests. Is there any more information you are able to give us? Is it happening for all requests? And all users? Is it only for requests using a particular service or workflow ?