Table Description
Issue Time Constraint: Time constraints for an issue.

Issue time constraints are added to an issue to allow for time constraints by type and for a period of days.

Example

An example of an issue time constraint is an appeal time limit; there may be a different time limit for each stage of the appeal process.
Model Details
Location in Model: Logical View::MetaModel::Curam::Core::Reference Model::Service Layer::IssueTimeConstraint::Entity::IssueTimeConstraint
Controlling File: core\model\Packages\Reference Model\Service Layer\IssueTimeConstraint\Entity\Entity_cat.efx
Table Options
ALLOW_OPTIMISTIC_LOCKINGyes
VALIDATION_EXIT_POINTyes
Attributes (6)
AttributeStereotypeNullableDescriptionDomain DefinitionCodetableDDL Type
issueTimeConstraintIDkeynoUnique reference number assigned by the system to the issue time constraint.ISSUE_TIME_CONSTRAINT_ID SVR_INT64
issueConfigurationIDdetails Unique reference number of the issue on which the time constraint has been created.ISSUE_CONFIGURATION_ID SVR_INT64
numberOfDaysdetails Time limit in days that applies to the time constraint type. For example, if the number of days is 30 and the time constraint type is First appeal, the system sets a time limit of 30 days on the First Appeal time limit for an issue.NUMBER_OF_DAYS SVR_INT32
constraintTypedetails Time constraint type, e.g., first appeal, second appeal. This is populated by the ConstraintType code table.CONSTRAINT_TYPE_CODEConstraintTypeSVR_STRING<10>
fromDatedetails Start date of the period during which the time constraint is valid.CURAM_DATE SVR_DATE
recordStatusdetails Status of the issue appeal stage record i.e. Active or Cancelled. Logical deletion supportedRECORD_STATUS_CODERecordStatusSVR_STRING<10>
Indices (1)
Index NameAttributes
IssueTimeConstraintIndex1issueConfigurationID, issueTimeConstraintID
Operations (13)
OperationStereotypeOptionsDescriptionSQL
insertinsertAUTO_ID: issueTimeConstraintID
AUTO_ID_KEY: ISSUESBO
PRE_DATA_ACCESS: yes
Standard Operation 
readread Standard Operation 
modifymodifyPRE_DATA_ACCESS: yes
Standard Operation 
searchByIssueConfigIDnsreadmultiORDER_BY: recordStatus, fromDate
Returns all time constraints associated with a specified issue type. 
countByTypeStatusnsPRE_DATA_ACCESS: yes
 		Counts the number of active issue time constraint records whose type is equal to the specified constraintType.SQL
validateModify  Validates the modified data. 
validateCancel  Validates the data which is to be cancelled. 
modifyStatusnsmodifyOPTIMISTIC_LOCKING: yes
PRE_DATA_ACCESS: yes
Changes the status of the issue time constraint record to 'canceled'. 
readVersionNonsread Returns the version number for a specified issue time constraint record. 
readRecordStatusnsread Returns the record status for a specified issue time constraint record. 
countByTypeStatusForModifynsPRE_DATA_ACCESS: yes
 		Counts the number of active issue time constraint records whose type is equal to the specified constraintType, excluding the record being modified.SQL
insertIssueTimeConstraintinsert Inserts&nbsp;issue&nbsp;time&nbsp;constraint&nbsp;record.&nbsp;This&nbsp;method&nbsp;expects&nbsp;the&nbsp;issueTimeConstraintID&nbsp;to&nbsp;be&nbsp;set.&nbsp;It&nbsp;is preferred&nbsp;to&nbsp;call&nbsp;insertIssueTimeConstraint&nbsp;method&nbsp;only&nbsp;in&nbsp;scenarios&nbsp;where&nbsp;calling&nbsp;method&nbsp;wants&nbsp;to&nbsp;set&nbsp;the&nbsp;value&nbsp;of&nbsp;primary<br /> key&nbsp;by&nbsp;itself. 
modifyIssueTimeConstraintmodifyOPTIMISTIC_LOCKING: yes
This modify operation will be called while re-applying a change set in the target system. Entity level validations that will happen during a standard modify operation will not be applicable in this case. This modify operation will update all the attributes defined for this entity.  
Related Pages (13)