84 views

Description

The On-call: Assign workflow activity is passing a sys id, but GlideScriptableObject.argString() is taking it as a long, not as a String. Notifications are not sent.

Steps to Reproduce

  1. Ensure that the On-call Scheduling and Notify plugins are activated.
  2. Navigate to On-Call Scheduling > Escalation > Trigger Rules.
  3. Open any of the demo data trigger rules.
  4. Note the conditions.
  5. Navigate to Incident > Create New.
  6. Ensure that the Assignment group field is empty.
  7. Ensure that the conditions stated in the trigger rule from step 3 are fulfilled to assign the corresponding group.
  8. Click Submit.
    Note that the notification fails to send due to error on workflow context. (The logs will show the error.) The notification should be sent out to the assigned rota group members.

Workaround

Update the workflow activity.

  1. Navigate to https://<your_instance_name>/sys_variable_value.do?sys_id=b63b24529f031100d8f8700c267fcf14.
  2. Find the line that reads:
    rota.who(workflow.inputs.assignment_group);
  3. Change that line to:
    rota.who(workflow.inputs.assignment_group + '');
    This change ensures that the API takes a string value, rather than a long.

Related Problem: PRB666264

Seen In

Helsinki Patch 6

Fixed In

Helsinki

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-09-05 16:09:43
Published:2017-01-12