|
|
|
This section includes the issues that are fixed in CA ERwin Data Modeler release 7.3.12.
This section contains the following topics:
The following issues are fixed in release 7.3.12:
Problem No.: 100 SUPERTYPE SUBTYPE NULL OPTION
Issue No.: 20059769-1
In a specific model that was created using CA ERwin Data Modeler release 7.3.10, when the supertype subtype rollup was used, the non-key column NULL option in the subtype tables were not handled properly. Subtype non-key NOT_NULL was not displayed as NULL in the rolled-up table.
Problem No.: 10525 CC - ERWIN CRASHES
Issue No.: 18640105-1
In a specific model that was created using CA ERwin Data Modeler release 7.3.5 or 7.3.6, a Complete Compare session caused the model to crash. The target server of the model was SQL Server 2005 and the following options were selected:
Problem No.: 10593 WRONG DROP COLUMN
Issue No.: 18627485-1
When a specific model was compared with another model that was reverse-engineered from an Oracle database, filtering only on indexes and key constraints, the generated alter script included DROP COLUMN statements.
Problem No.: 10596 ADD PARTITION RANGE
Issue No.: 18741645-1, 18903579-2, 20100747-1
In CA ERwin Data Modeler release 7.3.6, if a partition was added to an existing partitioned table in a specific Oracle model, the following code was included in the ALTER script :
SQL> create table tempabc (col1 varchar2(10), col2 int )
2 partition by range (col1)
3 ( partition p1 values less than ('A%')
4 );
Table created.
SQL> alter table tempabc
2 add partition p2 values less than ('C%');
Table altered.
However, if a partition was added to an existing partitioned table, the script in the Alter Script/Schema Generation dialog included a drop and create table statement, instead of simply altering the table.
Problem No.: 10602 RE CRASH
Issue No.: 18723518-1, 19754859-1
CA ERwin Data Modeler crashed when a specific model was reverse-engineered from an Oracle database.
Problem No.: 10738 ERWIN NEEDS TO CLOSE
Issue No.: 19051753-1
In a specific model that was created using CA ERwin Data Modeler release 7.3.8, when an identifying relationship between two tables was deleted and the PK was moved to the other table, the Migration Conflict dialog appeared. When clicked OK, the application crashed.
Problem No.: 10744 CHECK MODEL ERRORS 2
Issue No.: 19072346-1
In a model that was created using CA ERwin Data Modeler release 7.3.8, when an entity was marked as Logical Only and the model was checked before forward engineering, the following error was displayed for this entity:
Table should contain at least one column in order to successfully generate. Primary key on the table has no members defined.
However, no such message was generated for other entities.
Problem No.: 10768 CC AND IGNORE CODE COMMENTS
Issue No.: 19079110-1
CA ERwin Data Modeler release 7.3.8 and 7.2.8 did not find the changes in a specific store procedure code when the Ignore code comments option was selected.
Problem No.: 10769 ORACLE.FET, FIX REQUEST
Issue No.: 19041989-1
In CA ERwin Data Modeler release 7.3.8, for an Oracle 10g model, when a Validation Rule/Check Constraint value was changed and the check constraint was associated with a column, the resultant Alter Script syntax included SQL statements to drop the constraint and then modify it. This is incorrect as the syntax should be drop and add, instead of drop and modify.
Problem No.: 10830 FOCUS PROBLEM
Issue No.: 19187714-1
In CA ERwin Data Modeler release 7.3.8 and 7.3.9, the down arrow on the keyboard did not work properly on the SQL Server Partition Tab Editor dialog.
Problem No.: 10832 RE OF PARTN INDEX INCORRECT
Issue No.: 19192162-1
In CA ERwin Data Modeler release 7.3.8, when a specific model that included a partitioned index was reverse-engineered, incorrect index members were shown. The partitioning column of the partitioning index was included as the first member of the partitioned index.
Problem No.: 10862 SYBASE - REFERENTIAL CONSTRAINT
Issue No.: 19222734-1
In CA ERwin Data Modeler release 7.3.9, a Sybase 15.x model included a table with 12 foreign keys. When a column was added to the middle of the table, the foreign keys were dropped in the ALTER script. However, the keys were not included subsequently.
Problem No.: 10880 EXTERNAL ORGANIZATION CAPTURE
Issue No.: 19248991 -1
CA ERwin Data Modeler release 7.3 did not reverse-engineer a specific model that included external sources (External Organization database).
Problem No.: 10888 CC: TRIGGERS MISMATCH
Issue No.: 19257105-1
In CA ERwin Data Modeler release 7.3.3, when a specific Logical/Physical model was compared with a database, some of the triggers were shown as not aligned, although they were aligned.
Problem No.: 10903 MISSING SP/RE FM SS 2008 DB
Issue No.: 19266419-1
In CA ERwin Data Modeler 7.3.8, when a specific model was reverse-engineered from AdventureWorks 2008 Database, one of the stored procedures was not reverse-engineered.
Problem No.: 10985 ATTRIBUTE TO COLUMN PROBLEM
19627310-1, 20095616-1, 20353336-1, 20420873-1, 20459037-1, 20462500-1, 20551142-1, 20551680-1, 20659093-1, 20844484-1
In CA ERwin Data Modeler release 7.3.9, when a naming standards file and a macro were used for name mapping, the macro did not expand properly.
Problem No.: 11085 COMMENTS IN SCRIPT GENERATION
Issue No.: 19715117-1
In CA ERwin Data Modeler release 7.3.10, for a DB2/zOS Version 8/9 model, the DDL was generated for the comments added to columns, although the Comments option was not selected in the Alter Script Schema Generation dialog.
Problem No.: 11096 CRASH CLOSING ERWIN
Issue No.: 19668378-1, 19722798-1, 19735644-1, 19853099-1, 19893324-1, 19905620-1, 20046281-1, 20100521-1, 19573063-1, 19962097-1
CA ERwin Data Modeler release 7.3.5 crashed when the application was closed.
Problem No.: 11100 SS2005 RE UDP
Issue No.: 19675013-1, 20061605-1, 20267787-1
In CA ERwin Data Modeler 7.3.10, when a specific SQL Server 2005 database was reverse-engineered, the following error message was displayed:
An unexpected condition has occurred. this condition is not inherently fatal". GDM-39, GDM-41, GDM-40, GDM-33.
This error appeared only the first time the database was reverse-engineered. Subsequent reverse-engineering processes went on without any errors. If the application was closed, reopened and then closed, the errors recurred.
Problem No.: 11120 CRASH WHEN FUNCTION IS RE'D
Issue No.: 19496235-1, 20050955-1, 20060390-1, 20116801-1, 20151662-1
In CA ERwin Data Modeler 7.3.10, when a specific SQL Server 2005 database was reverse-engineered, the application crashed when Function was selected as an object to be reverse-engineered.
Problem No.: 11148 FE SQL SYNTAX RELATIONSHIP SHOULD NOT GENERATE IN SQL SYNTAX
Issue No.: 19949054-1
In a specific model in CA ERwin Data Modeler release 7.3.10, although a relationship was set to not generate, it still appeared in Forward Engineering SQL Syntax.
Problem No.: 11162 SWITCH TRANSFORM TO SHOW SOURC
Issue No.: 19992173-1
In CA ERwin Data Modeler release 7.3.10, when supertype subtype roll down transform was performed for an entity, the application either did not respond or crashed when Show Transform Source Objects or Show Transform Target Objects was clicked.
Problem No.: 11163 VIEW SYNTAX CRRASHING ERwin
Issue No.: 19983213-1, 20416583-1
In CA ERwin Data Modeler release 7.3.10, when a specific SQL Server 2008 database or a View (SQL syntax) was reverse-engineered, the application crashed.
Problem No.: 11178 DDL SCRIPT ALTER CONSTRAINT ST
Issue No.: 19917340-1
In CA ERwin Data Modeler release 7.3.10, a specific model generated storage information on indexes on some of the ALTER TABLE statements. This happened only when the ALTER TABLE statements included addition of indexes that had a constraint state.
Problem No.: 11179 XML IMPORT FIX
Issue No.: 20063339-1
In CA ERwin Data Modeler 7.3, when sub-type super-type rollup transform was performed and source-to-target mapping was done on a model, the model became corrupted. When the model was saved as an XML file and the XML file was opened, the model was empty.
Problem No.: 11190 ADD MODEL SOURCE ERROR: GDM23
Issue No.: 19948001-1
In CA ERwin Data Modeler release 7.2, when the Add Model Source function was used on a specific model, the following error was displayed:
GDM-23 WARNING: A transaction rollback was attempted out of sequence.
Problem No.: 11241 COLUMN LOST AFTER DERIVING
Issue No.: 19973773-1
In CA ERwin Data Modeler release 7.3, when a Logical/Physical model for Oracle 10g/11g was derived from a Logical only model, some columns from the child tables were missing. This happened for all options on the Model Naming Options dialog.
Problem No.: 11248 CC CAUSES CRASH
Issue No.: 20102332-2
In CA ERwin Data Modeler release 7.3, when a specific model was compared against a blank model, the application crashed.
Problem No.: 11249 CAN'T RE VIEW PRIMARY KEYWORD
Issue No.: 20474352-1
In CA ERwin Data Modeler release 8.1, the Views in an Oracle 11g database could not be reverse-engineered, as it included the reserved word or keyword Primary without quotes.
Problem No.: 11266 LOGICAL ONLY WILL NOT UNCHECK
Issue No.: 20225656-1, 20236843-1, 20236843-2, 20254739-1
In CA ERwin Data Modeler release 7.3.10, in some of the models that were created using Teradata Database 12, when a relationship was changed from Logical Only to Logical/Physical, it did not stay Logical/Physical. When the model was saved as XML and opened again, it solved the problem, but caused other problems.
Problem No.: 11293 CRASH ON OPENING NEW MODELS
Issue No.: 20052461-1, 20261885-1, 20340854-1, 20718381-1
On a specific computer that had CA ERwin Data Modeler release 7.3.7, new models could not be created. When a new model was created, the application crashed. Existing models could be opened, but new Subject Areas could not be created in existing models.
Problem No.: 11332 MISSING TRANSFORMS IN 7.3.11
Issue No.: 20260685-1
When a specific model was upgraded to CA ERwin Data Modeler release 7.3.11, all the column-denormalization transforms were missing. The conversion log was not created.
Problem No.: 11333 MISSING TRANSFORMS ISSUE 2
Issue No.: 20260685-2
When a specific model was converted from CA ERwin Data Modeler release 7.3.6 to 7.3.11, the model did not open properly and many transforms were missing.
Problem No.: 11401 CANNOT ADD MORE ATTRIBUTES
Issue No.: 20352349-1
In CA ERwin Data Modeler release 7.3.11, for an existing Oracle 10.x/11.x model, new columns could not be added. The following error message was displayed:
ESX-174101: Column exceeds limit for table.
However, columns could be added to a new model.
Problem No.: 11405 DB2.FET inline FK generate
Issue No.: 20291170-1
In CA ERwin DM release 7.3, for a DB2 z/OS version 7 through 9 model, the FK constraints of a relationship were included in the Forward Engineering script, despite not selecting the Generate option.
Problem No.: 11420 RES ORACLE prodOptFieldDType
Issue No.: 20380093-1
In CA ERwin DM release 7.3.11, an Oracle 11g database could not be reverse-engineered if it included an external column and the access parameter for the column exceeded a certain number of characters.
Problem No.: 11424 DEFALTS LOST ON CONVERSION
Issue No.: 20378094-1, 20552287-1
When a DB2 z/OS model was converted from CA ERwin Data Modeler release 7.3.9 to 7.3.11, the default values were not retained. In addition, for some models the CCSID property was not selected for the tables.
Problem No.: 11435 ODBC.FET
Issue No.: 20387067-1
In CA ERwin Data Modeler release 8.0, when the DISTINCT clause was used for a View for an ODBC model, the Forward Engineering script included incorrect SQL.
Problem No.: 11460 CRASH AFTER SWITCH SOURCE/TARG
Issue No.: 20414253-1
When a DB2 z/OS model was converted to CA ERwin Data Modeler release 7.3.11, the transforms did not switch from the target mode to the source mode. The application crashed when the Show Source Mode icon was clicked.
Problem No.: 11461 DERIVE:LP-LO, DOMAIN CHANGE
Issue No.: 20361389-1
When a Logical Only model was derived from a specific Logical/Physical model in CA ERwin Data Modeler release 7.3.11, the domain names were changed. When this model was compared with a blank model, the following error message was displayed:
An Attempt was made to read property type 'Parent_attribute_ref' (1075849136) on object type 'Domain' (1075838983) but no association exists between the pair.
Problem No.: 11467 SWITCH TARGET/SOURCE IMPOSSIBL
Issue No.: 20414483-1
When a specific model was converted to CA ERwin Data Modeler release 7.3.11, it did not switch from Show Source to Show Target mode of transforms.
Problem No.: 11482 GDM-91 ERROR DELETING COLUMN
Issue No.: 20437174-1
In CA ERwin Data Modeler release 7.3.11, for a SQL Server 2005 or 2008 model, if the length of an attribute was set to the maximum length allowed, and later the column was deleted from the model, the GDM-91 error was displayed.
Problem No.: 9179 CONV./UPPER CASE NOT SUBJ AREA
Issue No.: 16660447-1
In AllFusion ERwin Data Modeler 7.2.5, when the tables and column names were changed from lower case to upper case in the main Subject Area, the change was not applied to other Subject Areas that included these tables and columns.
Problem No.: 1201 CAN'T EXPORT CALCULATED
Issue No.: 19515334-1, 19583692-2, 19616984-1
For a specific model in CA ERwin Data Modeler release 7.3.10, [calculated] differences could not be resolved in the Model Manager Difference Reconciliation dialog. In addition, these differences could not be imported or exported.
Problem No.: 1213 3 way merge performance
Issue No.: 19765728-1
For a specific model in a SQL Server 2008 Mart in CA ERwin Data Modeler release 7.3.10, the Conflict Resolution screen was displayed after more than 50 minutes after a user action.
Problem No.: 1217 UPG 2000 TO 2008
Issue No.: 20020824-2, 20129735-1
When the Model Manager was migrated from SQL Server 2000 to SQL Server 2005, users could log in. However, when the MM Security Manager was opened for the first time, the security profiles were deleted. Users could not log in to Model Manager.
Problem No.: 10529 PROBLEM WITH LOGICAL, PHYSICAL
Issue No.: 19168624-2, 19168624-3, 19618117-1
In CA ERwin Data Modeler 7.3, the Identifying Relationship line disappeared in the Logical model, when the Physical Only property of the relationship was selected and unselected.
Problem No.: 10529 PROBLEM WITH LOGICAL, PHYSICAL
Issue No.: 19168624-1
In CA ERwin Data Modeler 7.3, when the Logical Only property was selected for two entities, the property was applied automatically to the relationship between the entities. However, when the property was unselected for the entities, it did not change for the relationship automatically.
Problem No.: 10797 ESX-1017 on RE of Validation Rules from SQL Server 2005/2008
Issue No.: 19111099-1
In CA ERwin Data Modeler release 7.3.8, when the validation rules were reverse-engineered from a SQL Server 2005 database, the following error message was displayed:
Advisory File Created <Level=0><Information> Reverse Engineer <Level=> <Successful Transaction> Set Property: Type Object type identifier = xxxxxxxx Object id = xxx Property type identifier = xxxxxxxxxxx <Level=2><Information> ESX-1017: Valid_Value object has been deleted due to incompatibility with the
value of property Type [Validation_Rule:CK__tblAPRecu__are_L__0116BF70]
This resulted in the validation rule syntax mismatch with the SQL Server 2005 Database.
Problem No.: 10847 BAD TD PPI SYNTAX FROM RE
Issue No.: 19194992-1
For a Teradata Database 12 model, CA ERwin Data Modeler release 7.3.8 did not parse the partition expression in the partition clause properly.
Problem No.: 10855 Set Logical Data Type on REDB for L/P Models
Issue No.: 18859175-1
When a Logical/Physical model was created by reverse engineering in CA ERwin Data Modeler release 7.2, users could enter physical data type values in the logical model.
Problem No.: 11122 XFRM-POSTLOAD ERRORS IN 7.3.11
Issue No.: 19852577-1
When transforms were upgraded from an earlier version to CA ERwin Data Modeler release 7.3.11 and recreated in 7.3.11, if these transforms were saved in an earlier version and again opened in 7.3.11, the transforms included several post load processing errors.
Problem No.: 11138 REQUIRE 6.3 MITI VERSION
Issue No.: 19850995-1
An end-user was not able to download the MIMB-OEM/6.3.0.dev file from the Meta Integration FTP server while using CA ERwin Data Modeler release 7.3.
Problem No.: 11145 SHOW SOURCE/TARGET CRASHES
Issue No.: 19930130-1
When the Show Transform Source Objects icon was clicked in CA ERwin Data Modeler release 7.3, all transforms were not displayed.
Problem No.: 11146 7.2 TO 7.3 TERADATA CONVERSION
Issue No.: 19889822-1
When CA ERwin Data Modeler was upgraded from 7.2.9 to 7.3.10, for some of the Teradata models, no editor opened, except for the Column Editor.
Problem No.: 1211 7.2.8 ERW/MM MODEL GDM-41
Issue No.: 19859315-1
When a model was switched from Logical to Physical in CA ERwin Data Modeler release 7.2.8, it took a long time to load and displayed the error message, GDM-41. After the model was upgraded to CA ERwin Data Modeler release 7.3.10, the following message was displayed and the model did not open:
Upgrading transactioned metadata:(7.2 schema 12.2) to (7.3 schema 0.2) Failed.
Problem No.: 1212 MM Performance
Issue No.: 19849345-1, 19922847-1, 20258464-1, 19932844-1
When a model was upgraded from CA ERwin Data Modeler release 7.1.2 to 7.3.10, it took around 30 minutes to open. In CA ERwin Data Modeler release 7.1.2, it took only three minutes.
Problem No.: 11145 SHOW SOURCE/TARGET CRASHES
Issue No.: 19930130-1
In CA ERwin Data Modeler release 7.3.6, transforms were displayed on the Physical model, but did not display on the Logical model.
Problem No.: 11789 RE FROM ISERIES RESULTS IN MULTIPLE INDEXES
Issue No.: 20846941-1
When a DB2 iSeries database was reverse-engineered into a CA ERwin Data Modeler release 7.3.11 model, a duplicate index was created for each index.
Problem No.: 11504 ERWIN 7.3 SQL
Issue No.: 19679584-1, 20447252-1, 20728300-1, 20728300-2
When several objects were retrieved through queries in CA ERwin Data Modeler 7.3.9, the content was truncated after the first 255 characters. This happened for objects such as UDP values, stored procedures, tables and columns.
Problem No.: 10975 RE ISERIES DB HAS 2 AK INDEX WITH SAME NAME
Issue No.: 19424691-2
When a specific DB2 iSeries database was reverse-engineered into CA ERwin Data Modeler release 7.3.9, two Alternate Key (AK) indexes were created for the same index member. The original database had only one AK index for this index member.
Problem No.: 1207 COPY REPORT TO MM NOT WORKING
Issue No.: 19627483-1, 20869333-1
The Copy Report to ERwin MM option did not work in CA ERwin Data Modeler releases 7.3.8, 7.3.9, and 7.3.10.
Problem No.: 11140 INCORRECT SYNTAX NEAR PRIMARY
Issue No.: 19926320-1
In CA ERwin Data Modeler release 7.3.8, when a model was forward-engineered to SQL Server 2008, the following error message was displayed:
ALTER DATABASE dgetstats_test_v090910_Forward_Engineer MODIFY FILEGROUP PRIMARY ReadWrite [Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near the keyword 'PRIMARY'. Execution Failed!
Problem No.: 11312 GETTING ERROR OPENING ERWIN
Issue No.: 20222505-1, 20224619-1, 20266280-1, 20273873-1
When CA ERwin Data Modeler release 7.3.10 was opened, the following message was displayed:
Application error erwin.exe instruction at (ref) memory cannot be read.
Problem No.: 11053 UDD GENERATED SQL
Issue No.: 19583692-1
In CA ERwin Data Modeler release 7.3.10, when a column was attached to a domain and User Datatype was selected in the Forward Engineering Schema Generation dialog, the DDL still included the domain data type for the column instead of the column data type.
Problem No.: 11423 PROPERTY LOGICAL ONLY
Issue No.: 20362598-3, 20385431-1
In CA ERwin Data Modeler release 7.3.11, when the Logical Only check box was selected for an entity, the following message was displayed:
Entity Editor
Set Property: Is_Logical_Only
Set Property: Is_Logical_Only
Set Property: Index_Members_Order_Ref
EXC-85: Failed to set property [Index_Members_Order_Ref]
Problem No.: 11353 NO WARNING WHEN DELETE ENTITY IN ENTIRE MODEL
Issue No.: 20321366
In CA ERwin Data Modeler 7.3.10, when an entity was dragged from the Model Explorer to a Subject Area and the Delete was clicked, the entity was deleted from not just the Subject Area, but the entire model, without displaying any confirmation message.
Problem No.: 11801 FE:INDEX PHYSICAL PROP MISS
Issue No.: 20870137
When a CA ERwin Data Modeler release 7.3.11 model was forward-engineered to a Sybase Adaptive Server 12.5 or 15 database, the DDL did not include some of the properties in the SQL of index, for those indexes that had the Physical Only check box selected in the Index Editor.
Problem No.: 10718 DB2 DDL SCRIPT FORMAT/SPACING
Issue No.: 19525685-1
When a DB2 z/OS version 8 or 9 model was forward-engineered or compared in CA ERwin Data Modeler release 7.3.5 and 7.3.10, the DDL script did not include blank lines or spacing between the statements.
Issue No.: 18794987-1 CHECK CONSTRAINT
CA ERwin Data Modeler releases 7.2.8 and 7.3.7 did not recognize a leading space in a validation rule during Complete Compare. Consequently, a mismatch was displayed for these values.
Problem No.: 10020-2 CC NOGEN NOT LIMITED
Issue No.: 17998582-1
In CA ERwin Data Modeler releases 7.2 and 7.3, when a database level compare was performed with a Subject Area and a database, the Resolve Differences dialog included some ungenerated objects, although the Include Only Generated Objects check box was selected.
Problem No.: 10113-2 AK(DB)PK(MDL)SAMENAMECCIMPRTPR
Issue No.: 18120598-1
When a CA ERwin Data Modeler 7.3.2 model and a database included the same index with the same name and members, where the index in the model was a primary key and the index in the database was a unique index, if this model and the database were compared and differences resolved, duplicate indexes were found and a rolename was lost.
Problem No.: 9962-2 CONSTRAINT WONT SYNC IN CC RD
Issue No.: 17916959-1, 18640389-1, 18774366-1, 18848567-1, 18863793-1, 19099210-1
In CA ERwin Data Modeler release 7.3, when a model was compared with a database, a constraint that was shown as a difference in the Resolve Difference dialog did not synchronize with the database. However, when a physical level comparison was performed in CA ERwin Data Modeler 7.2.9, the constraint was synchronized.
Problem No.: 1245 ERWIN ABNORMAL TERMINATION
Issue No.: 20751200-1, 20788623-1
When opening a model from an Oracle Model Manager mart in CA ERwin Data Modeler releases 7.2.9 and 7.3.11, if the Windows group policy Do not keep history of recently opened documents was enabled, CA ERwin Data Modeler crashed without any error message.
Problem No.: 120824 ERWIN 7.X AND OTHER VERSIONS
Issue No.: 21096061-1
When installing CA ERwin Data Modeler release 7.0 through 7.3.11, if another version of the application (for example, 8.1 or 9.0) is present on the same computer, then the newly installed release (7.0 through 7.3.11) did not export to CA Repository XML format. The following error message was displayed:
Failed to instantiate COM component.
In addition, any Web Portal installation that harvested from CA ERwin Data Modeler release 7 through 7.3.11 files or Mart did not work on that computer.
Problem No.: 11935 PAPER SIZE CHANGE FORGOTTEN
Issue No.: 20456281-1, 20998512-1
The Print Setup dialog did not retain the changes to the Color Appearance and the Paper Size options in CA ERwin Data Modeler release 7.3.11. When the values for these fields were changed, the application reverted the values to default. These values could be changed only through the Windows Control Panel.
Problem No.: 12003 WRONG INTERNAL STATE VALURE AFTER TRANSFORM MODE SWITCH
Issue No.: 20976721-1, 21074745-1
When a specific Teradata model that was saved in the Model Manager was updated by multiple users and the users saved the model, it took a long time for the Conflict Resolution dialog to appear. Before the dialog appeared, the following message was displayed:
Could not locate the object in the Modelset in order to calculate its changed status.
Problem No.: 12003 CAN'T EXPORT INTERNAL STATE
Issue No.: 21074745-1
When a specific model was compared with a blank model and the entire model was exported to the blank model, the supertype/subtype identity transforms showed a difference for the internal state—Mode Changing. These rows could not be exported to the blank model.
| Copyright © 2013 CA. All rights reserved. |
|