Table Description |
Agreement Issue History
:
A history of the issuing of an agreement over it's life time.
An agreement can be issued once it has been completed. An agreement can be issued multiple times to any clients or signatories on the agreement. Example James Smith's strengths and needs were assessed and an outcome plan was created to address these needs. Multiple activities were added to the outcome plan. An agreement is created which ensures that James agrees to participate in all of the activities outlined in the outcome plan. The agreement is completed and issued to James for signing. This entity stores a record of issuing the agreement to James. Technical Notes The issue date field should be populated by the system using the current date on creation of an agreement issue history. The issued by field should be populated by the system using the current program user on creation of an agreement issue history. The case participant role identifier relates to the client who the agreement is being issued to. The case participant role is in relation to either a registered client or signatory of the agreement. When the agreement is issued for the first time the reason field is defaulted to initial. The issue history only holds a record of the issues for the parent agreement. It has no requirement for a status field. |
Relationship Diagram |
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions. |
|
Model Details |
Location in Model: | Logical View::MetaModel::Curam::OutcomePlanning::OutcomePlan::Entity::Delivery::Agreement::AgreementIssueHistory::AgreementIssueHistory |
Controlling File: | AssessmentPlanning\model\Packages\OutcomePlanning\Entity\Delivery\IssueHistory.efx |
Table Options |
ALLOW_OPTIMISTIC_LOCKING | no |
Attributes (8) |
|
Foreign Keys (3) |
|
Indices (3) |
|
Operations (3) |
|
Related Pages (10) |