Uploaded image for project: 'New Features 2017'
  1. New Features 2017
  2. NF-2123

Bullhorn Integration->Issues when pulling Bullhorn candidate data to Workterra

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Integrations
    • Labels:
      None
    • Bug Type:
      Functional
    • Level:
      Admin
    • Module:
      Bullhorn
    • Reported by:
      Harbinger
    • Item State:
      Production Complete - Closed
    • Issue Importance:
      Q2
    • Browser:
      Google Chrome

      Description

      Please let us know how we can deal with below scenarios:

      Scenario 1
      When email ID is set as user id in Workterra and if bullhorn candidate do not have email ID ,then while adding such employee to WT. Below message is displaying:
      "Error occurred while adding employee record, please contact system administrator."
      Refer below screenshot "Error_WithhoutEmailID.JPG" for more details.
      Please make a note in this case though the UI shows error while adding employee, employee is getting added to Workterra DB with email ID as NULL

      Scenario 2
      When userid generation criteria is set as SSN or any other criterion in Workterra which does not have any corresponding data in Bullhorn, then while adding such candidate to WT below error is displaying:
      "Object reference is not set to instance of an object"
      Refer screenshot "ObjectReference.JPG" for more details.

      Cc: Saurabh Sablaka, Prasad Pise

        Attachments

          Issue Links

            Activity

            Hide
            saurabh.sablaka Saurabh Sablaka (Inactive) added a comment -

            Scenario 1
            When email ID is set as user id in Workterra and if bullhorn candidate do not have email ID ,then while adding such employee to WT. Below message is displaying:
            "Error occurred while adding employee record, please contact system administrator."

            Cause: This was due to validation not firing in case of bullhorn add employee & assign tour.
            Correction: We have fixed this issue and applied all the required validation.
            Affected files: /trunk/WORKTERRAweb/Web/Web Projects/WorkterraAPI/WorkterraAPI/Models/OnBoard/TourStepsStatus.cs

            Scenario 2
            When userid generation criteria is set as SSN or any other criterion in Workterra which does not have any corresponding data in Bullhorn, then while adding such candidate to WT below error is displaying:
            "Object reference is not set to instance of an object"

            Cause: This is due to invalid criteria selected. This need to be taken care while company setup to customize only email address as username criteria for ATS based company. This issue is invalid and should be handled at customization level.

            Show
            saurabh.sablaka Saurabh Sablaka (Inactive) added a comment - Scenario 1 When email ID is set as user id in Workterra and if bullhorn candidate do not have email ID ,then while adding such employee to WT. Below message is displaying: "Error occurred while adding employee record, please contact system administrator." Cause: This was due to validation not firing in case of bullhorn add employee & assign tour. Correction: We have fixed this issue and applied all the required validation. Affected files: /trunk/WORKTERRAweb/Web/Web Projects/WorkterraAPI/WorkterraAPI/Models/OnBoard/TourStepsStatus.cs Scenario 2 When userid generation criteria is set as SSN or any other criterion in Workterra which does not have any corresponding data in Bullhorn, then while adding such candidate to WT below error is displaying: "Object reference is not set to instance of an object" Cause: This is due to invalid criteria selected. This need to be taken care while company setup to customize only email address as username criteria for ATS based company. This issue is invalid and should be handled at customization level.
            Hide
            kunal.kedari Kunal Kedari (Inactive) added a comment -

            We have verified the scenario #1 on local, now when email ID of candidate is not mentioned in BH below validation message is displaying:
            "Required parameter emailID is missing"
            As mentioned in above comment #2 should be handled at customization level.

            We can deploy this change to stage.

            Show
            kunal.kedari Kunal Kedari (Inactive) added a comment - We have verified the scenario #1 on local, now when email ID of candidate is not mentioned in BH below validation message is displaying: "Required parameter emailID is missing" As mentioned in above comment #2 should be handled at customization level. We can deploy this change to stage.
            Hide
            kunal.kedari Kunal Kedari (Inactive) added a comment -

            Verified the scenario #1 on Production, when email ID of candidate is not mentioned in BH below validation message is displaying:
            "Required parameter emailID is missing"

            Closing the ticket.

            Cc: Saurabh Sablaka, Prasad Pise

            Show
            kunal.kedari Kunal Kedari (Inactive) added a comment - Verified the scenario #1 on Production, when email ID of candidate is not mentioned in BH below validation message is displaying: "Required parameter emailID is missing" Closing the ticket. Cc: Saurabh Sablaka , Prasad Pise

              People

              Assignee:
              kunal.kedari Kunal Kedari (Inactive)
              Reporter:
              kunal.kedari Kunal Kedari (Inactive)
              Developer:
              Saurabh Sablaka (Inactive)
              QA:
              Kunal Kedari (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Code Review Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  Time Spent - 1.25h Remaining Estimate - 2.75h
                  2.75h
                  Logged:
                  Time Spent - 1.25h Remaining Estimate - 2.75h
                  1.25h