Example: Implementing a Person/Prospect Person Evidence Replicator

The following example outlines how to implement a replicator. In this scenario, Sample Foreign Residency has been configured as a new dynamic evidence type. For more information on how to configure a new evidence type, please see the Cúram Dynamic Evidence Configuration Guide. The new Sample Foreign Residency evidence type has the following attributes,

• participant - the case participant role id of the person/prospect person that the evidence is being entered for
• country - the country of residency
• fromDate - the date the residency started
• toDate - the date the residency ended
• reason - the reason for residency in this country

It has been assumed that this dynamic evidence type has been activated and is configured for use with person/prospect person. Until now Sample Foreign Residency information has been stored as static evidence on the SampleForeignResidency database table. It is now necessary to store this information as dynamic evidence. A new replicator may be required to replicate evidence changes to the legacy database table so that this table is in sync with the dynamic evidence.

The steps involved in implementing a replicator are:

• Provide a replicator interface for the dynamic evidence type
• Provide a replicator implementation that will replicate dynamic evidence to the legacy database table
• Implement an event listener that will trigger the replication
• Add a binding to the new event listener implementation