Description
This page allows you to modify a Liquid Resources evidence record.
Page Preview
Page Flow Diagram
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions. Fullscreen
Fields
LabelTypeDescriptionMandatory
ValueCURAM_AMOUNTMonetary value of the liquid resource.Yes
Amount OwedCURAM_AMOUNTMonetary amount that is owed to the institution who lent the liquid resource. As mentioned above, for loan and note liquid resource types, the system performs calculations to ensure that the household member is scheduled to pay back the loan/note in full. The system compares the total amount owed to the projected total repayment amount. The total repayment amount is calculated using the repayment amount, the repayment frequency, and the repayment period (which is from the repayment start date to the repayment end date or life expectancy date). If the amounts do not match, and the household member appears to be short in his or her repayments, then the system will initiate preprocessing for sanctions.No
Date ReceivedCURAM_DATEDate liquid resource received.Yes
End DateCURAM_DATEDate liquid resource ended.No
Change Details
LabelTypeDescriptionMandatory
Received DateCURAM_DATEThe date on which the evidence was received.Yes
Change ReasonEVIDENCE_CHANGE_REASONThe change reason helps the reason for evidence correction. No
Effective Date of ChangeCURAM_DATEDate which the evidence becomes effectiveNo
Liquid Resource Details
LabelTypeDescriptionMandatory
Liquid Resource TypeEVD_LIQUID_RESOURCE_TYPELiquid resource type from the drop-down list of liquid resource types, e.g., loans, draft account, or savings account. The liquid resource type is used to determine whether or not the resource will be countable in a resource test. The system performs special calculations for the loan and note liquid resource types in order to determine whether or not the household member is likely to pay the loan/note back in full. If the household member is not paying the loan back in full, then the system initiates preprocessing for sanctions. For more information, see the repayment field descriptions below. Your system administrator can add a new liquid resource type via the Code Tables page (see "Code Tables" in the Cúram Administration Guide).No
Savings Certificate Details
LabelTypeDescriptionMandatory
Number of UnitsEVD_NUMBER_OF_SAVINGS_CERTIFICATE_UNITSNumber of National Savings Certificate units held by the participantNo
Issue NumberEVD_SAVINGS_CERTIFICATE_ISSUE_NUMBERNational Savings Certificate Issue Number.No
Share Details
LabelTypeDescriptionMandatory
Number of SharesEVD_NUMBER_OF_SHARESNumber of shares the household member has in relation to the institution, e.g., the number of shares invested in a company institution.No
Institution Details
LabelTypeDescriptionMandatory
Institution ParticipantFULL_NAMEIf the liquid resource institution is a case participant, you can select the institution from the drop-down list of case participants. The system automatically creates an additional case participant role of institution.No
AddressADDRESS_DATAThe address of the representative. No
Phone Area CodePHONE_AREA_CODEThe area code of the representative. No
Phone NumberPHONE_NUMBERThe phone number of the representative. No
LabelTypeDescriptionMandatory
Institution ParticipantCASE_PARTICIPANT_ROLE_IDIf the institution is a case participant, you can select them from the drop-down list of case participants. The system automatically creates an additional case participant role of "Institution".No
LabelTypeDescriptionMandatory
InstitutionSERVICE_SUPPLIER_IDYou can select the institution from the organization's registered participants. To do this, press the Search button to open the Search pop-up window. On the Search pop-up window, enter some or all of the search criteria and press the Search button to search for individuals or organizations with matching details. Click the Select link on the appropriate row from the list of participants displayed to select the medical service provider.The system automatically creates an additional case participant role of "Institution".No
LabelTypeDescriptionMandatory
Institution NameFIRST_FORENAMENo
Comments
LabelTypeDescriptionMandatory
CommentsCOMMENTSNo
Links and Actions
Page Level Actions
LabelDescription
CancelGeneric help message for cancel actions
SaveGeneric help message for save actions
Messages
When page is loaded
MessageMessage CatalogConfigurableConfigurable Validation Reference ID
%1s %2sLinkNo
%1s %2s (%3n)LinkNo
%1s %2s %3sLinkNo
%1s %2s %3s (%4n)LinkNo
An Exception occurred as the timeout has been reached and the transaction has been rolled back.LinkNo
An Exception occurred as the timeout has been reached and the transaction has been rolled back.LinkNo
No security implementation is supported for this transaction type. Please contact an Administrator.LinkNo
No security implementation is supported for this transaction type. Please contact an Administrator.LinkNo
When page is submitted
MessageMessage CatalogConfigurableConfigurable Validation Reference ID
'To be' rule sets contain validation errors - cannot continue with rule set migrationLinkNo
(error accessing field - '%1s')LinkNo
%1c case type not supported.LinkNo
%1s: %2s %3s (%4n %5n) %6sLinkNo
%1s %2sLinkNo
%1s %2s (%3n)LinkNo
%1s %2s %3sLinkNo
%1s %2s %3s (%4n)LinkNo
- %1s = %2sLinkNo
%1s has evidence that is currently awaiting approval and cannot be discarded.LinkNo
A cached rule set group was not found on the database. The cache has now been cleared. Please try again.LinkNo
Ancestor attribute availability not found for current attribute availability '%1s'.LinkNo
Ancestor attribute availability not found for to-be attribute availability '%1s'.LinkNo
Ancestor rule class not found for current rule class '%1s'.LinkNo
Ancestor rule class not found for to-be rule class '%1s'.LinkNo
An effective date must be entered to indicate the date on which the existing evidence became effective.LinkNo
An effective date must be entered to indicate the date on which the existing evidence became effective.LinkNo
An Exception occurred as the timeout has been reached and the transaction has been rolled back.LinkNo
Arguments for invocation %1n:LinkNo
A row identifier cannot be null.LinkNo
As you are attempting to correct the initial record in the timeline the effective date must be blank.LinkNo
Attempt to queue evidence records without configuring deferred verification.LinkNo
A verification item cannot be added to a case with a status of closed.LinkNo
Batch result codes were:LinkNo
Business Process class %1s for product of type %2c is not assignable to type %3s.LinkNo
Current rule set details not found for rule set '%1s'.LinkNo
Current rule set not found for rule set name '%1s'.LinkNo
Details structs were:LinkNo
Error during batch database operation - check log for details.LinkNo
Error processing invocation %1n of %2n - batch result code %3n:LinkNo
Error re-validating derivation for '%1s'.LinkNo
Evidence that is currently awaiting approval cannot be discarded.LinkNo
Exception instantiating hook for product of type %1c : %2s.LinkNo
existing entry found for %1s (%2s).LinkNo
For Participant evidence a caseID or participantID must be specified.LinkNo
MESSAGE CATALOG ENTRY REQUIRED: %1sLinkNo
Multiple evidence descriptor records exist with correctionSetID '%1s' and status code '%2c'.LinkNo
New rule class not found for moved attribute '%1s' (moving to '%2s').LinkNo
New rule set not found for moved class '%1s' (moving to '%2s').LinkNo
No attribute availability storage row found for attribute availability ID %1s.LinkNo
No database access is allowed at this point.LinkNo
No row manager set which contains the optimistic lock.LinkNo
No rule attribute storage row found for rule attribute ID %1s.LinkNo
No rule class storage row found for rule class '%1s'.LinkNo
No rule class storage row found for rule class '%1s' and rule set ID %2s.LinkNo
No rule set storage row found for rule set name '%1s'.LinkNo
No security implementation is supported for this transaction type. Please contact an Administrator.LinkNo
Number of results from batch database operation (%1n) does not equal number of invocations of batch operation (%2n).LinkNo
Only records with a status of 'In Edit' can be discarded.LinkNo
Post migration rule sets contain validation errors - cannot continue with rule set migrationLinkNo
Resource '%1s' not found on classpathLinkNo
Result %1n = %2nLinkNo
Rule attribute not found for current rule available attribute '%1s'.LinkNo
Rule attribute not found for to-be rule available attribute '%1s'.LinkNo
Rule class migration pair not found for '%1s'.LinkNo
Rule set migration pair not found for '%1s'.LinkNo
Rule set not found for to-be rule set '%1s'.LinkNo
System configuration error - Unable to retrieve system user details from the database. Please contact your system administrator.LinkNo
The action cannot be performed as elements of the data were previously associated with different evidence for this client.LinkNo
The change received date cannot be later than the current date.LinkNo
The change received date must not be earlier than the received date.LinkNo
The changes that you have made may affect the verification information recorded for the following item(s): %1s. Please review this verification information.LinkNo
The class '%1s' does not implement the interface curam.util.events.impl.EventFilter and therefore is not as an event filter.LinkNo
The class '%1s' does not implement the interface curam.util.events.impl.EventHandler therefore is not an event handler.LinkNo
The Date Received that you have entered must not be later than the current date.LinkNo
The due date must be later than the current date.LinkNo
The effective dated incoming values may already exist on this case please compare against existing evidence on %1d and correct existing using incoming values if required.LinkNo
The effective date specified will not result in the existing timeline of evidence being the latest to achieve that the effective date must be after %1dLinkNo
The effective date specified will not result in the existing timeline of evidence being the latest to achieve that the effective date must be after %1dLinkNo
The effective date specified will not result in the existing timeline of evidence being the latest to achieve that the effective date must be between %1d and %2dLinkNo
The effective date specified will not result in the existing timeline of evidence being the latest to achieve that the effective date must be between %1d and %2dLinkNo
The end date cannot be before the start date.LinkNo
The event filter: '%1s' could not be instantiated.LinkNo
The event handler: '%1s' could not be instantiated.LinkNo
The evidence change type must be specified.LinkNo
The evidence type must be specified.LinkNo
The following item(s) require verification: %1s.LinkNo
The Key Server cache and the Key Server database values are out of sync and therefore this record cannot be inserted. LinkNo
The logically equivalent configuration's XML rule could not be parsed.LinkNo
The login ID %1s does not map to a user name.LinkNo
The received date cannot be later than the current date.LinkNo
The received date must be entered.LinkNo
There is more than one rule set with name '%1s'.LinkNo
The start date must be entered.LinkNo
The VerificationController class cannot be found.LinkNo
The VerificationController class cannot be instantiated.LinkNo
This attribute value has been removed.LinkNo
This evidence record cannot be discarded as it has one or more dependent records.LinkNo
To-add rule set not found for rule set name '%1s'.LinkNo
To-be rule set not found for rule set name '%1s'.LinkNo
To-remove rule set not found for rule set name '%1s'.LinkNo
You cannot modify the due date as the evidence associated with it is no longer in use.LinkNo
You do not have the necessary case security rights to perform this action. Please contact your security administrator.LinkNo
You do not have the necessary product security rights to perform this action. Please contact your security administrator.LinkNo
You may not add this item to the verification as the evidence associated with it is no longer in use.LinkNo
Workflows
When page is loaded
None
When page is submitted
WorkflowDescription
VERIFICATIONDUEDATEPROCESSINGHandles processing that occurs when evidence is added to a case that requires verification which has a deadline. This includes calculating a due date and warning date, notifying the case worker and creating a communication that can be sent to the client in advance of the deadline date, if warning days are specified, notifying the caseworker when the due date is reached, and closing the case if the due date passes without verification being satisfied.
Related Entities
Technical Information
Page IDEVD_incomingModifyLiquidResourcesEvidence
LocationC:\Users\david\dev\src\esystems-inc\Curam_V8_IS\webclient\components\Evidence\Evidence\LiquidResources\EVD_incomingModifyLiquidResourcesEvidence.uim
Page Load InterfaceEVDEvidenceMaintenance.listCaseParticipantWithoutDuplicates, EVDEvidenceMaintenance.readLiquidResourcesEvidenceForIncomingModify
Page Submit InterfaceEVDEvidenceMaintenance.incomingModifyLiquidResourcesEvidence
Linked From Pages