 glajarige
|
da0260c569
N°653 Lifecycle flags can be defined on both states and transitions (Note: This is a beta version and need to be tested!)
|
hace 8 años |
 dflaven
|
a41a646c75
XML format 1.4, introducing the new "force" flag.
|
hace 8 años |
 romainq
|
de3826039a
ImageAttribute: only in XML version 1.3
|
hace 9 años |
|
romainq
|
6fd631a0b5
Model factory: handle the flag 'if_exists' when transforming XML from version 1.3 to older versions
|
hace 9 años |
|
romainq
|
9ea355a840
CustomFields: Attributes of type CustomFields must be removed when converting from 1.3 to 1.2
|
hace 9 años |
|
romainq
|
7f46108d88
New type of attribute: AttributeMetaEnum.
|
hace 9 años |
|
romainq
|
7eb1370be9
Core: a module can have its own design defined in XML (/itop_design/modules_designs/module_design) and accessed at run time via the class ModuleDesign. Switching to XML version 1.3.
|
hace 9 años |
|
romainq
|
bd03d15b7b
XML Modelization of the relations: updated the conversion from 1.2 to 1.1
|
hace 10 años |
|
romainq
|
6d07d14345
XML 1.2: handle the XML transformation. Added APIs to report the functionality loss when downgrading (snippets, portal, module parameters, relations and object key)
|
hace 10 años |
|
romainq
|
ed43485fa5
OQL enhancement: allow JOIN on a objclass/objkey pair of attributes (requires benchmarking)
|
hace 10 años |
|
romainq
|
26745c2b33
XML format conversion utilities: no version means '1.0'
|
hace 10 años |
|
romainq
|
53614d0a8b
XML format conversion utilities: reworked the API to implement a CheckConvert and handle any kind of upgrade/downgrade (easy way to add a new format like 1.2)
|
hace 10 años |
|
dflaven
|
43d2e5470a
Split in a separate "tool" class the upgrade of the format of the datamodel from 1.0 to 1.1.
|
hace 10 años |
