Assess Button Visible on New Problem Record After Australia Upgrade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
After upgrading to the Australia release, the Assess button is appearing on a brand-new/unsaved Problem record. Before the upgrade, it was hidden until the record met the required conditions.
We've compared the UI Action (Declarative Action) between environments and found no differences.
Has anyone seen this behavior after the Australia upgrade or know of any related platform/UI Action changes?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
ahoy @KartikM49574975,
Australia might have brought new roles for ITSM granularity - e.g. Problem admin etc.
What you can maybe do is to check the roles, has it displayed for admins as well or for any other specific role?
✂-----Cutting-out-the---✦AI-noise✦---All-replies-written-and-vouched-for-by-GlideFather---
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I tested the same scenario in three instances — Zurich, Australia, and Brazil — and what you’re seeing is expected behaviour across all instances.
As soon as a problem is created & Save, the Assess button is displayed by default. This is required because it is the only way for the problem to move to the next state.
So, the behaviour is working as expected. You may not have noticed it earlier, but this is the standard behaviour across the instances.
No Access button is there.
please repair the problem management plugin once.
Regards
Dr Atul G. - Learn N Grow Together ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
******************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you @KartikM49574975 for sharing it as I was able to reproduce this issue in my PDI Service Operations Workspace (as it is non-reproducible in Native UI).
Try renaming every Assess UI Action in your PDI and you will find out that this Assess button on new Problem record in SOW remains the same. Therefore, my recommendation is to create HI Case to ServiceNow so that they can share it with their engineering of it is already know to them then they can share fix with you.
My PDI:
Hope that helps!
