The new type of case should be included in the CT_VerificationTypeCode code table. This would correspond to the relatedItemID of the Verification Requirement Usage entity. For example, Product Delivery, Integrated Case.
The various possible values for each code in the VerificationTypeCode code table would correspond to a relatedItemType field of the Verification Requirement Usage entity. For example, if an Integrated case is selected as verification type code, the possible values are the individual Integrated Case types recorded. The various possible values for this case type would be same as the value of caseType inserted in the case header table when the corresponding case is created.
With this approach, whenever a type of case has to be handled by the verification engine, it would retrieve the corresponding verificationType for the given case type from the administration configuration dynamically and process the same.
If there is a need to consider a new case type, there should be an entry made in CT_VerificationTypeCode.ctx. For example, Health Care Reform Cases which may correspond to Application Cases present in the CT_CaseTypeCode.ctx.
There must also be an entry in the Curam-config.xml for the domain definition used for RelatedTypes, so that it appears in the search pop-up in the administration section.
When a verification requirement is configured and applied on the administration section for example, Health Care Reform Case (specified in CT_VerificationTypeCode) and Application Cases (specified in CT_CaseTypeCode) the same will be processed by the Verification Engine.