Also to add on , in workflow designer , I have added Run as a 'current user' , but still in ITSM logs, it's taking 'Demo' as a loggin user.
Demo doesn't exists in ITSM People profile, it's only in User form. Hence when it executes filter WOI:WIC:CreateWorkOrder_040_SetReqByPersonId_WhenNull
It returns null value.
You shouldn't need to hard code the first name/last name. Here's a screenshot from my own system (which simply creates a WO and closes it when the status changes in ITSM) Is this what you're trying to achieve ? I left the default "Run as Administrator" option blank.
Thanks & Regards,
For Run As, at service broker workflow level, there are two options , run as a 'logged in user' and run as a 'Administrator'. I tried both of these, but always the logged in user in the ITSM is 'Demo' . This global 'Run as' can be inherited to the component level.
However, customer support or you helped us to track down the exact problem . And issue is resolved. Thanks for the support.
Root case : the customization adjusted
For on behalf of users, we are getting below error 'ERROR (46422): ; You are not authorized to act on behalf of XXXXX'.. I don't think this could be OOB issue. But still, in case any one come across the solution. Please do inform us .
1 of 1 people found this helpful
you need to create the OBO rule in Remedy (ITSM) to allow someone to act as someone else in the front end (MyIT/SB).
Hi Sanket - this is exactly what's happening in our environment. You mentioned "Root case: the customization adjusted". Can you explain or give more detail on how you fixed?