Notifications

1765 views

Description

Trigger rule not triggered if Assignment group field is pre-populated.

Steps to Reproduce

  1. Create a new trigger rule.
  2. When to activate:
    • Table: incident
    • Match conditions: All
    • Condition: Short description > contains > test22
  3. What actions to take:
    • Group: Database
    • Trigger action: Script
    • Trigger script:
      testEscalate();
      function testEscalate(){
          gs.log("333START33TEST333ESCALATION");
      }
  4. Create a new incident.
  5. In Short Description, type test22.
  6. Leave the assignment group field empty.
    The escalation fires as expected and the Assignment Group is updated with Database. Server logs show the gs.log statement.
  7. Create another new incident.
  8. In Short Description, type test22.
  9. In Assignment group, type Database.
    The escalation does not fire. You can verify this by monitoring the server logs and looking for the gs.log statement.

Workaround

There is no workaround as this is the current expected behavior of trigger rules. 

If you have business processes in place where the assignment_group and/or the assigned_to fields is/are mandatory but you still want to use trigger rules, you can do the following:

  1. Create a before-insert business rule on the table, in this case, incident.
  2. Make the condition for the business rule match the condition of any trigger rules on incident you want to fire.
  3. In the expressions, set current.assignment_group = null; and current.assigned_to = null;
  4. Set the order number to 10.

This lets you keep all your current processing and user experience the same, but lets you use trigger rules to launch workflows.


Related Problem: PRB606557

Seen In

Eureka Patch 1
Eureka Patch 11
Eureka Patch 4 Hot Fix 1
Fuji Patch 3
Fuji Patch 5
Fuji Patch 8
Geneva Patch 7

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-10-09 00:52:24
Published:2015-02-17