Alberto M Posted September 11, 2020 Share Posted September 11, 2020 Hi. We have been implementing automation so requests are raised automatically from external applications. For this, we created specific catalog items where requests should only be raised by this automated processes and not by customers, nor by analysts. So, besides setting the access to the catalog item only to service desk, to avoid customers to raise requests (and have access to these requests as well), we would like to avoid service desk to raise requests manually for these catalog items - and this limitation is only regarding the raise action; not to limit service desk to access these requests. Is there any way to set this? (I can't find it and I believe not) Thanks, Alberto Link to comment Share on other sites More sharing options...
Deen Posted September 14, 2020 Share Posted September 14, 2020 @Alberto MI'm not sure this can be done as the only options I can see are Portals/ServiceDesk/Both. I suppose a fourth option is required here. If I can think of a way around this i'll let you know. Link to comment Share on other sites More sharing options...
Steve Giller Posted September 15, 2020 Share Posted September 15, 2020 @Alberto M It would be a bit ugly, but a ProCap that branches on Portal Type or Source to a message to the User asking them not to use this CI might guide the User away. I haven't tested this, but if the View is set to Portal Only, and no Customers subscribe to it, I would expect that it would not show to anyone on the Customer Portal, and it wouldn't be visible to the Service Desk. Link to comment Share on other sites More sharing options...
Alberto M Posted September 21, 2020 Author Share Posted September 21, 2020 @Steve Giller, yes, that "ugly" part of it is the one we would like to avoid. Regarding the visibility, this should be something working at catalog item, and I believe the subscription is defined at service level, right? (we don't use services subscription, so it's something I've never explored and tested) Cheers Link to comment Share on other sites More sharing options...
Steve Giller Posted September 21, 2020 Share Posted September 21, 2020 2 hours ago, Alberto M said: Regarding the visibility, this should be something working at catalog item, and I believe the subscription is defined at service level, right? Any CI can exclude groups, so if you add at least one group at the Service level, then exclude it at the CI level this should have the same effect. Again, I've not tested this as I don't have a Customer Portal on my test Instance currently, but it should work in theory until a better option is available. Link to comment Share on other sites More sharing options...
Alberto M Posted September 21, 2020 Author Share Posted September 21, 2020 Thanks, @Steve Giller, I'll give this a try. 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