Issues
- OPT export remoces terminologies from coded textTDPR-18
- Can't specify Valueset (Terminology) value in TDTDPR-17
- Constraint references mix types and do not export correspondent definitions on OPTTDPR-16
- Template name doesn't allow special characters used in other languagesTDPR-15
- not all archetype constraint bindings are being exported in OPTsTDPR-14
- Allow to specify 0..0 occurrences for SLOT nodesTDPR-13
- Codes got removed when exporting OPT for TEXT/CODED TEXT node when TEXT is removedTDPR-12
- TD doesn't save annotation set on cluster node that is placed inside a slotTDPR-11Resolved issue: TDPR-11
- Units file doesn't load on startupTDPR-10
- Term definitions code gets wrong value in opt when a URI is enteredTDPR-9
- Term definitions code clash in optTDPR-8Heath Frankel
- Error ValueSet Template DesignerTDPR-7Resolved issue: TDPR-7
- error export TemplateDesignerTDPR-6Heath Frankel
- Allow to set DV_CODED_TEXT to a DV_TEXT nodeTDPR-5Heath Frankel
- Missing datatype namesTDPR-4Heath Frankel
- Allow to set occurrence 0..0 to slotsTDPR-3Peter Gummer
- TD seems to export OPTs with BOM that migth break some parsersTDPR-2Heath Frankel
- OET namespaceTDPR-1Resolved issue: TDPR-1Heath Frankel
1-18 of 18
1 of 18