Vitech Corporation CORE Enterprise 6.0 Client Service Pack 2 Released 15 February 2010 This service pack is cummulative and includes all changes released in Service Pack 1. ______________________________________________________________________ DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK 2 Recovery log generates errors when recovering new diagram objects ID Number: CDTS.15 Description: When using the recovery log with CORE Workstation, attempting to recover diagram view descriptions with new diagram objects (new connectors on the Interface Block Diagram or relationship fields on icons) generates a conflict message. These view descriptions fail to load. Resolution: Apply CORE 6.0 Service Pack 2. Help commands do not open help file ID Number: CDTS.22 Description: The links to access online help file from the help menu do not open the help file. However, the online help can be opened by double-clicking the help file in the Windows Explorer. Resolution: Apply CORE 6.0 Service Pack 2. Rotating resizes labels on block diagrams ID Number: CDTS.49 Description: When rotating a label on a block diagra, the label resizes resulting in "..." being displayed instead of the label text. The user then must manually resize the label. Resolution: Apply CORE 6.0 Service Pack 2. Incorrect icon on Interface Block Diagram ID Number: CDTS.50 Description: The icon in the upper right corner of the Interface Block Diagram is the CORE icon instead of the diagram icon. Resolution: Apply CORE 6.0 Service Pack 2. Tunneled boundary labels overwrite one another ID Number: CDTS.51 Description: Tunneled boundary labels on the IDEF0 overwrite one another rather than spacing out along the side of the diagram. This only occurs with tunneled labels, not other boundary labels. Resolution: Apply CORE 6.0 Service Pack 2. Boundary outputs overwrite IDEF0 frame block ID Number: CDTS.52 Description: If the diagram options are set to show the frame, labels for boundary outputs can overwrite the diagram frame. Resolution: Apply CORE 6.0 Service Pack 2. Renaming a connection on a block diagram recomputes the diagram size ID Number: CDTS.55 Description: Renaming a link on the Physical Block Diagram causes the diagram to recompute its size. The result can be inconsistent with the size required. Closing and reopening the diagram correctly sizes the diagram. Resolution: Apply CORE 6.0 Service Pack 2. API fails when returning large data sets ID Number: CDTS.58 Description: The CORE API fails to transport a folder with more than 800 elements from the API server to the client. The socket fails to flush appropriately and hangs. Resolution: Apply CORE 6.0 Service Pack 2. Quick filter GUI does not update correctly ID Number: CDTS.59 Description: When selecting a saved filter from the drop-down in the Edit Filter Dialog, the individual rows do not consistently update correctly. The filter is not impacted, but the display is misleading. Resolution: Apply CORE 6.0 Service Pack 2. Extracting versioned attributes in Enterprise results in an error ID Number: CDTS.57 Description: In Enterprise, using the Element Extractor to extract a value into a versioned attribute (a Function description for example) results in a "gsiClassGeneration failed" error. Resolution: Apply CORE 6.0 Service Pack 2. ______________________________________________________________________ DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK 1 Incorrect nested coloring on Sequence Diagrams ID Number: CDTS.7 Description: The ALT and PAR constructs on the Sequence Diagram do not properly inherit the coloring of the parent constructs. Resolution: Apply CORE 6.0 Service Pack 1. Error deleting icon template fields after the saved template has been deleted AR Number: CDTS.8 Description: From the icon template editor (either in User Preferences or in diagram settings), select a saved template. Add a field to the icon and then delete the saved template. Deleting the added field results in an error. Resolution: Apply CORE 6.0 Service Pack 1. COREsim Guide is not included on the Help>>Documentation menu AR Number: CDTS.10 Description: Though the COREsim Guide is present on the Windows Start menu, it is not shown in the CORE Help>>Documentation menu. Resolution: Apply CORE 6.0 Service Pack 1. Component icon profiles on Sequence Diagrams are not properly exported AR Number: CDTS.11 Description: The Sequence Diagram contains separate icon profiles for the functions and the components. Changes to the function profile (icon sizing, etc) are properly exported. Exporting a stored view description in which the component icon profile has been changed results in an error. Resolution: Apply CORE 6.0 Service Pack 1. Initial window frames on new CORE 6 diargams are too small AR Number: CDTS.12 Description: The initial window frame for the Interface Block Diagram, Activity Diagram, Requirements Diagram, and Sequence Diagram are too small. However, once one of the diagrams is opened and closed, the frame is properly stored. Resolution: Apply CORE 6.0 Service Pack 1. Hangul characters with low unicode values abort the XML export AR Number: CDTS.13 Description: If a description includes a character with a low Unicode value (31 or below), exporting to XML results in a warning that aborts the export. This case can occur when Hangul is used. Resolution: Apply CORE 6.0 Service Pack 1. XML representations of filters include unnecessary fields AR Number: CDTS.14 Description: XML exports of filters include invalid properties. This does not result in an error but clutters the XML. Resolution: Apply CORE 6.0 Service Pack 1. Sample files do not have versioning enabled AR Number: CDTS.18 Description: When importing a CORE 6 sample file, the file does not have versioning enabled by default. Though versioning can then be toggled on at the project level, it would be more convenient if the sample file enabled versioning by default. Resolution: Apply CORE 6.0 Service Pack 1. Importing relationships can bypass the limitation on maximum targets AR Number: CDTS.21 Description: If a relation is marked as limited (only permitting a maximum number of targets), importing more targets than allowed results in a conflict that the relationship could not be added. However, the relationship is added and the target limitation is exceeded. Resolution: Apply CORE 6.0 Service Pack 1. Help file not accessible from the Help menu AR Number: CDTS.22 Description: Though the online help can be opened by double-clicking the file directly, using the command on the Help menu does nothing. Resolution: Apply CORE 6.0 Service Pack 1. Cannot save diagrams in SVG format AR Number: CDTS.23 Description: Attempting to save any diagram to SVG format causes CORE to hang. Resolution: Apply CORE 6.0 Service Pack 1. Entering time values with a closing colon results in an error AR Number: CDTS.23 Description: When dealing with an attribute of type time, entering a value where the last character is a colon results in a "do: not understood:" error message on the screen. For example, entering "4:" will trigger an error. However, entering "4:00" (or "4:0") works correctly. Resolution: Apply CORE 6.0 Service Pack 1. Importing an XML file with only schema and folders can result in a conflict AR Number: CDTS.27 Description: If you import a database from an XML file and choose "schema and folders only" from the import wizard does not properly import the schema and shift back to database mode. This can result in conflicts if some of the folders are defined for newly created classes. Resolution: Apply CORE 6.0 Service Pack 1. Sequence Diagram algorithm does not always sequence functions based upon triggering AR Number: CDTS.28 Description: Though the sequencing of function nodes on a given lifeline are correct, the Sequence Diagram does not consistently use triggering to order nodes within a parallel construct. This results in triggers being drawn upward when they do in fact move downward with time. Resolution: Apply CORE 6.0 Service Pack 1. (NOTE: CORE computes Sequence Diagrams from the underlying behavior. While triggers control sequencing between branches in a parallel construct, sequencing order within a given branch must be preserved. As a result, it is possible to draw a Sequence Diagram in which the trigger moves upward [back in time]. This is a valuable diagnostic indicating a potential problem in the system model.) Diagram node positions revert when adjusting diagram scale with the mouse wheel AR Number: CDTS.32 Description: Though the online help can be opened by double-clicking the file directly, using the command on the Help menu does nothing. Resolution: Apply CORE 6.0 Service Pack 1. Renaming relationship attributes can result in a conflict on import AR Number: CDTS.33 Description: Create a relationship attribute and then rename the attribute. Next export the schema and import it into a new project. Upon import, a conflict indicates that the relationship attribute does not exist (though it is successfully imported from the relationship complement). Resolution: Apply CORE 6.0 Service Pack 1. Item icon size field not properly populated on Activity Diagrams AR Number: CDTS.35 Description: Change the item icon size in the diagram options for an Activity Diagram. Close the options dialog and the new icon size is properly applied. However, reopening the diagram options shows the default item icon sizing instead of the new icon sizing. Resolution: Apply CORE 6.0 Service Pack 1. Cannot resize external icon nodes on a Physical Block Diagram AR Number: CDTS.37 Description: Though nodes representing external systems on a Physical Block Diagram show the resize handle in the lower-right, dragging the handle does not resize the node. Resolution: Apply CORE 6.0 Service Pack 1. Importing an RDT file into CORE Enterprise results in an error AR Number: CDTS.38 Description: Using a CSV parser to generate an RDT file and importing the file into CORE Enterprise results in an error. The error only occurs when attempting to load a rich text field (such as a description). XML files import correctly. Resolution: Apply CORE 6.0 Service Pack 1. Editing node templates with no projects open AR Number: CDTS.44 Description: Editing a node template in the User Preferences when no project is open open results in an error. Resolution: Apply CORE 6.0 Service Pack 1. ______________________________________________________________________ VITECH CORPORATION SUPPLEMENTAL END USER LICENSE AGREEMENT This service pack and the documentation updates, supplements, or replaces functionality of the CORE Enterprise 6.0 software. As such, the service pack and its documentation are governed under the terms of the original license agreement. By installing this software, you acknowledge and agree to be bound by the terms of the existing license agreement. If you do not agree to the terms, promptly return the service pack and its documentation to the place you obtained them.