Xog in a list of risks does not validate the existence of its ownerCode

Document ID : KB000122902
Last Modified Date : 12/12/2018
Show Technical Document Details
Issue:
XOG in a list of risks, the Ownercode (resource associated to the Risk) is only validated on the first of the risks from the list.
If an invalid resource is being specified, ownerCode="dummy", the XOG in does not fail and adds the risk using the onwerCode from the previous risk from the list.


STEPS TO REPRODUCE

1. Add a new project or use an existing project.
For instance, Project with ID "MYPROJECT"
projectCode="MYPROJECT"

2. Add a new resource or use an existing resource.
For instance, Resource with ID "myresource"

3. Xog in a list of risks for this project.
The first risk having "myresource" as its owner.
ownerCode="myresource"

The other risks having a non existing resource on the application
ownerCode="dummy"

The complete XML for the XOG in

****
<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_risk.xsd">
  <Header version="7.5" externalSource="ORACLE-FINANCIAL" action="write" objectType="risk"/>
  <risks>
    <risk approachCode="" assumptions="" categoryTypeCode="" code="TEST_1" description="Desc 1" impactCode="" impactDescription="" name="Risk name" ownerCode="myresource" priorityCode="LOW" probabilityCode="" projectCode="MYPROJECT" resolution="High probability SER opportunity." statusCode="OPEN" targetResolutionDate="2019-06-07">
    </risk>
    <risk approachCode="" assumptions="" categoryTypeCode="" code="TEST_2" description="Desc 2" impactCode="" impactDescription="" name="Risk name 2" ownerCode="dummy" priorityCode="LOW" probabilityCode="" projectCode="MYPROJECT" resolution="High probability SER opportunity." statusCode="OPEN" targetResolutionDate="2020-01-03">
    </risk>
  </risks>
</NikuDataBus>

***


Expected Results: The XOG in should fail because the resource "dummy" does not exist.

Actual Results: All risks as created.
The risks having an invalid ownerCode are using the ownerCode from the previous entry/risk being created.
Environment:
15.4.1, 15.5
Cause:
This issue is reported as Defect:  DE45878
 
Resolution:
The Defect DE45878 has been resolved and will be included in CA PPM version 15.6