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_LOCKINGno
Attributes (8)
AttributeStereotypeNullableDescriptionDomain DefinitionCodetableDDL Type
agreementIssueHistoryIDkeynoUnique identifier of the issue historyINTERNAL_ID SVR_INT64
issueDatedetailsnoThe date the agreement was issuedCURAM_DATETIME SVR_DATETIME
agreementIDdetailsnoThe unique identifier of the agreement this Agreement Issue History is part ofINTERNAL_ID SVR_INT64
caseParticipantRoleIDdetailsnoThe unique identifier of the case participant role relating to either the client or signatory to whom the agreement is being issuedCASE_PARTICIPANT_ROLE_ID SVR_INT64
issuedBydetailsnoThe name of the user who issued the agreementUSER_NAME SVR_STRING<64>
issuedTodetailsnoThe unique identifier of the address where the agreement was issued to. That is, an email or an address identifier.INTERNAL_ID SVR_INT64
issuedToTypedetailsnoThe type of address where the agreement is being issued to. For example, email.AGREEMENT_ISSUED_TO_TYPEAgreementIssuedToTypeSVR_STRING<10>
reasondetailsnoThe reason for issuing the agreement. When the agreement is initially issued this is defaulted to InitialAGREEMENT_ISSUE_REASON SVR_STRING<2000>
Foreign Keys (3)
ChildParent
AgreementIssueHistory.agreementIDAgreement.agreementID
AgreementIssueHistory.caseParticipantRoleIDCaseParticipantRole.caseParticipantRoleID
AgreementIssueHistory.issuedByUsers.userName
Indices (3)
Index NameAttributes
IND__1689005077agreementID
IND_1766992794caseParticipantRoleID
IND__1122836772issuedBy
Operations (3)
OperationStereotypeOptionsDescriptionSQL
insertinsertAUTO_ID: agreementIssueHistoryID
Standard Operation 
searchByAgreementreadmultiORDER_BY: issueDate
Returns a list of Issue History records for the agreement. The list is ordered by the issue date. 
readread Standard Operation 
Related Pages (10)