Vitech Corporation CORE Workstation 5.1 Service Pack 3 Released 31 August 2007 This service pack includes all changes from Service Pack 2. ______________________________________________________________________ DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK 3 Error importing stored physical hierarchy view description from XML AR Number: CR.1493 Description: Create and open a Physical Hierarchy diagram in which Component_001 is built from Component_002, which is built from Component_003. Move one of the nodes in the diagram and then select View >> Diagram >> Save View Settings Now. Then delete Component_002 from the database. Finally, export the project (with Stored Views) to XML. Importing it into a new project generates an error message that says "'relationshipFor:target:' not understood" Resolution: Apply CORE 5.1 Service Pack 3. Error exporting to CORE 4.0 format after deleting user AR Number: CR.1494 Description: Launch a virgin CORE Workstation image. Log in as Administrator. Open Administrative Tools and create a new user. Open the Default project. Create a new element in the project. Edit the permissions of the new element and add the new user to its access control list. Delete the new user that was just created. Export the project in CORE 4.0 RDT format. The error message says, "A serious error occurred during the export. . . . system primitive failed . . . The export process has been aborted." Resolution: Apply CORE 5.1 Service Pack 3. Delay opening XML Import Wizard AR Number: CR.1495 Description: When importing from XML, CORE is very slow to open the XML Import Wizard. When attempting to import a large XML file, CORE may actually run out of memory. Resolution: Apply CORE 5.1 Service Pack 3. Incorrect handling of element name conflicts during incremental XML imports AR Number: CR.1496 Description: In CORE 5.1 SP2, create an element named Component_001 in class Component. Export the project baseline to XML. Erase project history. Create additional elements Component_002 and Component_003 such that Component_002 is "built from" Component_003. Export project changes to XML. Import the project baseline into a new project. (Have the importer create the project.) Create an element named Component_002 in class Component within the new project. Import the project changes into the new project. The import should log a name conflict, create $0 Component_002 and relate Component_003 to $0 Component_002. Instead, it logs a different name conflict, fails to create $0 Component_002, and fails to create any relationship from Component_003. Resolution: Apply CORE 5.1 Service Pack 3. (Note: This problem only occurs in projects created by the importer, not in projects that are manually created prior to the import.) There are no privilege constraints on the import of users and groups AR Number: CR.1497 Description: It is possible to promote the privileges of users and groups via XML import even if the user performing the import does have the appropriate privileges. Resolution: Apply CORE 5.1 Service Pack 3. Find operation does not find search string in element names AR Number: CR.1498 Description: If a 'Find' operation is performed on a project, folder, or element, the inspector window will open properly if the search string matches the name of an element exactly. Error launching saved image AR Number: WS.21 Description: An error launching a saved CORE Workstation image can be produced as follows: 1) User opens element grid view. 2) Grid view causes element index to be built. 3) User saves image. 4) User exits CORE. 5) User waits a sufficiently long time. 6) Index becomes defunct because of its age. 7) User launches saved image. 8) CORE releases defunct index. 9) Grid view causes CORE to rebuild index. 10) Rebuilding of index causes grid view to be refreshed. 11) Error occurs refreshing grid view because it has not yet been reopened. Resolution: Apply CORE Workstation 5.1 Service Pack 3. ______________________________________________________________________ DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK 2 SVG output AR Number: New capability Description: It is now possible to save diagrams in .SVG (Scalable Vector Graphics) format. Diagrams in this format can be imported into Visio for further manipulation. Resolution: Apply CORE 5.1 Service Pack 2. New persistent data format for Workstation AR Number: New capability Description: The File menu in CORE Workstation now contains "Save Database" and "Load Database" commands to allow image data to be written to and read from .CBN object files. Resolution: Apply CORE 5.1 Service Pack 2. Loading a .CBN file (after prompting) replaces all projects in the image with those in the file. A .CBN file also contains users and groups. The .ACF files in the target environment are merged into those in the .CBN file (but the Administrator password specified in the .CBN file is maintained). The current user is logged out when a .CBN file is loaded. Updated Interface Hierarchy definition AR Number: Enhancement Description: The "transfers" relation has been added to the definition of the Interface Hierarchy diagram. Resolution: Apply CORE 5.1 Service Pack 2. Enhanced Project Property Query AR Number: Enhancement Description: The following properties have been added to the Project Property Query script construct: "basePath", "schemaBaselineName", and "schemaVersion". Resolution: Apply CORE 5.1 Service Pack 2. Default hierarchy definitions assigned to classes AR Number: Enhancement Description: Default hierarchy diagram definitions have been assigned to the following classes: Item (Function hier), Needline (Interface hier), OperationalActivity (Function hier), OperationalInformation (Function hier), OperationalNode (Physical hier), Product (Function hier), and ProgramActivity (Function hier). Resolution: Apply CORE 5.1 Service Pack 2. OV-3 enhancement AR Number: Enhancement Description: Added search for source OperationalActivity based on 'input to' in addition to 'triggers' relationships. Added a warning message when an OperationalActivity both triggers and is input to the same OperationalActivity. Resolution: Apply CORE 5.1 Service Pack 2. The same goes for Functions and Items in the SV-6. HTML Report enhancement AR Number: Enhancement Description: Added the option to include Functional and Physical Hierarchy Diagrams in output pages. Added the element Description to the hotspot tip text in diagrams. Output all diagrams in uniform size. Resolution: Apply CORE 5.1 Service Pack 2. The same goes for the Bookmarked HTML Report. SDD enhancement AR Number: Enhancement Description: Separated Section 5, Issues & Decisions, into multiple parts based on the value of the Status attribute. Added Section 13, Acronyms, and Section 14, Glossary. Added shading to column headings in all tables. Output all diagrams in color. Resolution: Apply CORE 5.1 Service Pack 2. Generate CSV File enhancement AR Number: Enhancement Description: Added a prompt to the Generate CSV File script enabling replacement of carriage return characters with linefeed characters in output attribute values. Microsoft Excel accepts LFs but not CRs as line delimiters within cells. Thus, without this replacement, paragraph breaks within element descriptions would not be displayed. Resolution: Apply CORE 5.1 Service Pack 2. Renaming conflicts created by name-based imports AR Number: CR.1450 Description: Bad things happen if an element is created in CORE 5.x via .RDT import, the element is renamed, and a new element is created via .RDT import in the same class with the old name. Consequences include incorrect import conflicts and inability to erase the project. Import actions intended to target the new element may instead be performed on the old element. An extra element that duplicates the old element id and the new element name may appear in subsequent exports. Resolution: Apply CORE 5.1 Service Pack 2. Name-based imports (.RDT, .RDD, and .XML in which element ids are missing) now prefer an element with the specified name over an element that currently has a different name but has a unique id generated from the specified name. Incorrect folder element counts AR Number: CR.1451 Description: Add an element to a child folder. Copy the same element to a "grandchild" folder that is a child of the previous folder. The total element count of the child folder will appear incorrect (with the copied element counted twice). Resolution: Apply CORE 5.1 Service Pack 2. Elements incorrectly sorted AR Number: CR.1452 Description: An element list may be incorrectly sorted. When an element list is viewed, an index is created or updated to speed subsequent display of the same list. However, suppose an element list includes element A but does not include element B in the same class (i.e., B is in a different folder). Suppose the list containing element A is closed, and, while the list is NOT displayed, element A is modified in a way that could affect its sort order in the list. Suppose element B is modified in a similar way, and then a list containing element B but not element A is displayed using the same sort block as the list containing element A. Subsequent lists of elements in the class using that sort block may be ordered incorrectly. Resolution: Apply CORE 5.1 Service Pack 2. NOTE: If existing indices contain incorrectly ordered elements, you can purge all indices by shifting the project to schema mode and back to database mode. The indices will be rebuilt correctly on next use. Hebrew characters swapped in script output AR Number: CR.1453 Description: The Element Output script construct incorrectly maps ASCII values 243 and 249, resulting in Hebrew characters Pe and Shin being switched when a non-Unicode Hebrew font is used. Resolution: Apply CORE 5.1 Service Pack 2. Importing "modifiedBy" property value from CORE 4.0 AR Number: CR.1454 Description: After importing a CORE 4.0 .RDT file containing a "modifiedBy" property value, it is not possible to export the project to XML. Resolution: Apply CORE 5.1 Service Pack 2. Importing spelling profile AR Number: CR.1455 Description: An error occurs importing an XML file containing user preferences that include custom additions to the spelling checker dictionary. Resolution: Apply CORE 5.1 Service Pack 2. Importing SVD with deleted element AR Number: CR.1456 Description: If an element referenced in a stored view description is deleted and the project subsequently exported to XML, CORE cannot import the resulting file. Resolution: Apply CORE 5.1 Service Pack 2. Permissions level mismatch AR Number: CR.1457 Description: XML import fails if the permissions level of the source project does not match the permissions level of the target project. Resolution: Apply CORE 5.1 Service Pack 2. Rotating PBD label after import AR Number: CR.1458 Description: Rotating a Physical Block Diagram label, saving the view settings, exporting them to XML, importing them again, re- opening the view, and attempting to rotate the same label causes a "'rotateBy:' not understood" error. Resolution: Apply CORE 5.1 Service Pack 2. Folder renamed via incremental import AR Number: CR.1459 Description: Importing a change file that renames a folder causes an error. Resolution: Apply CORE 5.1 Service Pack 2. XML export terminated on unexpected data AR Number: CR.1460 Description: In the event of unexpected data conditions, it becomes impossible to export a project to XML. Exports terminate at the point where the condition is encountered. The error message states: "Cannot export attribute . . . from object . . . as type. . . . Expected. . . ." Moreover, insufficient context is provided during the export or in log files to identify the object that is causing the problem. Such a condition arises after importing an XML file containing a "modifiedBy" property. Resolution: Apply CORE 5.1 Service Pack 2. Incremental export after modifying folder AR Number: CR.1461 Description: Create a subfolder and an element in the subfolder. Delete, rename, or move the subfolder. A subsequent export of project changes to XML fails and generates an error message stating that the original folder does not exist. Resolution: Apply CORE 5.1 Service Pack 2. Incorrect schema import results AR Number: CR.1462 Description: Schema import from XML may result in incorrect conflicts and, in some cases, incorrect results. Class changes are exported in hierarchical order, changes to a superclass being exported before changes to its subclasses. This can cause problems if, for example, an attribute definition is removed from a subclass and an attribute with the same name is defined in a superclass. Resolution: Apply CORE 5.1 Service Pack 2. Changes are now exported in the order in which they were made. Externally generated import files are capable of corrupting folder hierarchy AR Number: CR.1463 Description: It is possible for an .RDT or .XML file imported into CORE to add an element to a folder in a different class. The element may not be visible in either class, though element counts in both classes may be incorrect. It is possible to generate such an RDT file using the Advanced CSV File Parser script on a badly formed source file. Resolution: Apply CORE 5.1 Service Pack 2. Errors after deleting user AR Number: CR.1464 Description: If one CORE user or group is added to another user's default element access control list (via Tools >> User Preferences >> General >> Permissions >> Edit), and if the first user or group is then deleted, any subsequent attempt by the second user to create an element in a project with Normal- or Fine-grained permissions will fail with an error. Resolution: Apply CORE 5.1 Service Pack 2. ExternalFile references in DODAF sample model AR Number: CR.1465 Description: Several JPEG files referenced in the DODAF sample model using ExternalFile elements were omitted from the folder. Resolution: Apply CORE 5.1 Service Pack 2. Various report inconsistencies AR Number: CR.1466 Description: Missing Doc. PUIDs, formatting irregularities and inconsistencies, failure to recognize some enumeration values, other errors. Resolution: Apply CORE 5.1 Service Pack 2. Crash after screen saver activation AR Number: CR.1467 Description: On a few systems, if the Windows screen saver is activated or the system is locked while CORE is running, CORE sometimes fails (either silently or with an error). Resolution: Apply CORE 5.1 Service Pack 2. Set Project in script to closed project AR Number: CR.1468 Description: If the Set Project script construct is used to set the active project of an executing script to a project that was not explicitly opened by the user, an error occurs when, e.g., the Script Debugger is opened. Resolution: Apply CORE 5.1 Service Pack 2. The project is now automatically opened. Sys Admin privilege required to start API server AR Number: CR.1469 Description: Sys Admin privilege is required to start the CORE API server. Resolution: Apply CORE 5.1 Service Pack 2. Moving attribute definition to superclass AR Number: CR.1470 Description: If an attribute definition is removed from a class and an attribute with the same name is defined in a superclass, a conflict may occur importing the exported schema. Resolution: Apply CORE 5.1 Service Pack 2. CORE classes may now be represented twice in an XML file (first to specify attribute definition deletions and then to specify other changes). The DTD remains unchanged, and old XML files remain valid. Pasting rich text cells from element table to Excel AR Number: CR.1471 Description: The contents of rich text cells are doubled when copied from a CORE element table and pasted into Microsoft Excel. Resolution: Apply CORE 5.1 Service Pack 2. Repeated element mismatch import conflicts AR Number: CR.1472 Description: Importing a project database (in XML or RDT format) logs a conflict if the file identifies an element by its name and class and if an existing element in the target project was created in that class with that name but now has a different name and/or is in a different class. Importing a project database (in XML format only) logs a conflict if the file identifies an element by its unique identifier but also specifies the element's name and class and if the target project already has an element with that id but a different name and/or class. This is desirable behavior. However, the same conflict is logged every time the element is referenced in the import file. Resolution: Apply CORE 5.1 Service Pack 2. Repeated missing user/group conflicts AR Number: CR.1473 Description: Importing a project database in XML format logs a conflict if the file specifies a project, element, or attribute access control list with an entry corresponding to a user or group that does not exist in or has been deleted from the target repository. This is correct behavior. However, the same conflict is logged every time the missing entity is referenced in the import file. Resolution: Apply CORE 5.1 Service Pack 2. SVD and export problems after element transformation AR Number: CR.1474 Description: If an element is transformed to a different class after a stored view description of it has been captured, the stored view description remains grouped under the old class and cannot be deleted. If the stored view is an FFBD or Enhanced FFBD and if the element was transformed to a class that is not a subclass of ProcessingUnit (i.e., a class other than Function, OperationalActivity, ProgramActivity, etc.), then the project cannot be exported (in XML or RDT format). The export quickly terminates with an "'includes:' not understood" error message. Resolution: Apply CORE 5.1 Service Pack 2. When an element is transformed, existing SVDs are moved with it to the new class. Views that are not valid for the new class are deleted. Element name conflicts not properly handled by incremental XML import AR Number: CR.1475 Description: Incremental XML imports that encounter an element name conflict (i.e., an existing element in the target project with the same name in the same class as an element specified for creation in the import file) fail to generate a unique name, create an element under the new name, and map subsequent changes to the element specified by the import file to the new element under its generated name. Resolution: Apply CORE 5.1 Service Pack 2. Project property fields not properly disabled AR Number: CR.1476 Description: The Name, Description, and Base Path fields of the project properties pane are enabled even if the current user lacks administrative permission to the project. (Attempting to set the values without administrative permission generates an error.) Resolution: Apply CORE 5.1 Service Pack 2. Login error if installation folder not writeable AR Number: CR.1477 Description: A user who has enabled "Show Tips on Startup" cannot log into CORE if the user does not have write permission to the CORE installation folder. CORE attempts to store the position of the last tip displayed back into the tips database file. Resolution: Apply CORE 5.1 Service Pack 2. Now, tips database files begins with a globally unique identifier, and the position of the last tip displayed is stored in the Windows registry in a value with a name matching the identifier embedded in the file. Renames exported in wrong order AR Number: CR.1478 Description: Import conflicts can incorrectly occur on schema imports and incremental database imports containing rename commands affecting facilities, classes, relations, class attributes, relation attributes, elements, enumeration attribute possible values, and collection attribute values. The rename commands can be exported in the wrong order. To reproduce the problem with schema objects, select 2 non-essential named objects (A and B) in the same scope. Rename B to C. Rename A to B. Export. Import into a new project. To reproduce the problem with database objects, create two named objects or values (A and B) in the same scope. Export a full database file. Erase project history. Rename B to C. Rename A to B. Export an incremental database file. Erase the project database. Import the full database file. Import the change file. Resolution: Apply CORE 5.1 Service Pack 2. Renames are now exported in the same order in which they occurred. Not all renames are exported AR Number: CR.1479 Description: Import conflicts can incorrectly occur on schema imports and incremental database imports containing rename commands affecting facilities, classes, relations, class attributes, relation attributes, elements, enumeration attribute possible values, and collection attribute values. Not all rename operations are represented by exported commands. The rename history is telescoped such that, if an object is renamed twice, only one rename from the original state to the final state is captured. To reproduce the problem with schema objects, select 2 non-essential named objects (A and B) in the same scope. Rename A to C. Rename B to A. Rename C to B. Export. Import into a new project. To reproduce the problem with database objects, create two named objects or values (A and B) in the same scope. Export a full database file. Erase project history. Rename A to C. Rename B to A. Rename C to B. Export an incremental database file. Erase the project database. Import the full database file. Import the change file. Note that these examples produce a circular dependency that cannot be resolved by merely changing the export order. Resolution: Apply CORE 5.1 Service Pack 2. All rename history is now captured and exported. During upgrade, circular dependencies are detected and broken by inserting an arbitrary rename to a temporary name. Transformations exported in wrong order AR Number: CR.1480 Description: XML import conflicts can incorrectly occur on incremental database imports containing element transformation commands. Rename commands and dependent transformations can be exported in the wrong order. To reproduce the problem, create element A in class 1. Crete element A in class 2. (The name of class 1 must come alphabetically before the name of class 2.) Export a full database file. Erase project history. Rename A to B in class 2. Transform A from class 1 to class 2. Export an incremental database file. Erase the project database. Import the full database file. Import the change file. Resolution: Apply CORE 5.1 Service Pack 2. Renames and transformations are now exported in the same order in which they occurred. If elements have been transformed from one class to another and the source definition is subsequently deleted, it persists in the change history and is not eligible for garbage collection until project history is erased. Attribute renames exported in wrong order AR Number: CR.1481 Description: Import conflicts can incorrectly occur on schema imports containing class attribute rename commands. The rename commands can be exported in the wrong order. To reproduce the problem, select a non-essential, non-inherited attribute definition (designated A) in class 1. Select another non- essential, non-inherited attribute definition (designated B) in class 2, where class 2 is a subclass of class 1. Rename B to C. Rename A to B. Export. Import into a new project. Resolution: Apply CORE 5.1 Service Pack 2. Attribute renames are now captured in a single, project-wide queue and are exported in the same order in which they occurred. Schema export failure after renaming attribute AR Number: CR.1482 Description: Override a property of an element attribute definition that exists in the base schema and is inherited from a superclass. Then rename the attribute definition in the superclass. Subsequent schema exports fail (in .SCH format). Resolution: Apply CORE 5.1 Service Pack 2. Initial attribute values may not be set during schema migration AR Number: CR.1483 Description: Select a class on which a non-essential attribute is defined. Create an element in the class, but do not set any of its attribute values. Shift the project to schema mode. Delete the non-essential element attribute definition. Create a new attribute definition with the same name in the same class and specify an initial value for it. Shift the project back to database mode. The new initial value should be set for the attribute in the existing element in that class, but it is not. A similar phenomenon occurs in relationship attributes. Resolution: Apply CORE 5.1 Service Pack 2. Incorrectly numbered SSDD sections AR Number: CR.1484 Description: Section elements can be numbered incorrectly when creating Interface and Link subsections in sections 4.4.1, 4.4.2, and 4.4.3 of a System/Segment Design Document. These sections use the ReportScripts "^ SSDD HWCI-to-HWCI Interfaces", "^ SSDD HWCI-to-CSCI Interfaces", and "^ SSDD CSCI-to-CSCI Interfaces", respectively. This problem would cause script errors for any Interface comprised of more than five Links. Resolution: Apply CORE 5.1 Service Pack 2. "RTF Font Not Found" during script execution AR Number: CR.1485 Description: The error "RTF Font Not Found" will occur during script execution if: 1) The default output file has been set via either executing the Set Default Output File construct or the Open Output File construct (where there is only one output file), then 2) an Include Style Sheet construct executes where the Ignore Database Formatting parameter is set to true, and then 3) an output construct executes where a) the argument variable contains a FormattedText object, b) the output type specified is File, and c) the file name specified is nil (indicating the default output file should be used). Resolution: Apply CORE 5.1 Service Pack 2. Groups imported from CORE 4.0 have no users AR Number: CR.1486 Description: All users are missing from groups imported into CORE 5.1 from CORE 4.0. In CORE Enterprise, exporting and importing users and groups is an explicit administrator action. In CORE Workstation, users and groups are imported on startup from ACF folders specified during installation. A CORE 4.0 group could only be imported into CORE Workstation 5.1 if a user manually copied the corresponding file from a CORE Workstation 4.0 ACF folder (or a file exported from CORE Enterprise 4.0) into a CORE Workstation 5.0 ACF folder. Resolution: Apply CORE 5.1 Service Pack 2. Imported users may lack group permissions AR Number: CR.1487 Description: If a user and a group of which the user is a member are imported together, and if the name of the user comes alphabetically before the name of the group, the user may not receive permissions assigned to the group. In CORE Enterprise, exporting and importing users and groups is an explicit administrator action. In CORE Workstation, users and groups are imported on startup from ACF folders specified during installation. Resolution: Apply CORE 5.1 Service Pack 2. Conflict importing schema that promotes target class AR Number: CR.1488 Description: In schema mode, disassociate a target class from one class (but don't remove the relation) and reassociate the target class with a superclass of the original class. Exporting the schema in either .RDT or .XML format and attempting to import it into a new project generates a conflict (and the change is not effected in the new project). Resolution: Apply CORE 5.1 Service Pack 2. Error when script attempts to launch external file AR Number: CR.1489 Description: A "'handle' not understood" error message is sometimes produced when a COREscript Close File construct attempts to launch the file while another application has the input focus. Resolution: Apply CORE 5.1 Service Pack 2. Error creating new conflict file AR Number: CR.1490 Description: A "system primitive failed" error may occur if an import causes a conflict and an extremely large conflict file with the same name as the imported file already exists in the same folder. Resolution: Apply CORE 5.1 Service Pack 2. RDT import fails to assign permissions to users/groups created in 5.0 AR Number: CR.1491 Description: If a user or group is created in CORE 5.0, permissions to an object are assigned to that user or group, and the object is exported in RDT format, the permissions will not be assigned on import. Resolution: Apply CORE 5.1 Service Pack 2. Error importing negative constant AR Number: CR.1492 Description: Importing a NumberSpec with a negative constant value generates an error. Resolution: Apply CORE 5.1 Service Pack 2. Recovering FFBD operations AR Number: WS.17 Description: Cuts, removals, deletions, and pastes to/from FFBD structures generate error message "index outside of collection bounds" when the corresponding commands are executed during restoration from the recovery log. Resolution: Apply CORE Workstation 5.1 Service Pack 2. Export after loss of license AR Number: WS.19 Description: In CORE Workstation, an "'execute' not understood" error message is generated when selecting the Ok or Cancel buttons in the Repository Export dialog after the following: acquiring a valid license; logging in; losing the license (e.g., if the lease is revoked by the Network License Manager); selecting "Export Database" from the Exiting dialog. Resolution: Apply CORE Workstation 5.1 Service Pack 2. Inaccurate/inconsistent element sorting in Workstation AR Number: WS.20 Description: CORE Workstation element lists and tables may be incorrectly sorted if at least one pair of elements are equal according to a case-insensitive comparison on the primary sort key (or the first alphabetic cell of the hierarchical number, if element number is the primary sort key). Resolution: Apply CORE Workstation 5.1 Service Pack 2. Case-sensitive comparison is now performed when case-insensitive comparison yields equality. Hierarchical numbers now sort in ascending order as follows: A, A.x, a, Aa, B. ______________________________________________________________________ 6. VITECH CORPORATION SUPPLEMENTAL END USER LICENSE AGREEMENT This service pack and the documentation updates, supplements, or replaces functionality of the CORE Workstation 5.1 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.