IDEA - Work Notes and Comments input not visible
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
I have found out an issue on an instance I manage. After upgrading to Australia version, on the Idea form (idea table) on PROD environment I cannot input any work note or additional comments, since they are not visible. when trying to create a new idea, the notes are visible in their section, but read only.(Check attachments) I have a user on my instance with idea_admin who can work freely. I have full administrator access along with security_admin role. No ACL has been created or updated way long before the upgrade was completed (the start of this month). Only this idea_admin user can input notes in PROD.
Weird thing is, in the DEV environment, this issue is not present. Everybody with access to view the Idea records can freely operate and input work notes and comments.
Both environments are on:
-Build date: 09-29-2026_2211
-Build tag: glide-australia-02-11-2026__patch6mw40-09-25-2026
Things I have checked:
- Client scripts, nothing to block the fields
- UI policies, nothing to block the fields
- Data policies, nothing to block the fields
- Form Design, fields are visible there
- ACLs, nothing to block the fields
- Business Rules, nothing to block the fields
- Script Includes, nothing to block the fields
Nothing in the instance on PROD or DEV suggest anything should restrict the access to idea_admin only.
To mention, no differences between PROD and DEV on anything regarding the whole Idea application.
I have repaired the com.snc.innovation_management plugin, still nothing.
In list view, I can apparently add comments from the column.
Any help is highly appreciated.
Kind regards,
Daniel C.
#idea #upgrade #australia #notes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Please update us when you have the cause. It can always help someone else.
Normally you could use the access analyzer to 'pretend' to add a role to someone, but in this case that wouldn't have mattered, since it already states that you should have access. An additional role wouldn't matter.
However, looking at licensing implications on PROD, you could easily have added the role to yourself, test and remove it again. That doesn't mess up licensing at all. Even if ServiceNow would check at that exact moment, when they come with their overview, the role is already gone, so it's not going to have any impact.