Overview
Also referred to as "enrichment", this step is where the system checks to see if it has all the transaction information that is required to process the case. If not, assignments are generated to collect the necessary informationflow is executed to gather additional details about the disputed transactions. The Enrich Data Pre-Conditions are evaluated to determine which of the following actions is taken.
| Multiexcerpt include |
|---|
| MultiExcerptName | Actions |
|---|
| PageWithExcerpt | Enrich Data Pre-Conditions |
|---|
|
When the enrichment process is complete, the Post-Enrichment flow is executed to trigger additional activities.
| Drawio |
|---|
| border | false |
|---|
| viewerToolbar | true |
|---|
| |
|---|
| fitWindow | false |
|---|
| diagramDisplayName | |
|---|
| lbox | true |
|---|
| revision | 8 |
|---|
| diagramName | ClaimandDisputeDetails |
|---|
| simpleViewer | false |
|---|
| width | |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| diagramWidth | 751 |
|---|
|
| Tip |
|---|
|
Determine when enrichment should be executed and whether it will be executed by a user or a service. (Enrich Data Pre-Conditions)Determine To define what values should be required and/or displayed for each transaction class. (SetEnrichManuallyConditionGroupsExtension)To configure the maximum number of retry attempts for the integration service, update D_ImplConfig.MaxCreditBureauMaintenanceServiceRetriesare required, update SetEnrichManuallyConditionGroupsExtension. |
References
| Stagil incoming links macro |
|---|
...
