Person Reconciliation

Introduction

Once you have completed your Relationship Specification configuration, your next step will be to review your collection's Person Reconciliation strategy.  On this screen, you will be able to specify the strategy you'd like to use to reconcile person fields between your repositories.

Instructions

To configure Person Reconciliation, click the 'Person Reconciliation' link.

Click 'Person Reconciliation'

 

Tasktop comes with a default person reconciliation strategy ("Copy with Default Matching"), which matches based on name, ID, and/or e-mail. 

More specifically, the algorithm will compare the metadata from each side as follows:

  • Username from source to username on target
  • Username from source to ID on target
  • ID from source to username on target
  • ID from source to ID on target
  • Email from source to email from target

Please review the Connector Docs to determine which fields are available for your specific repository.  If a field is not available, Tasktop will simply skip that step.

If the default strategy does not cover your needs, you can also configure a Person Reconciliation extension on the settings screen, and select that extension here.

We recommend reviewing our Connector Docs to see each specific connector's unique fields available for Person Reconciliation so that you can better understand your specific use case.

(lightbulb) Remember that person fields will flow between your repositories based on the field flow configuration you've enabled (i.e. one-way, two-way, no update, etc).  For a person field not to flow, it must either not be mapped to your collection(s), or be set to 'no update' on the field flow screen.

Select Person Reconciliation Strategy

Next Steps

Once Person Reconciliation is complete, your next step will be to configure State Transitions, if your repository utilizes state transitions or workflows.  If not, your collection configuration is complete, and you can move on to Step 4: Configure your Integration.