Table Description |
Agreement Status History
:
A history of the status of an agreement over it's life time.
An agreement can have the following states: In-Edit: when the agreement is first created Submitted: when the case worker attempts to complete the agreement and approval is required Completed: when the case worker completes the agreement Issued: when the case worker issues the agreement to a signatory Signed: when all signatories associated with the agreement has signed it Cancelled: when the case worker cancels 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 status record of In-Edit, Completed and Issued. Technical Notes The date and userName fields should be populated by the system using the current program user and current date on creation of an agreement status history. The agreement status history only holds a record of the status changes 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::AgreementStatusHistory::AgreementStatusHistory |
Controlling File: | AssessmentPlanning\model\Packages\OutcomePlanning\Entity\Delivery\StatusHistory.efx |
Table Options |
ALLOW_OPTIMISTIC_LOCKING | no |
Attributes (5) |
|
Foreign Keys (2) |
|
Indices (2) |
|
Operations (3) |
|
Related Pages (1) |