Attribute | Schema Type or Enumeration | Usage | Definition | Business |
---|
Rules Jira |
---|
server | Issue Tracker (JIRA) |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
---|
key | ODM-25 |
---|
Reference to the StudyEventDef. The StudyEventOID and StudyEventRepeatKey are used together to identify a particular study event. This pair of values uniquely identifies a StudyEvent within the containing subject. The StudyEventRepeatKey is present if and only if the StudyEventDef is repeating. | - Must match a StudyEventGroupDef/@OID or StudyEventDef/@OID for the MetaDataVersion /@OID value that matches the ClinicalData/@MetaDataVersionOID attribute.
|
StudyEventRepeatKey | repeatKey | Conditional | A key used to distinguish between repeats of the same type of study event for a single subject. | - If the StudyEventDef/@Repeating attribute has the value "Yes
|
. and When - " and there is more than one ClinicalData/SubjectData/StudyEventData/@OID element, the StudyEventRepeatKey attribute must be provided.
- Must be unique among the set of ClinicalData/SubjectData/StudyEventData/@OID elements.
- The StudyEventRepeatKey must be present only when the StudyEventDef/@Repeating attribute has the value "Yes".
|
TransactionType | (Insert | Update | Remove | Upsert | Context) | Conditional |
Identifies the transaction type when /ODM/@FileType is Transactional and there is no child element. | - Required when contained within an ODM Transactional file and the StudyEventData element has no child element content the TransactionType must be specified.
| Identifies the transaction type when /ODM/@FileType is Transactional and there is no child element. | - When importing data from an ODM Snapshot file, the TransactionType attribute must not affect the processing of any of the StudyEvent child elements.
|