HRIntegrationsHelper() script include in 'Trigger OutBound Services' business rule on sn_hr_core_case causes javascript.EcmaError: Cannot read property "transaction_log" from nullDescriptionHRIntegrationsHelper() script includes expects sn_hr_core_case records to have a 'transaction_log' field when triggered from 'Trigger OutBound Services' business rule, but sn_hr_core_case does not have transaction_log field defined in the table.This causes the error:org.mozilla.javascript.EcmaError: Cannot read property "transaction_log" from nullCaused by error in sys_trigger.f385492edb3a8010fc04ed384b9619b6 at line 6Steps to Reproduce 1- Open the OOB 'Trigger OutBound Services' Business Rule ( /sys_script.do?sys_id=078dabbf77d03300d0e310389a1061d6 ).2- Observe the call HRIntegrationsHelper.getMatchingOutboundServices. The code attempts to access the field transaction_log which does not exists on the table.WorkaroundThis problem has been fixed. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to. As a workaround, the condition on the script include (line 336) can be updated as below to add the check:if (glideRecord.isValidField('transaction_log') && glideRecord.transaction_log && glideRecord.transaction_log.changes())Related Problem: PRB1387212