Missing resolve conflict for a sys_ux_macroponent skipped record
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-16-2022 09:23 AM
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-16-2022 01:15 PM
At UC Berkeley, when we encounter these types of records we usually:
- search the community to see if anyone else has encountered it
- open a ServiceNow Support ticket to ask: is it benign or actionable
- Mark the skip/revert upgrade record as 'reviewed'
Thanks,
Terri
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-17-2022 09:54 AM
Opened a community topic and SN support ticket. Will see of we get similar or same information. Thanks.