Details
-
New Feature
-
Resolution: Completed
-
Minor
-
COmanage Match Future
Description
After a Potential Match is resolved, Match (when connected to Registry) should make a Registry API call to resume processing of the Pipeline (or Enrollment Flow?) associated with the Match request, presumably by Match passing the SOR+SORID to Registry, which can then figure out what the invoking request was? Or maybe Registry needs to send some metadata with the request that Match sends back on resolution.
Attachments
Issue Links
- has dependent
-
CO-2480 External Match Returns 500, not 202; Callback URL Support
- Resolved