Table Description
ViewProcessor:

A View Processor supplements the standard processing invoked when a data is read from the Citizen's Data Hub. View Processors are associated via the context attribute with a "Data Hub Context". The same context name is used to define other entities associated with the Data Hub Context such as the Transform. The View Processor is invoked after the Transform has converted the Evidence XML into datastore XML. The View Processor references a custom class that can be defined by developers. In this class the developer can add code that inserts additional information into the data store xml. There can be multiple ViewProcessors defined for the same Data Hub Context, each identified by a differenty logical name.

Example

A Customer adds two new ViewProcessors and associates them with the "AllEvidence" Data Hub Context. One references the Out-Of-The-Box class curam.citizen.datahub.internal.impl.HouseholdCustomViewProcessorFactory and the other references the Out-Of-The-Box class curam.citizen.datahub.internal.impl.CustomPersonAddressViewProcessorFactory. The former pulls in all related members of a Citizen's household and puts them into the datastore xml. The latter extracts a Citizen's Residential and Mailing addresses. All of this information is also inserted into the datastore xml.

Model Details
Location in Model: Logical View::MetaModel::Curam::WorkspaceServices::DataHub::Entity::ViewProcessor
Controlling File: WorkspaceServices\model\DataHub.efx
Table Options
ALLOW_OPTIMISTIC_LOCKINGyes
Attributes (5)
AttributeStereotypeNullableDescriptionDomain DefinitionCodetableDDL Type
viewProcessorIDkeynoUnique reference number of this record.INTERNAL_ID SVR_INT64
logicalNamedetailsnoA unique logical name for the View Processor. View Processors associated with the same context are executed in alphabetical order of their logical name. So AAA is executed before BBB for the Data Hub Context "HavingABaby" VIEW_PROCESSOR_LOGICAL_NAME SVR_STRING<256>
contextdetails Identifies the related Data Hub Context.CITIZEN_CONTEXT_NAME SVR_STRING<256>
viewProcessorFactorydetails Contains the class name of the Custom View Processor factory. The class must implement the interface curam.citizen.datahub.impl.CustomViewProcessorFactory. VIEW_PROCESSOR_CUSTOM_FACTORY SVR_STRING<256>
recordStatusdetails Record status of this record i.e. Active, Cancelled.RECORD_STATUSRecordStatusSVR_STRING<10>
Operations (6)
OperationStereotypeOptionsDescriptionSQL
readread Standard Operation 
modifymodifyOPTIMISTIC_LOCKING: yes
Standard Operation 
searchByRecordStatusreadmulti <p>Return all View Processors with a particular Record Status.</p> @curam.example <p>Return all Active ViewProcessor records.</p>  
readByLogicalNamensread Get the View Processor associated with a unique logical name. 
searchActiveByContextreadmultiORDER_BY: logicalName
<p>Return all the view processors associated with a given Data Hub Context.</p> @curam.example <p>The &quot;AllEvidence&quot; context is associated with two View Processors.</p>  
insertinsertAUTO_ID: viewProcessorID
Standard Operation 
Related Pages (0)