Table Description
Diary: A list of dates and events that affect the system (either at organization, division or user level).

Technical Notes

Please Note: This entity is no longer part of the default flow in the Curam Application, as such it is neither written to nor read from by the Curam Application. It continues to be shipped with the Curam model as customer may have custom logic which uses this entity, however it should be noted that if you are implementing custom logic which references this entity then you must also ensure that it is written to as needed. The information that was originally stored in this entity is now stored in calendar.
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::Core::Reference Model::Organisation::Entity Objects::Diary::Diary
Controlling File: core\model\Packages\Organisation\Diary_cat.efx
Table Options
ALLOW_OPTIMISTIC_LOCKINGyes
Attributes (11)
AttributeStereotypeNullableDescriptionDomain DefinitionCodetableDDL Type
eventIDkeynoUnique reference number assigned by the system to an Event record.DIARY_EVENT_ID SVR_INT64
fromDateTimedetails The start time and date of the event.CURAM_DATE SVR_DATE
toDateTimedetails The finishing time and date of the event.CURAM_DATE SVR_DATE
locationdetails Free text describing where the event is taking place.LOCATION SVR_STRING<60>
typeCodedetails Code value to indicate the type of event.DIARY_EVENT_TYPE_CODEDiaryEventTypeSVR_STRING<10>
descriptiondetails Free text describing the event type.DESCRIPTION SVR_STRING<300>
statusCodedetails Code table code describing the record status of the diary record.RECORD_STATUS_CODERecordStatusSVR_STRING<10>
ownerIDdetailsnoThe User ID of the User who is the Owner of the Event.USER_NAME SVR_STRING<64>
caseIDdetailsyesUnique reference number assigned by the system to a Case record.CASE_ID SVR_INT64
ticketIDdetailsyesUnique reference number assigned by the system to a Ticket record generated following a direct or indirect query in relation to a Concern or ProspectTICKET_ID SVR_INT64
creatorIDdetailsnoThe User ID of the User who creates the diary event on the system.USER_NAME SVR_STRING<64>
Foreign Keys (3)
ChildParent
Diary.caseIDCaseHeader.caseID
Diary.ownerIDUsers.userName
Diary.creatorIDUsers.userName
Indices (3)
Index NameAttributes
IND_480588903caseID
IND_403759730ownerID
IND_2047454379creatorID
Operations (3)
OperationStereotypeOptionsDescriptionSQL
insertinsert Standard Operation 
modifymodifyOPTIMISTIC_LOCKING: yes
Standard Operation 
readread Standard Operation 
Related Pages (0)