Details

    • Type: New Feature
    • Status: Done
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: CBAT Offer Letter - Fall
    • Labels:
      None

      Description

      API will rerturn candidate data (System & Custom Fields) from DMS

       

        Attachments

        1. CP1.JPG
          CP1.JPG
          25 kB
        2. CP2.JPG
          CP2.JPG
          20 kB
        3. DMS-1547- Details.doc
          32 kB
        4. DMS-1547- Details - V2.doc
          24 kB
        5. Pre-prod_1547_CBES.jpg
          Pre-prod_1547_CBES.jpg
          229 kB
        6. Pre-prod_1547.jpg
          Pre-prod_1547.jpg
          219 kB
        7. Screenshot (3560).png
          Screenshot (3560).png
          173 kB
        8. Screenshot (3561).png
          Screenshot (3561).png
          218 kB
        9. Screenshot (3565).png
          Screenshot (3565).png
          165 kB
        10. Screenshot (3566).png
          Screenshot (3566).png
          220 kB
        11. Screenshot (3567).png
          Screenshot (3567).png
          224 kB

          Activity

          Hide
          ramya.tantry Ramya Tantry (Inactive) added a comment -

          Hi Samir,

          Please provide the Candidate Profile API details where these changes are to be done.

          CC:Rohan J Khandave

          Show
          ramya.tantry Ramya Tantry (Inactive) added a comment - Hi Samir , Please provide the Candidate Profile API details where these changes are to be done. CC: Rohan J Khandave
          Hide
          samir Samir added a comment -

          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

          Show
          samir Samir added a comment - 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
          Hide
          ramya.tantry Ramya Tantry (Inactive) added a comment -

          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

          Show
          ramya.tantry Ramya Tantry (Inactive) added a comment - 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
          Hide
          ramya.tantry Ramya Tantry (Inactive) added a comment -

          Hi Samir,

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

          CC: Rohan J Khandave, Ganesh Sadawarte

          Show
          ramya.tantry Ramya Tantry (Inactive) added a comment - Hi Samir , PFA Updated Document as per our discussion over call -  DMS-1547- Details - V2.doc CC: Rohan J Khandave , Ganesh Sadawarte
          Hide
          ramya.tantry Ramya Tantry (Inactive) added a comment -

          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.

          Show
          ramya.tantry Ramya Tantry (Inactive) added a comment - 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.
          Hide
          rohan.khandave Rohan J Khandave (Inactive) added a comment -

          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

          Show
          rohan.khandave Rohan J Khandave (Inactive) added a comment - 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
          Hide
          ramya.tantry Ramya Tantry (Inactive) added a comment -

          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 :

           

          Show
          ramya.tantry Ramya Tantry (Inactive) added a comment - 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 :  
          Hide
          ramya.tantry Ramya Tantry (Inactive) added a comment -

          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

          Show
          ramya.tantry Ramya Tantry (Inactive) added a comment - 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
          Hide
          ramya.tantry Ramya Tantry (Inactive) added a comment -

          Verified on Pre-prod.
          CBAT Response :

          Other Response :

          Show
          ramya.tantry Ramya Tantry (Inactive) added a comment - Verified on Pre-prod. CBAT Response : Other Response :
          Hide
          priya.dhamande Priya Dhamande (Inactive) added a comment -

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

          {emailAddress}

          /

          {sourceProduct}

          /

          {documentid}

          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

          Show
          priya.dhamande Priya Dhamande (Inactive) added a comment - Environment: Preprod - OneIm Browser: FF and Chrome API: /api/candidateProfile/ {emailAddress} / {sourceProduct} / {documentid} 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

            People

            Assignee:
            priya.dhamande Priya Dhamande (Inactive)
            Reporter:
            samir Samir
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 70h
                70h
                Remaining:
                Time Spent - 62.75h Remaining Estimate - 7.25h
                7.25h
                Logged:
                Time Spent - 62.75h Remaining Estimate - 7.25h
                62.75h