- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2016 12:19 PM
Hi Friends,
We have a requirement, where we need to give access to a user to create change module only. He should not have access to update the change request.
Without giving ITIL role to that user , how can we achieve this one.
Please provide your inputs.
Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2016 12:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2016 01:22 PM
I'm no expert by any means on licensing, but I have to think you are entering some shady territory by allowing a non-rolled user access to create changes any other way than a record producer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2016 04:24 PM
Yes, you are definitely skirting the rules. We use call as a gateway to real tasks, but it is a process user that opens the record (ie, help desk) not the end user.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2017 09:09 PM
Hi mallen_nspi - Sorry to dredge up an older thread, but are you saying you have new_call set up with a Record Producer which is published to ESS users in your Service Catalog? Would be interested to know if other orgs are using New Call this way.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2017 07:14 AM
From my experience, new_call is used lightly, which is a shame, because it is so handy. Most of the time, when a user calls in, it takes about 5 minutes or so to get to the source of the issue. Call records allow you to capture the initial information without committing to a record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-30-2017 08:51 PM
Yeah, it's a reasonable use case, and is similar to "interaction" in HP Service Manager. What I was getting at was creating a record producer for self service in the catalogue (rather than expecting a user to know the difference between an incident and a request etc.