Description
This page allows you to add a verification requirement usage record. A verification requirement usage record is the use of a verification requirement by a case type. A verification requirement can be used by different types of case. For example, a participant's income amount is captured at the integrated case level. If there is a verification requirement to verify the income amount, this requirement can be used by multiple cases within the integrated case.
Page Preview
Page Flow Diagram
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions. Fullscreen
Fields
Details
LabelTypeDescriptionMandatory
NameVERIFICATION_REQUIREMENT_NAMEThe name of the verification requirement. Yes
LevelVERIFICATION_LEVELThe level of verification that must be achieved in order to consider the data verified.Yes
From DateCURAM_DATEThe start of the period during which the verification requirement applies.Yes
To DateCURAM_DATEThe end of the period during which the verification requirement applies.No
Minimum ItemsVERIFICATION_REQUIREMENT_MINIMUM_ITEMSThe minimum number of items that must be provided before the data can be considered verified. The application will not allow the verification to be accepted unless at least the number of items specified within the administration of the verification requirement has been added to the verification.No
Reverification ModeREVERIFICATION_MODEDefines how much, if any, of the verification information that was recorded for an Active evidence record that is copied forward to the In Edit record. Yes
Supplied By ClientCURAM_INDICATORThis field indicates if it is the responsibility of the client as opposed to the third party to supply the verification items. No
MandatoryCURAM_INDICATORA verification requirement may be defined as mandatory or optional. A mandatory verification means that the evidence associated with the verification may not be activated until the rules defined for the verification have been met. Therefore, if an In Edit evidence record has a data item that has a mandatory verification requirement, then the evidence record may not be activated until the verification rules have been satisfied and the data can be considered verified.No
Verification Due Details
LabelTypeDescriptionMandatory
Due DaysNUMBER_OF_DAYSThe number of days after the event specified in due date from by which date the verification must be achieved.No
Warning DaysNUMBER_OF_DAYSThe number of days after the event specified in due date from by which date a warning is raised, indicating that there is an outstanding requirement to verify this piece of data.No
Due Date FromVERIFICATION_DUE_DATE_FROMThe number of days after the event specified in due date from by which date the verification must be achieved.No
Modify Due DateCURAM_INDICATORIndicates whether a case worker can modify the due date for this verification.No
Due Date EventVERIFICATION_REQUIREMENT_DUE_DATE_EVENT_TYPEThe event type which will be executed once the verification due date has been reached.No
Event Details
LabelTypeDescriptionMandatory
Add EventVERIFICATION_REQUIREMENT_ADDED_EVENT_TYPEThe type of workflow event that is raised when a verification to meet this requirement is created.No
Value Changed EventVERIFICATION_REQUIREMENT_VALUE_VERIFIED_CHANGED_EVENT_TYPEThe type of workflow event that is generated when the value of the evidence to be verified has changed.No
Update EventVERIFICATION_REQUIREMENT_UPDATE_EVENT_TYPEThe type of workflow event that is generated when the verification is updated by the addition of removal of a verification item.No
Description
LabelTypeDescriptionMandatory
DescriptionCOMMENTSFree text description of the verification requirement usage. No
Links and Actions
Page Level Actions
LabelDescription
CancelThe Cancel action dismisses the page.
SaveThe Save action creates a new record from the information entered on the page.
Messages
When page is loaded
None
When page is submitted
MessageMessage CatalogConfigurableConfigurable Validation Reference ID
A Due Date Event cannot be specified if there are no Due Days specified.LinkNo
An Exception occurred as the timeout has been reached and the transaction has been rolled back.LinkNo
A Verification Requirement Name must be entered.LinkNo
A Verification Requirement with the name specified already exists. Please enter a new nameLinkNo
Due Days cannot be specified if there is no Due Date From specified.LinkNo
The Due Days specified must not be less than zero days.LinkNo
The login ID %1s does not map to a user name.LinkNo
The Minimum Items specified must not be less than zero.LinkNo
The Modify Due Date indicator cannot be set if there are no Due Days specified.LinkNo
The number of due days must not exceed the period of the verification requirement.LinkNo
The number specified for warning days must be less than that specified for due days.LinkNo
There are no verification item utilizations to satisfy this verification requirement.LinkNo
The To Date must be equal to or later than the From Date.LinkNo
The Warning Days specified must not be less than zero days.LinkNo
Warning Days cannot be specified if there are no Due Days specified.LinkNo
Related Entities
When page is loaded
None
When page is submitted
VerifiableDataItem
VerificationItemUtilization
VerificationRequirement
Technical Information
Page IDVerificationAdmin_createVerificationRequirement
LocationC:\Users\david\dev\src\esystems-inc\Curam_V8_IS\webclient\components\Verification\Verification Admin\Verification Requirement\VerificationAdmin_createVerificationRequirement.uim
Page Load Interface
Page Submit InterfaceVerificationAdministration.createVerificationRequirement
Linked From Pages