Table Description
PDM Run Evidence Control: This table is used to monitor the external evidence that was received from Trusted Data Sources as it passes though the various stages of PDM & AR processing. The table can be used to drive various processing, including when batch jobs can be run, what records can be processed by batch jobs, the contesting of evidence by the Citizen etc...
Relationship Diagram
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions.
Model Details
Location in Model: Logical View::MetaModel::Curam::HCR::Periodic Data Matching::Entity::PDMRunEvidenceControl
Controlling File: HCR\model\PeriodicDataMatching\Entity\PDMEntity.efx
Table Options
ALLOW_OPTIMISTIC_LOCKINGyes
Attributes (8)
AttributeStereotypeNullableDescriptionDomain DefinitionCodetableDDL Type
pdmRunEvidenceControlIDkeynoThe primary key.INTERNAL_ID SVR_INT64
evidenceDescriptorIDdetailsnoLink to the evidence descriptor of the evidence that is being tracked by this record.EVIDENCE_DESCRIPTOR_ID SVR_INT64
initiallyCompatibledetailsyesRecords, when the evidence is initially processed whether the evidence was deemed to be compatible when compared to the internal evidence. This value is set on first comparison only and not maintained if subsequent updates to either external or internal evidence results in a change of state.This will provide an audit trail if indirect changes disagree with the value of this flag.PDM_EVIDENCE_COMPATIBLEPDMEvidenceCompatibleSVR_STRING<10>
contestedDatedetailsyesDate that the citizens contestation was recorded.CURAM_DATE SVR_DATE
contestedReasondetailsyesComments type field that records the citizen's reason for contesting the TDS evidence.HCR_LARGE_STRING SVR_STRING<1000>
autoAppliedDatedetailsyesThis date is set after an auto-redetermination has been carried out for the case that this evidence is associated with. An auto-redetermination is enacted when a citizen takes no action in the period that was afforded them. Depending on the evidence type and legislative rules it can result in evidence from external sources being applied to the case automatically without the citizen's explicit consent.CURAM_DATE SVR_DATE
pdmRunCaseControlIDdetailsnoThe foreign key to the case process control table.INTERNAL_ID SVR_INT64
contestedBydetailsyesCodetable value indicating who contested the evidence.PDM_CONTESTED_BYPDMContestedBySVR_STRING<10>
Foreign Keys (2)
ChildParent
PDMRunEvidenceControl.evidenceDescriptorIDEvidenceDescriptor.evidenceDescriptorID
PDMRunEvidenceControl.pdmRunCaseControlIDPDMRunCaseControl.pdmRunCaseControlID
Indices (2)
Index NameAttributes
PDMEvidenceIdxevidenceDescriptorID
IND__967219925pdmRunCaseControlID
Operations (13)
OperationStereotypeOptionsDescriptionSQL
readread Standard read method. 
modifymodifyOPTIMISTIC_LOCKING: yes
PRE_DATA_ACCESS: yes
Standard modify method. 
insertinsertAUTO_ID: pdmRunEvidenceControlID
Standard insert method. 
searchByCaseControlIDreadmultiORDER_BY: evidenceDescriptorID ASC
Return the evidence process control records with the specified case process control ID. 
searchByEvidenceDescriptorIDreadmultiORDER_BY: evidenceDescriptorID ASC
Return the set of records associated with the specified evidence descriptor ID. 
searchByCaseIDnsmulti Return the set of records associated with a case.SQL
searchByCaseIDAndRunIDnsmulti Get the evidence control records associated with the specified case and run identifiers.SQL
searchByCaseIDAndAnnualRenewalIndnsmulti Return the set of records associated with a case and PDM/AR flag.SQL
searchByCaseIDRunIDAndAnnualRenewalIndnsmulti Return the set of evidence control records associated with a case, run and PDM/AR flag.SQL
setContestedEvidencensmodify Set the contested evidence. 
setContestedDateAndReasonnsmodify Set the contested date and reason. 
setContestedDateReasonAndContestedBynsmodify Set the contested date, reason and Contested By. 
setAutoAppliedbatchmodifyPRE_DATA_ACCESS: yes
  
Related Pages (5)