70 views

Description

Through the Istanbul release, a business rule created for the sys_update_xml table would be triggered when a new update record was created for a new business rule or an update was made on a script include, which creates new records or updates the existing one on the table. However, beginning with the Jakarta release, updates on the business rule that creates a record in sys_update_xml do not trigger the business rule on sys_update_xml. However, if you modify records directly in sys_update_xml, the business rule is triggered.

Steps to Reproduce

  1. Create a new business rule with the following parameters:

    • Name: "log on update" 
    • Runs on Table: "Customer Update [sys_update_xml]" 
    • When: Before 
    • Advanced: true 
    • Insert: true 
    • Update: true
    • Script:
    (function executeRule(current, previous /*null when async*/) {
    gs.log('updateSet: ' + current.update_set);
    })(current, previous);
  2. Save the business rule.

  3. Create a new Script Include with any content.

  4. Go to System logs > all modules.

    Expected Result: 

    • When the system property glide.update_xml_version.enable_workflow is true, the log should be inserted when the new script include is created, and the business rule therefore executes correctly.

    • When the system property glide.update_xml_version.enable_workflow is false (the default value), no log is created.

    Actual Result: No log is created when the new script include is created, and therefore the business rule does not execute.

 

Workaround

Contact Customer Support for assistance.

 


Related Problem: PRB1108536

Seen In

There is no data to report.

Fixed In

Jakarta Patch 5
Kingston

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-06-12 06:25:02
Published:2018-06-12