No readable comment field in portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2019 03:54 AM
Hi,
I have added a widget instance to my portal, to show watched RITs, so that a non ITIL user can view and comment on any requests where they have been added to the watch list.
This has worked fine, and the watcher can see the RITs. But when they click on the RIT, it comes up with the message No readable comment field.
I have updated the ACLs sc_req_item.comments for read and write to 'or watch list is dynamic me' but this does not appear to have resolved the issue.
Any other places I may need to allow the watcher to ensure they can see and add comments
Thanks
Collette
- Labels:
-
Service Catalog

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2019 05:26 AM
Hi,
You may want to go to the task table level and look at that comment field.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2019 01:29 AM
Hi Allen,
Thanks for the reply.
I looked at ACL's for task, but unfortunately you cannot add the watcher at task level.
Regards
Collette

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2019 08:06 PM
Please try using:
Watch List "CONTAINS" javascript:gs.getUserID();
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2020 01:50 AM
Hi Allen,
I have tried the suggested, for both read and write ACLs, but still get the same issue.
This is my condition on the ACL -
Operation read (also same condition on write)
Name requested item[sc_req_item]
additional comments
Description: Allow read for comments in sc_req_item, if the ACL condition (request.requested_forDYNAMIC90d1921e5f510100a9ad2572f2b477fe^ORrequest.opened_byDYNAMIC90d1921e5f510100a9ad2572f2b477fe^ORrequest.watch_listLIKEjavascript:gs.getUserID()^EQ) evaluates to true.
I also have an ACL for the requested item [sc_req_item]
operation read
no field specified
description: - Allow read for records in sc_req_item, if the ACL condition (watch_listDYNAMIC90d1921e5f510100a9ad2572f2b477fe^EQ) evaluates to true.
Criteria
Not sure if I need to change to javascript:gs.getUserID() on this one as well?
To give some further information, I do also remember when we went to New York we had an issue with ITIL users not being able to add comments to RITs as they were not the requester or the requested for, so I had to create a new ACL with role ITIL for Requested Item - additional comments - read, (no conditions) so wonder if this is overwriting the ones I have set up above?
There is also an ACL - admin created (I believe as part of the upgrade) for requested item - additional comments - write (no conditions) for roles ITIL and Catalog. Again could this be the cause.
Sorry for so many details, but I don't generally amend the ACL's but was hoping there would be a simple fix
Thanks for your help
Collette