(Re)Assigning a Risk With XOG Does Not Send Notifications
search cancel

(Re)Assigning a Risk With XOG Does Not Send Notifications

book

Article ID: 445002

calendar_today

Updated On:

Products

Clarity FedRAMP Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

When assigning or reassigning a risk instance using XOG, the users do not receive notifications (available in Organizer).

Steps to Reproduce:

  1. Create a project and a risk.
  2. XOG out (read) the risk.
  3. Update the Owner/Assigned To attribute to a different user with Classic notifications enabled.
    <risk [...]
      ownerCode="user"
      [...]>
    </risk>
  4. XOG in (write) the risk.

Expected Results: The user receives a notification 'This risk has been assigned to you.' available in the Organizer.

Actual Results: The user does not receive any notification in the Organizer.

Similarly, the notification 'The following risk has been reassigned.' is not received when the risk is reassigned to a different user when using XOG.

Environment

Clarity 16.3.3

Cause

DE205257

Resolution

This issue has been fixed in Clarity 16.4.3.

 

Workaround: Use the equivalent REST API endpoint for updating the risk instance:

PATCH http://example.com/ppm/rest/v1/projects/5xxxxxx/risks

Body:

{"d":[{"assignedTo":"5yyyyyy","_internalId":5zzzzzz}]}

Replace:

  • 5xxxxxx: Internal Project ID
  • 5yyyyyy: Internal Resource ID
  • 5zzzzzz: Internal Risk ID