Portal Shows Incorrect Value for Requestor and Requested For
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2023 09:17 AM
Hi guys!
We are using the OOB widget SC Order Status however, the value for Requestor and Requested For in portal is incorrect.
In this screenshot, the REQUESTOR is System Administrator since he's the one who created the ticket. REQUESTED FOR is Abel Tutor.
But in Service Portal, it shows Abel Tutor as REQUESTOR while the REQUESTED FOR is System Administrator which is incorrect. Can someone teach me how to fix this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2023 01:24 PM
Hi @Byron Plant ,
How are your variables configured on the 'Azure Database' catalog item? If the 'Requested for' input is not a 'requested for' variable type, then the OOB widget will overwrite the Requested for with the current logged in user.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2023 12:06 AM
Hi @matthew somers thank you so much for responding.
Just want to note that since we are using the OOB widget, we did not changed anything at all. It says here that this widget is READ ONLY and cannot be edited so we will have to clone this widget so we can edit make it editable.
For the "Requested for" field, we are using a variable set and the type is a Reference because we need to reference this field to our sys_user table.
Our main issue is the REQUESTED FOR field as it is the one that's very visible. We want to make sure that the Requested For field gets the correct value. Can you help me fix the Requested For field?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2023 06:10 AM
@Byron Plant- instead of reference as the variable type in your variable set, try the requested for variable type. You can still have reference to users within the sys_user table with requested for type. The widget will then take the requested for value that is set within the catalog item to populate in the REQ instead of defaulting to the current logged in user. As you can see below, it is automatically referencing sys_user and you can enter any sort of reference qualifier, if needed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2023 06:57 AM
Hi @matthew somers,
I changed the variable type of "Requested For" field from reference to requested For. I also deactivated the Business rule that I found:
But when I did that, the Requested For went missing in the portal view