/
Moving Pipeline from one Candidate/Job to another

Moving Pipeline from one Candidate/Job to another

Introduction

 

The moving pipeline feature is designed to assist administrators in addressing data inaccuracies by allowing them to link any pipeline to another job or candidate. This feature is particularly useful in scenarios where:

  • A pipeline has been added to an incorrect job.

  • A pipeline was created for the wrong user (e.g., an employee account vs. a personal account).

The moving pipeline feature provides a special operation to re-link a pipeline to another job or candidate, ensuring data consistency and accuracy.

Validation Rules: 

  1. The new job must have an identical pipeline workflow.

  2. It is not allowed to add a pipeline to an archived job or candidate.

Data Impact when Moving to Another Job

 

  1. Pipeline Participants:

  • If synchronisation is enabled, job participants are automatically copied to the pipeline.

  • Constants for transferring participants when creating a pipeline are applied.

  1. Screening Question Answers:

  • Answers for screening questions are completely removed from the pipeline after it is moved to a new job.

  1. Candidate Interaction:

  • Relevant messages are updated to reflect new job details.

 

Data Impact when Moving to Another Candidate

Candidate Interaction: 

  • Relevant messages are moved to the new candidate's omnichat.

 

Steps to Move a Pipeline to Another Job or Candidate

 

  1. Navigate to the Pipeline Dropdown menu in the http://EVA.ai interface.

  2. Select the "Move to Another Job" or "Move to Another Candidate" option from the dropdown menu.

  1. A modal window will open. Use the search field to filter the list of jobs or candidates by entering relevant keywords.

  • The central panel will display a list of entities based on your search. Select the desired job or candidate by clicking the corresponding radio button.

  1. Click the "Submit" button to move the pipeline to the selected job or candidate.

  • If you wish to cancel the operation, click the "Cancel" button.

 

Example Scenarios

Example 1: Moving a Pipeline to Another Job

Scenario: A pipeline was mistakenly added to the "Marketing Manager" job instead of the "Sales Manager" job.

Steps:

  1. Open the Pipeline Dropdown menu for the pipeline currently linked to "Marketing Manager."

  2. Select "Move to Another Job."

  3. In the search field, enter "Sales Manager" to find the correct job.

  4. Select "Sales Manager" from the list of search results.

  5. Click "Submit" to complete the move.

The pipeline is now linked to the "Sales Manager" job, and all relevant data is updated accordingly.

 

Example 2: Moving a Pipeline to Another Candidate

Scenario: A pipeline was created for a personal account instead of an employee account.

Steps:

  1. Open the Pipeline Dropdown menu for the pipeline currently linked to the personal account.

  2. Select "Move to Another Candidate."

  3. In the search field, enter the name of the correct employee account.

  4. Select the correct employee from the list of search results.

  5. Click "Submit" to complete the move.

The pipeline is now linked to the employee account, and all relevant data is updated accordingly.

 

Security and Validation

  • Only administrators can perform this operation.

  • Validation checks ensure that the new job has the same pipeline workflow and that neither the current nor the new job/candidate is archived.

Note:

  • If the new job or candidate is not defined, an error message will appear.

  • If the new job has a different pipeline workflow, the move will be prevented.

  • If the current or new job/candidate is archived, the move will be prevented.

  • We will not support Bulk movement