Notifications

25 views

Description

The BR "Predict COE, Service after insert" is executing a script before insert on the record and making an update which is causing "Unique Key violation" on HR cases.

Steps to Reproduce

  1. Go to "sn_hr_core_case.do"
  2. Set source to "email"
  3. Fill in mandatory fields and submit

Behavior: Getting "unique key violation" error

Workaround

Please find below workarounds to choose from

Either:

  • Remove line 9 "current.update()" of Business Rule "Predict COE, Service after insert"

Or

  • Set property "sn_hr_core.auto_categorization" to "false" (Can also be done via "HR Administration" -> "Properties" -> "Enable HR Case auto categorization" -> uncheck)

Related Problem: PRB1370699

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 - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3

Intended Fix Version

Orlando

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:2019-12-02 08:25:49
Published:2019-11-11