Name | CluCluRelationInfo | |
---|---|---|
Usage | LuService | |
getCluCluRelation validateCluCluRelation createCluCluRelation updateCluCluRelation | ||
Type | Complex |
ShortName | Name | Type | Description | Cardinality | XML Attribute? |
---|---|---|---|---|---|
cluId | ??? | String | Unique identifier for a Canonical Learning Unit (CLU). | One | No |
relatedCluId | ??? | String | Unique identifier for a Canonical Learning Unit (CLU). | One | No |
isCluRelationRequired | ??? | Boolean | Indicates if the relation is required upon instantiation of a LUI. Default is "true". |
One | No |
effectiveDate | ??? | Date | Date and time that this CLU to CLU relationship became effective. This is a similar concept to the effective date on enumerated values. When an expiration date has been specified, this field must be less than or equal to the expiration date. |
One | No |
expirationDate | ??? | Date | Date and time that this CLU to CLU relationship expires. This is a similar concept to the expiration date on enumerated values. If specified, this should be greater than or equal to the effective date. If this field is not specified, then no expiration date has been currently defined and should automatically be considered greater than the effective date. |
One | No |
attributes | ??? | Map |
List of key/value pairs, typically used for dynamic attributes. | One | No |
metaInfo | ??? | org.kuali.student.core.dto.MetaInfo | Create and last update info for the structure. This is optional and treated as read only since the data is set by the internals of the service during maintenance operations. |
One | No |
type | ??? | String | Unique identifier for the LU to LU relation type. | One | Yes |
state | ??? | String | Identifier for the current status of a CLU to CLU relationship. The values for this field are constrained to those in the luLuRelationState enumeration. A separate setup operation does not exist for retrieval of the meta data around this value. |
One | Yes |
id | ??? | String | Unique identifier for a CLU to CLU relationship. This is optional, due to the identifier being set at the time of creation. Once the relation has been created, this should be seen as required. |
One | Yes |