Hi Shamooka Mohapatra

Mapped fields with their change data.

If 10 fields are mapped and data changed for 2 then only 2 mapped fields change data

Regards,

Samir

Hi Samir,

As per our discussion in today's call, Please refer DMS-1547- Details.doc for sample responses.

I have listed queries as well in the document for which your input/discussion is needed. Once our approach is finalized I will analyze and update the estimates.

As discussed, this Jira is only related to returning candidate data (System & Custom Fields) from DMS. Hence updating the description.

CC:Rohan J Khandave,Ganesh Sadawarte

Hi Samir,

PFA Updated Document as per our discussion over call - DMS-1547- Details - V2.doc

CC: Rohan J Khandave, Ganesh Sadawarte

Task Details and Estimate breakdown
A. Fetch history details - 20h
1. Generic logic for all tables in code but process needs to handled Table wise.
2. Tables - Person, Assignment, PersonCustomAttribute, AssignmentCustomAttribute, users, Address, phone, Email, Webtype
B. Validation logic for Sourceproduct and documentid - 4h
C. Fetch source field ids - 4h
D. Fetch dms field names for original resultant set - 4h
E. Create object as per sourcefield and its value - 6h
F. Test cases writing and Performance testing - 10h
G. Unit testing - 4h
H. Code review - 4h

Total Estimate : 56 hrs.

Hello Ramya Tantry,

As per discussion in call with Shamooka Mohapatra & Alex. CBATS needs only mapped fields which are having CBATS source fields ids into DMS.

Thanks,
RohanK

CC – Samir , Satya

API Details :
API URL : api/candidateProfile/{emailAddress}/{sourceProduct}/{documentid}

HTTP Verb : GET
Responses:
1. Last updated mapped document details provided with source field id for CBATS
Input: api/candidateProfile/ramya.tantry@careerbuilder.com/CBATS/9793
Output:

2. All mapped fields details provided for given document id for source product other than CBATS
Input : api/candidateProfile/ramya.tantry@careerbuilder.com/WORKTERRA/9575
Output :

Hi Samir,

Please refer my earlier comment for sample responses. Also refer DMS-1547- Details - V2.doc for additional information related to API.

Assigning this Jira to you for code review.

Note : Triggers are prerequisite for this and it is assumed that Triggers and History tables are created for all tables.

CC: Rohan J Khandave

Verified on Pre-prod.
CBAT Response :

Other Response :

Environment: Preprod - OneIm
Browser: FF and Chrome
API: /api/candidateProfile/

/

/

Scenarios:
1. CBAT User
2. CBES User
3. Onboard user
4. User not matching with document.

All scenarios worked as expected. So, marking jira done.

Sachin Hingole Hrishikesh Deshpande Rohan J Khandave Samir