REST Service Issues Using GET/PUT Methods With Client
(Doc ID 2975332.1)
Last updated on SEPTEMBER 20, 2023
Applies to:
Oracle Insurance Policy Administration J2EE - Version 11.3.1.17 and laterInformation in this document applies to any platform.
Symptoms
On : 11.3.1.17 version, REST Services
ACTUAL BEHAVIOR
---------------
1. When performing a GET for a particular client using the ClientGUID the return json does not include the companyId, or the companyId is returned as null. The expectation is to return the Company that the Client is attached to e.g. in the AsRole roleCode '02' - note: this is an expected Field on a PUT and it does not allow Null even though that is what the GET returns.
2. When preforming a PUT the ClientGUID is part of the URL however it is ignored. It needs to be added to the body and can be different than the one in the URL and in that case it ignores the URL and updates the one in the body.
3. When making an update the UpdatedGmt is not being updated and there is no record of the update occurring.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Perform a GET for a particular client using the ClientGUID not the return json has a null companyId.
2. Perform a PUT with the URL ClientGUID and body ClientGuid different.
3. Note the UpdatedGmt is not being updated for any PUT.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |