The Update Child Incidents base system business rule sends empty comments to child incident's caller, and that produces an empty update. Because of those actions, the following occurs:
- confuses the caller by sending them a notification containing: 'Dear customer, we have some new information regarding your request #1234567: (blank)'
- confuses the people assigned to child tickets because there is a false update of the ticket with no new information
- confuses the people on the other end of an integration by sending them an empty work notes update
- causes other cascaded scripts to run when they should not

Steps to Reproduce

  1. Create two incidents.
  2. Designate one of the incidents as the parent for another.
  3. Update comments OR work notes in the parent incident.
    You should see both Comment copied from Parent Incident in the Additional comments and Work note copied from Parent Incident in the Work notes, even though only one field was updated. This issue causes empty notifications to be sent to th caller of the child incident.


The business rule Update Child Incidents always copies the values from additional_comments and work_notes from the parent incident to the child incident, whether they are empty or not.

The workround is to import the xml file attached to this known error article.

NOTE: Importing the attached xml file overwrites any changes made to the script. Revert the record 'sys_script_8f61f1b00a0a3c7401aac471d27a2718' to the base system version before upgrading.

Related Problem: PRB635292

Seen In

Eureka Patch 10
Eureka Patch 8
Fuji Patch 10
Fuji Patch 12 Hot Fix 1
Fuji Patch 7 Hot Fix 3
Geneva Patch 4
Geneva Patch 6
Geneva Patch 8 Hot Fix 1

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-01-15 03:43:01