-
Type:
Bug
-
Status: Done
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: Carry Over - Fall
-
Labels:None
-
Company:All Clients/Multiple Clients
-
Epic Link:
As we talked during Friday meeting, there's the current feedback we have regarding your API. We did not have much time to further test your API request/response consistency since then but will keep going.
However, top priority for today: could fix this bug: [https://apimanagement.cbplatform.link/#routes/tester?preURL=https%3A%2F%2Fapi.careerbuilder.com%2F&postURL=corporate%2Fdms%2Fapi%2Fcandidate%2Fdocument%2Fcreate&method=post&contentType=application%2Fjson&acceptType=application%2Fjson&version=default®ion=productionus&flow=authorization_code&userDid=U314KN6Y8LSZN111SMW&accountDid=AKF7Y86DJ2Z4VLMS9MN&headers=&body={%0D%0A+%22email%22%3A%22joris.berthelot%40careerbuilder.com%22%2C%0D%0A+%22payload%22%3A
{%0D%0A++++%22candidat_adresse1%22%3A+%223469+Coolidge+Avenue%22%2C%0D%0A++++%22candidat_adresse2%22%3A+%22%22%2C%0D%0A++++%22candidat_cp%22%3A+%2294602%22%2C%0D%0A++++%22candidat_nom%22%3A+%22Test%22%2C%0D%0A++++%22candidat_prenom%22%3A+%22Olivier%22%2C%0D%0A++++%22candidat_region_actu%22%3A+%22CA%22%2C%0D%0A++++%22candidat_tel_fixe%22%3A+%22%22%2C%0D%0A++++%22candidat_ville%22%3A+%22Oakland%22%2C%0D%0A++++%22poste_date_debut%22%3A+null%2C%0D%0A++++%22poste_intitule%22%3A+%22Data+Warehouse+Analyst%22%0D%0A++}%2C%0D%0A+%22requisitionId%22%3A%221417%22%2C%0D%0A+%22sendDocument%22%3A+true%2C%0D%0A%22sourceProduct%22%3A%22CBATS%22%2C%0D%0A+%22sourceUserId%22%3A%22991%22%2C%0D%0A+%22templateId%22%3A%22401%22%0D%0A}]
Hi Rohan J Khandave,
We have verified on Preproduction
Refer below status :
1. Update user API : Added new API to update user details - PUT api not working (will fix under DMS-1227)
2. Make User relates API consistent : All users api are now have same url - Pass
3. Send Document Status Id : Added statusid into document latest status & status history API - Pass
4. issue regarding the document history : Handle global templates in latest status & status history API - Pass
5. Register company return 200 status even company already exists. : Done ,now return 409 , conflict
6. Return 404 when company & user not found in getCompany & getUser API : Fail(will fix DMS-1194).
As reported issues will fix under respective jira. closing this ticket
Thanks,
Jayshree
Jayshree Nagpure (Inactive)
added a comment - Hi Rohan J Khandave ,
We have verified on Preproduction
Refer below status :
1. Update user API : Added new API to update user details - PUT api not working (will fix under DMS-1227 )
2. Make User relates API consistent : All users api are now have same url - Pass
3. Send Document Status Id : Added statusid into document latest status & status history API - Pass
4. issue regarding the document history : Handle global templates in latest status & status history API - Pass
5. Register company return 200 status even company already exists. : Done ,now return 409 , conflict
6. Return 404 when company & user not found in getCompany & getUser API : Fail(will fix DMS-1194 ).
As reported issues will fix under respective jira. closing this ticket
Thanks,
Jayshree
Priya Dhamande Sachin Hingole Hrishikesh Deshpande Satya 
Below points consider into this JIRA.
1. Update user API : Added new API to update user details
2. Make User relates API consistent : All users api are now have same url
3. Send Document Status Id : Added statusid into document latest status & status history API.
4. issue regarding the document history : Handle global templates in latest status & status history API.
5. Register company return 200 status even company already exists. : Done ,now return 409 , conflict
6. Return 404 when company & user not found in getCompany & getUser API : Yes now return 404 , not found.