Registration Data Pushes

A Registration Data Push (RDP) groups beneficiary records that are prepared and pushed from Country Workspace to HOPE Core.

RDPs are managed within the selected Program in the Analyst / Collector Workspace.

For Programs with biometric deduplication enabled, deduplication is performed as a separate step before the RDP can be pushed.

RDP workflow

flowchart LR
    A[Create RDP] --> B[RDP created]
    B --> C{Biometric deduplication required?}
    C -->|Yes| D[Run deduplication]
    C -->|No| E[Push to HOPE Core]
    D -->|Deduplicated| E
    E -->|Failed| F[Retry push]
    F --> E
    B -.->|Cancel| G[Cancel RDP]
    F -.->|Cancel| G

Creating an RDP starts the workflow. For biometric Programs, deduplication must complete successfully before the RDP can be pushed to HOPE Core.

A failed push can be retried, and an open RDP can be cancelled when the cancellation requirements are satisfied.

See Lifecycle and statuses for RDP statuses and transitions.

Before creating an RDP

Make sure that the required Office and Program are selected and the beneficiary records are ready for processing.

Country Workspace performs additional checks before creating an RDP. See Create an RDP for the creation process and conditions that can prevent it.

Biometric deduplication

For Programs with biometric deduplication enabled, the RDP must be successfully deduplicated before it can be pushed to HOPE Core.

See RDP deduplication for the deduplication workflow and Program for deduplication settings.

Push to HOPE Core

The push runs asynchronously and may include resetting an existing HOPE RDI before beneficiary data is sent.

See Push to HOPE Core for the push workflow, retries, and successful completion.

Troubleshooting

See Troubleshooting if an RDP cannot be created, deduplication fails, or a push does not complete as expected.