New bug: Phase field is ignored in transformations

[Oliver F.]

Whatever is defined in a transformation template as phase for an element, it is ignored in the transformed element created. Instead the default value from the global EA settings is used.

The following transformation log shows the correct setting of the phase property generated by the template through %TRANSFORM_CURRENT()%:

Code: [Select]

Class
    {
       notes="VDV/GDM adaptation table for creating the indices of the 'Fahrt' tables."
      scope="Public"
      multiplicity=""
      language="Oracle"
      author="uidm5336"
      alias="AdapFahrt"
      name="AdapTrip"
      complexity="1"
      stereotype="business type"
      concurrency=""
      persistence=""
      arguments=""
      phase="1.0"
      status="Proposed"
      visibility=""
      cardinality=""
  
      language="SQL"
      filename="%GDM_EXPORT%\SysTable.sql"
      name="AdapFahrt"
  
      version="98"
}
If phase has a different default value than 1.0 all elements created by the transformation will have the default value instead of the one seen in the transformation log.
This does not apply for the version field.