Request Offering - History - Unathorized Access

Karen_Bruster1

Hello,
I have been having a continuing issue with 1 RO, and I was just wondering if anyone had seen this before.
When a customer tries to use this particular RO then they go to save it, it gives unauthorized access popup and will not save. I have recreated it several times, as well as the template. Today I looked in the History section of the RO and found this

Brad_McKenna

Have you validated the user(s) have access to the template?

This has caught us a few times were we create a new template and RO, then realize we did not provide the user (their user role) access to the template.

Karen_Bruster1

@Brad_McKenna Yes and also validated that they have access using an SQL script.
I found that some SR tickets are being added to the History information by SCSM my service account. I wanted to upload a screen capture but there is no way to do it to this Question.

Brian_Wiest

Does the RO have any configuration items attached in the template, or selected via the RO?

Karen_Bruster1

@Brian_Wiest No there are not configuration items in either the template or the RO.
The History shows items being added by the SCSM Service Account -

Relationship Changes:
Add/Remove             Relationship Class                                          Item

Add                           Work Item relates to Request Offering     SR261309: Additional IT Equipment (AITE)

There are several entries on multiple days with this information but different SR#s

Brian_Wiest

Yea those come after the fact of the workflow making your relationships for reporting how many times a specific RO is requested.

What I was referring to/looking for is on the initial submit do you see something like this.

Typically when users have access to the RO/SO etc but do not have rights to edit configuration items you get the failure.

So when it fails what shows in the portal\logs\console.log

john_doyle

@Karen_Bruster1  another possibility is that there is a relationship on one of the activities which the end users do not have the right to create. For instance, you may have a custom relationship to a user or an activity. If that relationship is bound in the template, then the end users need permission to write that relationship.

If you have an SMA runbook activity in the template, for example, and that runbook has the author defined, then end users would need permission to create the runbook activity to author relationship. End users should have implicit permission to create any relationship which relates to the work item being created. You just need to watch for relationships being created between related objects. Mostly they work, but if you have any custom relationships you may have to give the users implicit permission to create the relationship. In the example of the runbook activity, you could simply remove the author entry from the template. If the relationship is not defined on the template or mapped in the request offering, it will not be created, so you just need to check those relationships which are defined.

Karen_Bruster1

@Brian_Wiest No there are not related configuration items. @john_doyle there are no associated Runbooks to this RO its strait up activities..

Erik_Dixon

I am also getting this on an RO.. Seems to happen upon final submission.. Not on all RO's though.