Changelog elements-ioxml

Filter x

2021.0.0 (2021-04-23)

Added

  • Added support for createOnly FullSourceBase importing + integration with ApplicationRevision-based importing
  • ExpansionResourceImportRunner now supports expanders-maven-plugin’s experimental dependency file

Fixed

  • Fixed ExpansionResource importer crashing on unknown data loaders
  • Guard ExpansionResource importer from re-importing the same resource (and thus breaking internal links)

Updated

  • Updated prime-radiant 2020.8.4 -> 2021.1.0

2020.9.7 (2020-10-12)

Updated

  • Updated nsx-parent 2019.5 -> 2020.9.1

2020.9.6 (2020-09-29)

Fixed

  • Fixed some issues in tests with loading expansion-resource dependencies that provide data resources

2020.9.5 (2020-09-08)

  • Skipped

2020.9.4 (2020-08-20)

Updated

  • Updated nsx-shared-cli to v2020.7.2 to fix incorrect exit codes for CliParser

2020.9.3 (2020-08-19)

Fixed

  • [rmi,xml] Import/Export of ApplicationExpansionSettings now relies only on the file name (without extension) as a name
  • [rmi] Fixed clean import not always removing old applications/instances/expansionSettings
  • [xml] ExpansionSettingsTreeToXml no longer exports excludeDefaultExpanders/useComponentFile when set to false

2020.9.2 (2020-08-18)

Fixed

  • [rmi] ApplicationInstance settings (presentation, etc.) are no longer clean-imported

2020.9.1 (2020-07-08)

Fixed

  • [onionSpec] layoutStyle() spec builder can now be used as a child spec in the application() spec builder.

2020.9.0 (2020-07-07)

Removed

  • Removed foundation component
  • Removed use of custom Appender/Finalizer from custom import/export runners
  • [PR] improved import/export runners for Prime Radiant

2020.8.0 (date n/a)

Changed

  • Io-xml classes now use runtime classes of nsx-shared-xml, which have a different packageName and will not be compatible with the previous versions.
    • This should normally not be a problem except for classes where the ElementBuilder or DocumentBuilder are called directly.
  • ElementOptionConverter has been deprecated in favor of expanded option-converter classes. E.g. DataOption-converters are now registered in DataElementOptionConverter

2020.7.2 (2020-06-15)

Fixed

  • Fixed expansion resource sorting debug information not showing actual resource names/versions.

2020.7.1 (date n/a)

Merged 2020.6.3 patch into 2020.7.1 version.


2020.7.0 (2020-05-28)

Changed

  • Replaced singleDataBaseSchema with db.globalSchemas and db.global.schemaName to force global schema naming
  • Added applicationInstanceOption db.tableName.format (with lastPackage and appl4_comp4_prefix formats) to set default table naming

2020.6.3 (date n/a)

Fixed

  • PrimeDataLoader can now populate DataRegistries to prevent issues with data-resources loading in expander tests.

2020.6 (date n/a)

Added

  • ApplicationInstance option singleDataBaseSchema forces all data-elements to use a single schema defined in the option value (leave empty for default schema).
  • import/export of models for entire sourceBase

2020.5 (date n/a)

Added

  • Improved logging of imports
  • Colored log output

2020.1 (date n/a)

Added

  • Added applicationExpansionSettings.xsd

Removed

  • Removed unused anchors and customAnchors elements from expander.xsd

Changed

  • isRequired fieldOption is automatically removed for CALCULATED_FIELD fields

2019.7.8 (2019-12-16)

Added

  • Added a clear error message when a linkField targets a dataElement from a component on which there is no dependency
  • The options includeCsvImport, includeCsvExport can now be added to ApplicationInstance or Component and will be cascaded down.

2019.7.7 (2019-12-06)

Added

  • Added DataResourceLoader to support the reading of dataResources in nsx-prime (these can provide additional layers, libraries, technologies etc.)

Changed

  • [onionSpec] finder("findByNameEq") is no longer added automatically when dataOption("nameNotWanted") is defined
  • [onionSpec] Provide default globalOptionSettings, technicalInfrastructure, businessLogicSettings and presentationSettings to applicationInstance if none are defined

2019.7.6 (2019-11-21)

Added

  • Added artifactModifiers field to Expander, which can contain a map of variables that can be used in teh artifactPath/Name.

2018.06.1 (date n/a)

Added

  • <description> is always exported for elements that have such a field
  • <componentDependency>’s <dependsOn> now includes version attribute
    • if no version is specified, the old behavior is preserved
    • in elements-io the import would use the first (usually oldest) component with the given name
  • <dataFlowTask>’s states are automatically created during import when missing
  • specifying <disabled>yes</disabled> will remove the entity instead

Changed

  • all elements are sorted by id when exported
    • in elements-io it was a mixture of sort by name and sort by id
  • <valueFieldType>’s name now contains its actual name
    • previously it was fullType
    • both name and fullType are accepted for backwards compatibility
  • order of <dataElementOption>’s <value> and <dataOptionType> swapped
    • to make it consistent with other Options
  • importing layout style with empty name now uses explicit default ‘nsxbootstrap’
    • instead of random (first?) one from db
  • replaced combined access rights with separate boolean elements
    • e.g. <rights create="y" delete="y" edit="n" read="y"/> becomes <mayCreate value="true"/>, etc.
    • both formats accepted for import, but export is in new format only
  • renamed <commandAccessRight>’s <scope> attribute element to dataElement
    • e.g. <scope command="changePassword" component="account" dataElement="User"/>
    • both formats accepted for import, but export is in new format only

Removed

  • <type> is no longer exported for <field> and <connectorField>
    • the information is derivable from <valueField> and <linkField> contents
  • <status> field is no longer exported for DataElement
  • <disabled> field is no longer exported for any element, but is accepted on import