Table Description
Concern Case Role: The role or roles that a concern plays in a case throughout the lifetime of the case.

A concern can have multiple case roles in a case or different roles in different cases. A case may have one or more concern case roles.

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 case participant role.

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::Case::Entity Objects::ConcernCaseRole::ConcernCaseRole
Controlling File: core\model\Packages\Case\Concern Case Role_cat.efx
Table Options
ALLOW_OPTIMISTIC_LOCKINGyes
Attributes (9)
AttributeStereotypeNullableDescriptionDomain DefinitionCodetableDDL Type
concernCaseRoleIDkeynoUnique reference number assigned by the systemCONCERN_CASE_ROLE_ID SVR_INT64
concernRoleIDdetailsnoConcernRoleID of the ConcernRole in respect of which this concernCaseRole was enteredCONCERN_ROLE_ID SVR_INT64
caseIDdetailsnoCaseID of the CaseHeader in respect of which this ConcernCaseRole was enteredCASE_ID SVR_INT64
statusCodedetails Code value to denote the status of the Concern Case RoleCASE_ROLE_CLIENT_STATUS_CODECaseRoleClientStatusSVR_STRING<10>
startDatedetails Commencement Date of Concern Case Role.CURAM_DATE SVR_DATE
endDatedetails Expiry Date of Concern Case Role.CURAM_DATE SVR_DATE
typeCodedetails Code value to indicate the type of Concern Case Role. This is populated using the ConcernCaseRoleType code table.CONCERN_CASE_ROLE_TYPE_CODEConcernCaseRoleTypeSVR_STRING<10>
commentsdetails Free text registered by the User.COMMENTS SVR_STRING<300>
recordStatusdetails record status from the code table RecordStatusRECORD_STATUS_CODERecordStatusSVR_STRING<10>
Foreign Keys (2)
ChildParent
ConcernCaseRole.caseIDCaseHeader.caseID
ConcernCaseRole.concernRoleIDConcernRole.concernRoleID
Indices (5)
Index NameAttributes
ConcernCaseRoleIndcaseID
ConcernRoleIdxconcernRoleID
IND_356268544typeCode
IND__1431234340recordStatus
IND_910021752statusCode
Operations (16)
OperationStereotypeOptionsDescriptionSQL
insertinsert Standard Operation 
modifymodifyOPTIMISTIC_LOCKING: yes
Standard Operation 
readread Standard Operation 
searchByConcernRolereadmulti Returns all ConcernCase Roles for a particular concern role ID. 
countCasesns Returns the number of cases of the specified status for the specified concern.SQL
searchByCaseIDnsreadmulti Returns all ConcernCase Roles that match the caseID 
searchByCaseIDWithDateAndStatusnsreadmultiORDER_BY: caseID,concernRoleID
Returns all concern case roles that match the caseID and returns extra date fields and status fields to the previous readmulti. 
searchByConcernRoleAndCasereadmulti Returns all ConcernCase Roles read by caseID and concernRoleID 
readByTypeandCaseIDnsread Returns all ConcernCase Roles by Type and CaseID 
modifyByCaseIDAndStatusnsmodifyOPTIMISTIC_LOCKING: yes
This method updates the Concern Case Roles for a given case, of a given status. To have a new status and set the end date. 
searchActiveICClientsnsmulti returns the list of currently active clients for an Integrated case.SQL
searchForDupConcernCaseRolesnsmulti searches for duplicate concerns on the sSQL
modifyAllStartDatesByCaseIDandStatusnsmodifyOPTIMISTIC_LOCKING: yes
This method updates the Concern Case Roles start dates for a given case, of a given status. 
removeremove Standard Operation 
readByCaseIDConcernRoleIDStatusnsread Read to see if a Concern is already an active ConcernCaseRole on a specific case. 
readCaseIDAndParticipantSensitivityns Retrieves the case id and sensitivity of the participant related to this concern case role.SQL
Related Pages (0)