Name | meetingScheduleInfo |
---|---|
Label | Meeting Schedule |
JSTL Key | MeetingScheduleInfo |
Java Class | org.kuali.student.r2.common.dto.MeetingScheduleInfo |
Description | Captures space and time information associated with a meeting or event. |
Primary Key(s) | id |
Field to use as the title (or name) | null |
Field | Required? | DataType | Length | Short Label | Summary | Label | Description | Read Only, Dynamic, or Hidden | Default | Repeats? | Valid Characters | Lookup | Cross Field | Default Control |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
id | STRING | 1 to 36 | ID | Unique ID assigned to this object | Identifier | The system assigned unique id used to identify this Object. Could be implemented as as sequence number or as a UUID. |
validation.validChars [A-Za-z0-9.,><_\\/\-\?\+=()\[\];:'"&%$#@!\t ]* |
TextControl | ||||||
spaceId | STRING | 1 to 255 | Space Id | Space code where the meeting is going to take place | Space Code | Space code where the meeting is going to take place |
validation.validChars [A-Za-z0-9.,><_\\/\-\?\+=()\[\];:'"&%$#@!\t ]* |
TextControl | ||||||
timePeriods | STRING | 1 to 255 | Time Periods | Date and Time The date and time values for all vCalendar properties are formatted as a string consistent with the ISO 8601 representation for combinations of dates and times. | Time |
Date and Time The date and time values for all vCalendar properties are
formatted as a string consistent with the ISO 8601 representation for
combinations of dates and times. Either the basic or extended format is
allowed. The use of UTC, rather than local time, should be used when ever
possible in order to avoid time zone ambiguities. The format for the
complete, basic representation of a date and time value is written in the
following sequence of characters:
|
validation.validChars [A-Za-z0-9.,><_\\/\-\?\+=()\[\];:'"&%$#@!\t ]* |
TextControl |