Notifications

113 views

Description

When users use the '@' Mention feature in the Activity Formatter the platform code does a short impersonation of the user 'mentioned'. This can generate extra login Event[sysevent] records. The suggested workaround is to ignore login events without a corresponding external.authentication.succeeded Event.

Steps to Reproduce

- login to any OOB NY instance with demo data
- sysevent.list and note your actual login Event (example screenshot attached: My actual login)
- go to any Incident and use the @ Mention in a worknote update, e.g @Beth Anglin Are you there? (example screenshot attached: Mention feature in INC)
- Back to sysevent, check out how many extra login Events were created (example screenshot attached: All the extra login events created by Mention)
(screenshots done on an employee instance that no one else was using at the time)

Workaround

The suggested workaround is to ignore login events without a corresponding external.authentication.succeeded Event.


Related Problem: PRB1388054

Seen In

SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - ITOM - Fundamentals Istanbul Jakarta Kingston r1 - v5.99.6
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Intended Fix Version

Paris

Fixed In

New York Patch 9
Orlando Patch 4

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-04-20 16:43:01
Published:2020-04-14