Uploaded image for project: 'Document Management System'
  1. Document Management System
  2. DMS-1417

Update DMS GetCandidate API to return all DMS attributes including PII

    Details

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

      Description

      We need to update the GetCandidate API to return all DMS attributes including PII after checking that the user has the correct permissions to read candidate data and PII data.

      If the PII data isn't accessible to the API caller - return blank values

        Attachments

          Activity

          Hide
          swapnil.pandhare Swapnil Pandhare (Inactive) added a comment - - edited

          CC : Samir Rohan J Khandave

          Hi Harshveer Singh,

          From below API, we need to return all fields as mentioned in Jira Description =>

          Relative Url : /api/candidateProfile/{emailAddress}

          PFA dms fields with PII data.DMSFIelds.xlsx

           

          Thanks,

          Swapnil P.

          Show
          swapnil.pandhare Swapnil Pandhare (Inactive) added a comment - - edited CC : Samir Rohan J Khandave Hi Harshveer Singh , From below API, we need to return all fields as mentioned in Jira Description => Relative Url : /api/candidateProfile/{emailAddress} PFA dms fields with PII data. DMSFIelds.xlsx   Thanks, Swapnil P.
          Hide
          priya.dhamande Priya Dhamande (Inactive) added a comment -

          Environment: Preprod - ONEIM 
          API: /api/candidateProfile/{emailAddress}

          Points covered:
          1. Able to run API successfully.
          2. Incorrect Email ID

          All scenarios worked as expected. Refer screen capture.

          Samir Rohan J Khandave Hrishikesh Deshpande Sachin Hingole

           

          Show
          priya.dhamande Priya Dhamande (Inactive) added a comment - Environment: Preprod - ONEIM  API: /api/candidateProfile/{emailAddress} Points covered: 1. Able to run API successfully. 2. Incorrect Email ID All scenarios worked as expected. Refer screen capture. Samir Rohan J Khandave Hrishikesh Deshpande Sachin Hingole  

            People

            Assignee:
            harshveer.singh Harshveer Singh (Inactive)
            Reporter:
            ravi.banda Ravi Banda (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 16h Original Estimate - 16h
                16h
                Remaining:
                Time Spent - 58.5h Remaining Estimate - 8h
                8h
                Logged:
                Time Spent - 58.5h Remaining Estimate - 8h
                58.5h