Description
This page allows you to modify a Alien 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
Current Alien StatusEVD_ALIEN_TYPEAlien type from the drop-down list of alien types, e.g., "parolee", "battered spouse or child", "asylee". This type determines whether or not the household member is an exempt alien. Exempt aliens do not need to meet date of entry requirements to be eligible for the Food Assistance (US) and Cash Assistance (US) programs (see the "Date of Entry" field). Your system administrator can add a new alien type via the Code Tables page (see "Code Tables" in the Cúram Administration Guide).Yes
Alien Status on EntryEVD_ALIEN_TYPEType of alien status on entry from the drop-down list of alien status on entry types, e.g., "parolee", "battered spouse or child", "asylee". Your system administrator can add a new alien status on entry type via the Code Tables page (see "Code Tables" in the Cúram Administration Guide). No
Date of EntryCURAM_DATEDate the alien household member first entered the country/region. Alien household members may be eligible or ineligible for certain programs depending on the period of time that has elapsed since their date of entry. For example, for the Cash Assistance program, an alien lawfully admitted for permanent residence on or after August 22, 1996 is ineligible for 5 years from date of entry unless an exempt alien.Yes
End DateCURAM_DATEThis is the end date of the alien record.No
Country/Region of OriginCOUNTRY_CODECountry/Region the alien household member entered the country from on the member's most recent trip out of the country from the drop-down list of countries, e.g., "Mexico", "Canada". An alien household member may leave the country several times after the date of entry and this is the country of origin for the member's most recent trip out of the country. Your system administrator can add a new country via the Code Tables page (see "Code Tables" in the Cúram Administration Guide).Yes
Country/Region of CitizenshipCOUNTRY_CODEAlien household member's country of citizenship from the drop-down list of countries, e.g., "Mexico", "Canada". Your system administrator can add a new country via the Code Tables page (see "Code Tables" in the Cúram Administration Guide).No
Country/Region of BirthCOUNTRY_CODEAlien household member's country/region of birth from the drop-down list of countries, e.g., "Puerto Rico", "Cuba". Your system administrator can add a new country via the Code Tables page (see "Code Tables" in the Cúram Administration Guide).No
Registration NumberEVD_ALIEN_REGISTRATION_NUMBERHousehold member alien registration number. This number relates to the Immigration and Naturalization Service (INS) file number.No
INS SectionEVD_INS_SECTIONINS section number that relates to the household member's immigration status. Household members who are granted asylum under certain INS section numbers are potentially eligible for food assistance and/or cash assistance benefits in the US.No
Date Last Left CountryCURAM_DATEAn alien household member may leave the country several times after the date of entry and this is the most recent date on which the member left the country.No
Date Alien Status GrantedCURAM_DATEDate on which the alien status has been granted.No
Indigent AlienCURAM_INDICATORIf the household member is an indigent alien, select the Indigent Alien selection box. An indigent alien is someone the agency has determined to be unable to obtain food and shelter, taking into account the alien's own income and resources, as well as assistance provided by other individuals including alien sponsor(s). An indigent alien is considered an exempt alien for one year after the indigence decision is made. During this year, the system does not count any resources or income from other individuals including the alien's sponsor(s) as part of the alien's household income and resource totals.No
Continuously Residing in Country since Date of EntryCURAM_INDICATORThis field indicates whether or not the household member has continuously resided in the US from their date of entry through the date they became a qualified alien.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
Alien Details
LabelTypeDescriptionMandatory
Household MemberFULL_NAMEHousehold member to whom the alien evidence applies from the drop-down list of household members. Note that this household member must have a citizen status of a type that allows the member to be recorded as an alien, e.g., "alien". Note also that the system displays the primary alternative ID of each of the members displayed on the drop-down list. In the US, the primary alternative ID is the social security number (SSN).No
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_incomingModifyAlienEvidence
LocationC:\Users\david\dev\src\esystems-inc\Curam_V8_IS\webclient\components\Evidence\Evidence\Alien\EVD_incomingModifyAlienEvidence.uim
Page Load InterfaceEVDEvidenceMaintenance.listCaseParticipantWithoutDuplicates, EVDEvidenceMaintenance.readAlienEvidenceForIncomingModify
Page Submit InterfaceEVDEvidenceMaintenance.incomingModifyAlienEvidence
Linked From Pages