RITM record not loading on Agent workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2019 01:02 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2019 05:00 AM
Hi Jen,
I think this was a known issue in Madrid, it should be fixed in New York:
Just tried in my personal instance (New York), I can load any RITM records without any problem, please upgrade your instance to the new New York release and try again:
If I have answered your question, please mark my response as correct and/or helpful so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.
Thank you
Cheers
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2020 07:04 AM
Hi
The screenshot that you have attached, i can RITM in that. Are you able to access RITM table in workspace?
I am trying to use AWA for sc_req_item table. But i am not receiving any ritm request in the inbox.
However in Work item(awa_work_item) table, i can see the ritm number was routed to right queue.
I have configured ritm just like incident.For incidents it's working as expected.
Can we receive RITM requests as well in the inbox?
Any leads would be highly appreciated.
TIA!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2020 01:34 AM
Hi there,
We are facing the same issue in a New York instance, while it doesn't happen in another one (same patch level). Can please someone recommend how to debug and find the difference?
I already compared the views and switched certain scripts on and off, but it's like searching for a needle in a haystack if I can't simply see which script or configuration is causing the lag. All I can see is that if I open the RITM from a "My Work" list (which is using the Task form), it is getting loaded properly. So it should be something related to the RITM table directly.
Best regards,
Valen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2020 02:44 AM
PS: I caught the error below with GraphQL debug. Does anyone have a well-trained eye and can see where to look at next?