Notifications

185 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 - 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 - 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 - Configuration Compliance - 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

Fixed In

New York Patch 8
Orlando

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-06-23 08:28:36
Published:2019-11-11