Vitech Corporation CORE Workstation 6.0 Service Pack 3 Released 31 March 2010 This service pack is cummulative and includes all changes released in Service Packs 1 and 2. ______________________________________________________________________ DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK 3 Appending to output files in the reporting / scripting framework ID Number: New capability Description: Historically, opening an output file using COREscript has overwritten the content of an existing file. Content could be appended to an open file, but once the file was closed, opening the file again would overwrite content. The OpenOutputFile construct now includes an option to overwrite (the default for backwards compatibility) or append content (the new option allowing users to progressively build content, particularly useful in COREsim and utility scripts). Duplicating an element should not duplicate the PUID element ID Number: CDTS.64 Description: The PUID must be unique within a project to be useful. When duplicating an element, CORE should not duplicate the PUID attribute. Instead, it should be left blank. This allows the user or the Assign PUID script to set the PUID to a unique value. Resolution: Apply CORE 6.0 Service Pack 3. Transforming a function to an element that does not support decomposition structures can result in an import error ID Number: CDTS.66 Description: When a decomposable element which supports a structure (such as functions) is transformed to a element class that does not support structures, the structure is not properly removed from the element. The result causes an error when the project is exported and imported. Resolution: Apply CORE 6.0 Service Pack 3. Attempting to open a class ER diagram results in the error “displaySysML: not understood”. ID Number: CDTS.67 Description: With the release of CORE 6, the SysMLAlias property was added to support representing classes in a different manner for SysML diagrams. This alias was properly handled for all SysML diagrams. This change ensures that other diagrams can leverage the SysMLAlias as well. Resolution: Apply CORE 6.0 Service Pack 3. Sorting user groups by description produces inconsistent results when the description is empty. ID Number: CDTS.72 Description: Double-clicking the header in the User Group list of the administrative tools allows you to sort the list by the specific column. If the description field is empty, the sort results are inconsistent. Resolution: Apply CORE 6.0 Service Pack 3. Attempting to execute a rename project command from the recovery log results in a conflict. ID Number: CDTS.74 Description: The form of the rename project command has been revised to work in the recovery log. Recovery logs generated prior to CORE 6.0 Service Pack 3 will generate a conflict, if loaded. Recovery logs generated with Service Pack 3 or later will execute rename commands without conflict. Resolution: Apply CORE 6.0 Service Pack 3. Importing physical block diagram preferences from CORE 5.1.5 into CORE 6.0 results in a "missing required field definition" conflict. ID Number: CDTS.75 Description: With the addition of the L0 variants in CORE 6.0, a new preference was added to the user settings to specify if the user should be prompted to select the desired variant when opening the diagram. The handling of this preference in the XML import / export file has been revised to accommodate XML files generated by CORE 5.1.5. Resolution: Apply CORE 6.0 Service Pack 3. If the attribute order for a relation is lost, the attribute does not show up in the relationship tree view. ID Number: CDTS.85 Description: As relations are manipulated in the schema, CORE automatically updates the attribute order. However, if an inconsistent order is imported, the visual display in the database can be lost. With this change, CORE now validates the relationship order when shifting from schema to database mode. Resolution: Apply CORE 6.0 Service Pack 3. Importing CORE 5 users into CORE 6 can result in an error due to the renaming of the Physical Block Diagram toolbar. ID Number: CDTS.87 Description: To generically support the various block diagrams with a common toolbar, CORE 6 renamed the phyiscal block diagram toolbar to the block diagram toolbar. Importing previous user settings can maintain references to the outdated toolbar name and generate an error when viewing the physical block diagram. Resolution: Apply CORE 6.0 Service Pack 3. When running COREsim under Windows XP, if the screensaver kicks in, you receive an OS error that stops the simulator. ID Number: CDTS.88 Description: Windows XP has errors in the way graphic resources are allocated. This error is not present in Windows Vista or Windows 7. To bypass this error, service pack 3 includes special error handling code to anticipate this operating system issue. Resolution: Apply CORE 6.0 Service Pack 3. ______________________________________________________________________ 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. Loading a CBN file can generate an "id not understood" error ID Number: CDTS.62 Description: When loading a CBN file, user groups do not properly resolve the members. 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. Conflicts can occur when using the recover log to import view descriptions AR Number: CDTS.15 Description: Using the recovery log in CORE Workstation to recover view descriptions can result in conflicts reporting that a graphic object does not exist. The resulting view description is not loaded. Only the view descriptions are affected - the technical content and data is recovered correctly. 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. 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 Workstation 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.