Steve Giller Posted June 20, 2017 Share Posted June 20, 2017 Is there a way to force the selection of a catalog item? We have the Raise New ... option forcing the selection of a Service, but we need to enforce a Catalog Item so that a suitable PC/BP are triggered. Link to comment Share on other sites More sharing options...
Hornbill Staff DR Posted June 20, 2017 Share Posted June 20, 2017 Hi Steve,  the application setting servicemanager.progressiveCapture.servicedetails.catalogRequired should do the trick. Dan Link to comment Share on other sites More sharing options...
Steve Giller Posted June 20, 2017 Author Share Posted June 20, 2017 I thought there would be a setting somewhere! Thanks. Link to comment Share on other sites More sharing options...
Alberto M Posted October 13, 2021 Share Posted October 13, 2021 @Steve Giller, we have this setting "ON" and apparently it does nothing. Anyway, we don't have catalog items for change requests, but we'd like to force the catalog item to be selected for Incidents and Service Requests. Is there some way to have this set? @Stephane LE TANTER, FYI Link to comment Share on other sites More sharing options...
Steve Giller Posted October 13, 2021 Author Share Posted October 13, 2021 @Alberto M Just to clarify - are you saying that it does nothing, or that it does nothing if you have a Service with no CIs? Also, where are you seeing this (lack of) behaviour? Is this in the Employee/Service/Analyst/Customer Portal? I have this set and if I select a Service only, I get this message and the Progressive Capture will not continue: When I select a CI the Capture will continue as expected. Link to comment Share on other sites More sharing options...
Alberto M Posted October 13, 2021 Share Posted October 13, 2021 @Steve Giller In this situation, on https://live.hornbill.com/........./request/new/incident , when we have a service that has no incident catalog items, it allows an analyst to raise an incident without catalog item selected by clicking in the "Next" button. This creates us a problem because we mainly assign teams to requests based on the selected catalog item. Link to comment Share on other sites More sharing options...
Alberto M Posted October 13, 2021 Share Posted October 13, 2021 @Steve Giller, however, limiting this will create us a problem to Change Requests, because we don't user catalog items in Change Requests. Link to comment Share on other sites More sharing options...
Steve Giller Posted October 13, 2021 Author Share Posted October 13, 2021 46 minutes ago, Alberto M said: Anyway, we don't have catalog items for change requests, but we'd like to force the catalog item to be selected for Incidents and Service Requests. I believe (although someone from Service Manager may correct me here) that the statement above explains why you're seeing that behaviour, which is kind of what you're saying in your last post. The easiest way to prevent this is not to have any Services which have no CIs for Incidents and Service Requests - even if there's only one CI it will force the selection. Link to comment Share on other sites More sharing options...
Alberto M Posted October 13, 2021 Share Posted October 13, 2021 @Steve Giller, ... or disable the service types that does't have catalog items? Link to comment Share on other sites More sharing options...
Steve Giller Posted October 13, 2021 Author Share Posted October 13, 2021 If you have no need for an (in the above example) Incident to be raised against the Service that should work fine. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now