Database Table: LifeEvent
| Life Event:
An instance of a life event.
A life event captures changes to a person's data submitted as a result of a change in their circumstances. A life event can also be triggered indirectly by another life event.
Example James Smith logs into the citizen account and selects to submit a change of address life event. James submits his new address. This entity stores the address data that has been changed. |
|
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions.
|
|
|
| Location in Model: | Logical View::MetaModel::Curam::WorkspaceServices::LifeEvents::Entity::LifeEvent |
| Controlling File: | WorkspaceServices\model\Packages\LifeEvents\Entity\LifeEvent_Entity.efx |
| ALLOW_OPTIMISTIC_LOCKING | yes |
| Attribute | Stereotype | Nullable | Description | Domain Definition | Codetable | DDL Type |
| lifeEventID | key | no | Unique identifier for a Life Event. | INTERNAL_ID | | SVR_INT64 |
| originalData | details | yes | References the root entity of a data store that holds the original data for the Life Event, i.e. the Data, if any, that already exists for this person. | INTERNAL_ID | | SVR_INT64 |
| workingData | details | yes | This attribute references the root entity of a data store that holds the working data for the Life Event, i.e. the data
that the user modifies using a Life Event Script. | INTERNAL_ID | | SVR_INT64 |
| relatedPerson | details | | Identifies the Person to whom the Life Event relates. | LIFE_EVENT_PARTICIPANT_ID | | SVR_STRING<128> |
| lifeEventContextID | details | no | Unique identifier of the context in which this life event has been submitted e.g. citizen self service, case worker application. | INTERNAL_ID | | SVR_INT64 |
| timestamp | details | | A timestamp set at the time of the submission of the Life Event. | LIFE_EVENT_DATE_TIME | | SVR_DATETIME |
| recordStatus | details | no | The status of the record, Active or Cancelled. | RECORD_STATUS_CODE | RecordStatus | SVR_STRING<10> |
| state | details | no | Describes the state of the Life Event as defined in the LifeEventState code table. | LIFE_EVENT_STATE | LifeEventState | SVR_STRING<10> |
| baselineData | details | | Stores the XML that is used to populate the datastore at the point where a life event is created. When the life event is submitted, the finished XML in the data store is compared against this baseline XML to generate a 'Difference Command' which describes all the changes that were made by the user when they entered values in the life event script. | LIFE_EVENT_XML_DATA | | SVR_STRING<100000000> |
| intakeClientID | details | yes | A Life Event can be optionally associated with a Citizen Workspace Account via this attribute. If this attribute is null, this indicates that the Life Event is associated with a Concern Role rather than a Citizen Workspace Account.
| INTAKE_CLIENT_ID | | SVR_INT64 |
| iegExecutionStateID | details | yes | Stores the IEG Execution State ID associated with the Life Event when the life event is launched. This data is needed later to launch the life event in read-only mode in the same execution that submitted it so that the internal IEG list of visited pages is the full list. | INTERNAL_ID | | SVR_INT64 |
|
| Index Name | Attributes |
| LifeEventIdx | workingData |
| relatedPersonIndex | relatedPerson |
| IND__1413170445 | intakeClientID |
| IND_53434541 | lifeEventContextID |
|
| Operation | Stereotype | Options | Description | SQL |
| insert | insert | AUTO_ID: lifeEventID
| Standard Operation | |
| read | read | | Standard Operation | |
| modify | modify | OPTIMISTIC_LOCKING: yes
| Standard Operation | |
| searchActiveByPersonAndState | readmulti | | Returns the set of active records based on the person and life event state. | |
| readByWorkingData | nsread | | Returns a record based on the working data identifier. | |
| listByPerson | readmulti | | Returns a set of records based on the related person. | |
| searchActiveByAccountAndState | readmulti | | Returns the set of active records based on the account and life event state. | |
| remove | remove | | Physically remove a Life Event. This operation should be invoked with caution - Life Events can contain data of record for a Citizen. Life Events should be removed only when they are no longer referencable.
| |
|
