Vitech Corporation CORE Enterprise 4.0 Server Service Pack 8 Released 8 January 2003 1. ABOUT THIS SERVICE PACK 2. SERVICE PACK SERVER COMPATIBILITY 3. SERVICE PACK CLIENT COMPATIBILITY 4. OBTAINING THE SERVICE PACK 5. INSTALLING THE SERVICE PACK 6. UNINSTALLING THE SERVICE PACK 7. DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK 8. VITECH CORPORATION SUPPLEMENTAL END USER LICENSE AGREEMENT ______________________________________________________________________ 1. ABOUT THIS SERVICE PACK This service pack (SP8) is an update to CORE Enterprise 4.0 server. SP8 contains a series of changes for the CORE Enterprise server. Please see section 7, "DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK", for more information. There are separate versions of the service pack corresponding to CORE Workstation, CORE Enterprise client, and CORE Enterprise server. Please obtain the appropriate Service Pack (CORE Enterprise 4.0 Server Service Pack 8) from our website. See section 4, "OBTAINING THE SERVICE PACK", for further instructions. Service Pack 8 includes all changes from Service Packs 1-7 and can be installed either by itself or after any of Service Packs 1-7. The Service Pack contains the following files: File Target Directory ---- ---------------- login.htm \COREServer\HTTP logout.htm \COREServer\HTTP timeout.htm \COREServer\HTTP SP4008n.sll \COREServer\HTTP\bin httpvtca.bnd \COREServer\HTTP\bin httpvtcc.bnd \COREServer\HTTP\bin addtargets.inc \COREServer\HTTP\Reports\common annotate.inc \COREServer\HTTP\Reports\common editattrfield.inc \COREServer\HTTP\Reports\common editelementattr.inc \COREServer\HTTP\Reports\common editelement.inc \COREServer\HTTP\Reports\common editelementtargets.inc \COREServer\HTTP\Reports\common editelemrel.inc \COREServer\HTTP\Reports\common elemattr.inc \COREServer\HTTP\Reports\common elementdiagramtable.inc \COREServer\HTTP\Reports\common endpage.inc \COREServer\HTTP\Reports\common foldermultielementselection.inc \COREServer\HTTP\Reports\common foldermultielementselectionform.inc \COREServer\HTTP\Reports\common modannotation.inc \COREServer\HTTP\Reports\common modelement.inc \COREServer\HTTP\Reports\common selecttargets.inc \COREServer\HTTP\Reports\common standardhtmlheaderadv.inc \COREServer\HTTP\Reports\common standardmessage.inc \COREServer\HTTP\Reports\common viewsmenu.inc \COREServer\HTTP\Reports\common behavior_diagram.inc \COREServer\HTTP\Reports\SystemEngineer behavior_diagram_selection.inc \COREServer\HTTP\Reports\SystemEngineer behaviormodelselection.inc \COREServer\HTTP\Reports\SystemEngineer gentableforclass.inc \COREServer\HTTP\Reports\Utilities SP4008.bat \COREServer\scripts SP4008.tpz \COREServer\scripts SP8Readme.txt \COREServer\scripts enterprise40.pdf \COREServer\doc SP8Readme.txt \COREServer\doc coreua.dll \COREServer\ualib ______________________________________________________________________ 2. SERVICE PACK SERVER COMPATIBILITY CORE Enterprise 4.0 Server Service Pack 8 is intended to be applied to a standard CORE Enterprise server installation. If CORE Enterprise 4.0 Server Service Pack 8 is installed after other server service packs, you may have to reinstall the other service packs unless their documentation explicity says it is safe to install CORE Enterprise 4.0 Server Service Pack 8 after them. Applying CORE Enterprise 4.0 Server Service Pack 8 multiple times on the same server will have no effects, either good or bad. Service Pack 8 includes all changes from Service Packs 1-7 and can be installed either by itself or after any of Service Packs 1-7. IF YOU REPLACE THE EXTENT WITH A CLEAN EXTENT, FOR EXAMPLE, WHEN RESTORING FROM A HOT BACKUP, YOU WILL HAVE TO REAPPLY THE SERVICE PACK TO THE NEW EXTENT. To determine what service packs are currently installed on a server, perform the following steps ON THE SERVER: 1. Open Windows Explorer via the Start >> Programs menu. 2. In Windows Explorer, locate and select the script subdirectory of the CORE Enterprise server installation (C:\COREServer\scripts by default) containing the two files SPReport.bat and SPReport.tpz. 3. Double-click on file SPReport.bat to run it. 4. The results of the operation are logged to SPReport.Out in the COREServer\logs directory. View this file by finding and selecting in Windows Explorer the logs subdirectory of the CORE Enterprise server installation (C:\COREServer\logs by default). 5. Double-click on file SPReport.Out to open it. 6. If prompted for an application in which to view the file, choose Notepad. ______________________________________________________________________ 3. SERVICE PACK CLIENT COMPATIBILITY CORE Enterprise 4.0 Server Service Pack 8 has a corresponding client- side service pack. Clients that do not have the client-side Service Pack 8 installed will not be able to use the server after this server- side Service Pack 8 is installed. Neither can clients to which Service Pack 8 has been applied use a server to which Service Pack 8 has not been applied. ______________________________________________________________________ 4. OBTAINING THE SERVICE PACK You can download the service pack from the support and product update section of the Vitech web site at: http://www.vitechcorp.com/updates.html If you are having difficulty downloading a service pack, call us at: (703) 883-2270 Or email us at: support@vitechcorp.com ______________________________________________________________________ 5. INSTALLING THE SERVICE PACK **************************************************************************** * WARNING: CORE2NET MUST BE SHUT DOWN AND ALL CORE ENTERPRISE USERS LOGGED * * OUT BEFORE APPLYING THIS SERVICE PACK TO THE SERVER. * **************************************************************************** NOTE: The COREStone and NetLDI51 services must be running for the service pack to be successfully applied. The installer will start them if they are not already running. NOTE: If CORE2net is running when the service pack is applied, it must be restarted for the updates to become effective. The installer will attempt to do this. Therefore, when the service pack is applied, all active CORE2net sessions will be logged out. To install CORE Enterprise 4.0 Server Service Pack 8, follow these steps: 1. Download the ent40serverSP8.exe file and double-click on it to start the setup utility. 2. Select the "Next" button at the Welcome Dialog. 3. The next dialog will ask you to specify the directory where the service pack files should be unpacked. The main CORE Enterprise 4.0 Server directory must be specified to ensure the service pack is installed correctly. By default, this directory is "C:\COREServer". If a different directory was specified during the CORE Enterprise 4.0 Server installation, you will need to specify that directory here also. 4. The setup utility will then begin unpacking the files. If you are asked whether or not to overwrite any files during this process, please select the "Yes to All" button. 5. When the installer is finished extracting the service pack files, it will launch a batch program that executes a script on the server. The script loads changes into your CORE Enterprise repository and may take several minutes to finish. 6. The installation of the CORE Enterprise 4.0 Server Service Pack 8 is complete. Please click "OK" to finish the setup. 7. Use Windows Notepad to view the file \COREServer\logs\SP4008.Out. Peruse the file for errors and make sure the end contains the text: "CORE Enterprise 4.0 Server Service Pack 8 was successfully installed." NOTE: If you restore an archived or backup repository (extent0.dbf file) that was last used before the service pack was installed, you may have to reapply the service pack when the server is running with the restored extent. Do this by double-clicking on \COREServer\scripts\SP4008.bat. ______________________________________________________________________ 6. UNINSTALLING THE SERVICE PACK The following files should be removed: File Default Location ---- ---------------- SP4008n.sll \COREServer\HTTP\bin httpvtca.bnd \COREServer\HTTP\bin httpvtcc.bnd \COREServer\HTTP\bin SP4008.bat \COREServer\scripts SP4008.tpz \COREServer\scripts SP8Readme.txt \COREServer\scripts ______________________________________________________________________ 7. DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK Error deleting element in Insert Element dialog AR Number: CR.1291 Description: Deleting the last item in the Selections list of an Insert Element dialog (used, e.g., to insert Function nodes in an FFBD) results in an "index out of bounds" error. Resolution: Apply CORE 4.0 Service Pack 8. Logging out of CORE can fail to close all windows AR Number: CR.1292 Description: Open a Database Editor. Create or select an element. Then enter an invalid hierarchical number (e.g., '1a') in the Number attribute field. Pull down the File menu on the CORE Control Panel and invoke the Logout command. Other windows will be closed, and the Login dialog will appear, but the Database Editor will remain open. Resolution: Apply CORE 4.0 Service Pack 8. CORE GUI sometimes stops showing repository updates AR Number: CR.1293 Description: Under some circumstances, CORE GUI views will stop processing updates from certain projects. For example, when an element is created, it will not appear in an appropriate element list in an existing window until the Refresh Window command is invoked. Resolution: Apply CORE 4.0 Service Pack 8. Documented CORE Expression Language operator not recognized AR Number: CR.1294 Description: The #folders operator is documented in the COREscript 4.0 Language Reference Guide but is not recognized when static checks are performed using the Validate button in the Script Editor. Resolution: Apply CORE 4.0 Service Pack 8. In EFFBD, what is Cut not always restored by Paste AR Number: CR.1296 Description: If a connected data node and function node in an EFFBD are selected and then a Cut is performed, a subsequent Paste restores the function node but not the data node. The relationship between the Item and the Function has been deleted. Resolution: Apply CORE 4.0 Service Pack 8. Relationships between selected data nodes and non-selected function nodes must be deleted to ensure the data nodes are removed by the Cut. These relationships will not be restored by a Paste. Also, if two function nodes represent the same function and only one is selected, the relationship from a selected data node to the function will still be deleted by the Cut and not restored by a Paste. Global variable values persist across COREsim runs AR Number: CR.1297 Description: The values assigned to global variables in ScriptSpecs evaluated by COREsim persist across executions of the simulation model. Resolution: Apply CORE 4.0 Service Pack 8. Case mismatch in URL generated by HTML reports AR Number: CR.1298 Description: A reference to the class list page does not match the case of the actual file name. This makes the reference unusable in a case-sensitive environment such as UNIX. Resolution: Apply CORE 4.0 Service Pack 8. SDD can fail on recursive model AR Number: CR.1299 Description: The System Description Document report script can fail if there are recursive relationships in the project on which it is running. Resolution: Apply CORE 4.0 Service Pack 8. SDD slowed down by redundant calculations AR Number: CR.1300 Description: Relevant Constraints, Functions, Interfaces, Links and PerformanceIndexes are recalculated in the different sections where they are used. Resolution: Apply CORE 4.0 Service Pack 8. These element lists are now calculated once at the beginning of the script execution. Duplicate entries in SDD Section 11 AR Number: CR.1301 Description: Duplicate entries can occur in Section 11 Part I. Resolution: Apply CORE 4.0 Service Pack 8. Protocol incorrect in SDD Section 11 AR Number: CR.1302 Description: The Protocol attribute value is not correctly output in Section 11 Part III of the System Description Document report. Resolution: Apply CORE 4.0 Service Pack 8. Converting plain text to formatted text can strip linefeeds AR Number: CR.1303 Description: When converting a plain text string to formatted text, linefeeds are stripped. This will occur when clicking an attribute button in the Extractor to copy selected text into a formatted text attribute when the Maintain Formatting option is off, or when importing 2.x or previous RDT files with text attributes that were plain strings. Resolution: Apply CORE 4.0 Service Pack 8. Enterprise import fails on empty element name AR Number: GS.162 Description: When a CORE Enterprise import encounters an empty Element name (e.g., in an RDT file generated by the Basic CSV File Parser script), the import process on the server fails due to a stack overflow instead of simply reporting the conflict. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 8. Project creation can fail in Enterprise AR Number: GS.163 Description: Occasionally, when creating a project in CORE Enterprise, the user encounters an error message near the end of the operation titled "Command Commit Failed" with text "An error occurred while attempting to commit the transaction. Error: GemStone Error - rtErrPrimFailed - Primitive failed , selector #perform:withArguments: receiver System class ." The project is not created. This can occur when concurrent sessions attempt more than one project creation, deletion, or rename at a time. A conflict could also occur if, during project creation by one session, another session logs in or opens or closes a project. Resolution: Apply CORE Enterprise 4.0 Service Pack 8. ______________________________________________________________________ Service Pack 8 includes the following changes from Service Packs 1-7. Formatting of text attributes lost in CORE2net AR Number: CN.12 Description: When a CORE2net script outputs FormattedText objects to an HTML stream, they are essentially represented as plain text. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 7 or later. Carriage returns displayed as '
' in CORE2net AR Number: CN.15 Description: When a text attribute is displayed by CORE2net in a text area blocks, a carriage return is converted into '
'. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 7 or later. CORE2net does not properly return documents of some MIME types AR Number: CN.17 Description: CORE2net returns incorrect MIME (Multipurpose Internet Mail Extensions) types in some of its HTTP (Hypertext Transfer Protocol) responses. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 7 or later. Unnecessarily large margins around CORE2net diagrams AR Number: CN.18 Description: Diagram views generated by CORE2net scripts are sometimes given unnecessarily large (300-pixel) margins. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 7 or later. CORE2net login page does not set focus in user name field AR Number: CN.20 Description: In the CORE2net login page (as well as the logout and timeout pages), the focus is not automatically set in the user name field. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 7 or later. Memory leak in Element Inspector window AR Number: CR.1272 Description: Element Inspector windows are not properly garbage-collected when they are closed. Resolution: Apply CORE 4.0 Service Pack 7 or later. Quick filter cannot compare text attribute value AR Number: CR.1273 Description: If a quick filter is defined to compare a text attribute to a string, the search string is reset to 'a FormattedText' the second time the filter is executed. Resolution: Apply CORE 4.0 Service Pack 7 or later. SRS report does not include leaf-level Functions AR Number: CR.1274 Description: The Software Requirements Specification (SRS) report fails to include Functions through the leaf level in the Function hierarchy. It only includes through the next level of allocation. Resolution: Apply CORE 4.0 Service Pack 7 or later. Reports sort Interfaces inconsistently AR Number: CR.1275 Description: Interfaces are listed in numerical order in the tables in System/Segment Specification (SSS) Section 3.2.3, Software Requirements Specification (SRS) Section 3.1, and System/ Segment Design Document (SSDD) Sections 3.4.2 and 3.4.3, but in alphabetic order in the text. Resolution: Apply CORE 4.0 Service Pack 7 or later. Interfaces and Links are now sorted numerically in both the tables and text. COREsim does not update clock time until after Function produces Resources AR Number: CR.1276 Description: In COREsim, use of a Simulator Property Query for the simulation time reveals that a Function's Duration is not added to the clock immediately upon completion of its execution, but only after all Resources are produced. Thus, a script determining the Amount produced effectively runs at the time the Function starts rather than the time at which it finishes. Resolution: Apply CORE 4.0 Service Pack 7 or later. Reported number of replacements incorrect AR Number: CR.1277 Description: The total number of replacements reported at the end of a Replace All operation is sometimes incorrect if there is a conflict in updating an element (because it is not edit locked, the user lacks permissions, the attribute is read-only, etc.). Resolution: Apply CORE 4.0 Service Pack 7 or later. Set Element Attribute script construct fails on ReferenceSpec AR Number: CR.1278 Description: Attempting to use the Set Element Attribute script construct on a ReferenceSpec attribute (e.g., of an ExternalFile, ExternalGraphic, or ExternalText) results in an error. Resolution: Apply CORE 4.0 Service Pack 7 or later. Possible to lose uncommitted attribute values AR Number: CR.1279 Description: Under some circumstances, it is possible to lose uncommitted element attribute or script construct property values when performing the following actions: o Selecting a different element in a Database Editor. o Selecting a different folder in a Database Editor. o Collapsing a folder in a Database Editor. o Performing a drag-drop operation on a folder in a Database Editor. o Invoking any of the following commands: Delete Folder, Duplicate Element, Set Attribute Permissions, Set Element Permissions, Set Project Permissions, Import Database, Import Settings, Import Users & Groups, Insert Construct, Jump to Target, Load Recovery Log, New Folder, New Element, Edit Filter, Refresh All Windows, Refresh Window, Release Edit Lock, Rerun Filter, Terminate Edit Lock, Toggle Edit Lock, Show Elements in Subfolders, Transform Element Class, Unlock All Elements. Resolution: Apply CORE 4.0 Service Pack 7 or later. Poorly positioned labels in IDEF0 diagram AR Number: CR.1280 Description: If, in an IDEF0 diagram view, a mechanism branches into child mechanisms, and if there is an input arrow such that the left boundary of the diagram is changed, the labels for the child mechanisms are not properly positioned. Instead, they are offset to the left by the amount of the shift in the left boundary. Resolution: Apply CORE 4.0 Service Pack 7 or later. Deceptive highlighting in tree view control AR Number: CR.1281 Description: Sometimes the item that appears to be selected in a tree view control is not really selected. Resolution: Apply CORE 4.0 Service Pack 7 or later. Font definitions with different character sets considered equal AR Number: CR.1282 Description: When using any font with an extended character set, the characters may be translated upon output when CORE mismaps the font definition to one of the same name but without the proper charset. Resolution: Apply CORE 4.0 Service Pack 7 or later. Word cannot display some unicode characters in RTF reports AR Number: CR.1283 Description: Unicode values in RTF (represented as '\u####') are not encoded in such a way that Microsoft Word can process two consecutive unicode values. Resolution: Apply CORE 4.0 Service Pack 7 or later. SVDs not sorted in RDT files AR Number: CR.1284 Description: Stored View Descriptions are not sorted in exported .RDT files. If an error occurs while exporting an SVD, it may be difficult to determine which element is responsible. Resolution: Apply CORE 4.0 Service Pack 7 or later. SVDs are now sorted primarily by the class and secondarily by the name of the element which the view represents. SVDs of the same element are sorted by view type, but the order of multiple hierarchy view descriptions of the same element is undefined. SVD deletion commands are not sorted. Duration script runs before Item/Resource Amounts calculated in COREsim AR Number: CR.1285 Description: In COREsim, a Function's Duration is calculated before the Function inputs or is triggered by Items or captures or consumes Resources, even though the Duration may depend on the Items or Resource Amounts. Resolution: Apply CORE 4.0 Service Pack 7 or later. Change All, Replace All commands do not work on unlocked elements in Enterprise AR Number: New Feature Description: In CORE Enterprise, the Replace All command and the spelling checker Change All command do not work on elements that are not edit locked in the user's session. Also, if the user locks an element displayed in the inspector during a Find/Replace operation, there is no opportunity to unlock the element before the inspector is closed after the Find or Replace button is clicked. Resolution: Apply CORE Enterprise 4.0 Client Service Pack 7 or later. During a Change All operation in the spelling checker or a Replace All command, an attempt is now made to edit lock and appropriately unlock elements automatically. If an element cannot be locked/unlocked, an error is reported at the end of the process. Also, during a spelling check or a Find/Replace operation in Enterprise, an attempt is now made to automatically lock an element before it is displayed in the Element Inspector window. If the element is successfully locked, it will automatically be unlocked after the inspector closes. If the element cannot be locked, no error will be reported, as the inspector will simply be displayed in its disabled state. Change All, Replace All commands do not work on element names AR Number: New Feature Description: The Replace All command and the spelling checker Change All command do not work on element names as they do on attribute values. Resolution: Apply CORE 4.0 Service Pack 7 or later. Find/Replace does not work in transcript windows AR Number: New Feature Description: The Find and Replace operations do not work in COREsim transcript windows or script transcript windows. Resolution: Apply CORE 4.0 Service Pack 7 or later. Text attribute values pasted from different sources use inconsistent fonts AR Number: New Feature Description: When the Element Extractor or the Copy and Paste commands are used to enter values of text attributes, they retain the font attributes of the source document, and the resulting attribute value styles are often inconsistent with each other, which affects report output. Resolution: Apply CORE 4.0 Service Pack 7 or later. There is now a command on the Edit menu to "Paste Unformatted" text from the clipboard into a formatted text pane. Control characters hidden in formatted text pane AR Number: New Feature Description: There is no way to view invisible control characters in text attribute values. Resolution: Apply CORE 4.0 Service Pack 7 or later. There is now a command on the Edit >> Font menu that can be toggled to "Show Control Characters" within a formatted text pane. CORE2net Annotate script requires arbitrary name AR Number: New Feature Description: The scheme used by the Annotate script in CORE2net for determining a "blank" Annotation element that can be used to hold a new annotation is that 'blank' appear anywhere in the element name. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 7 or later. The new criteria are that the Annotation Description be empty and the Annotation not be connected to any element. CORE2net Annotate script does not set Creation Stamp or Creator of Annotations AR Number: New Feature Description: When the Annotate script in CORE2net is used to annotate elements, the Annotation's Creation Stamp and Creator do not reflect the review history and cannot be used to search for Annotations created by a specific reviewer or in a specific time period. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 7 or later. Note that this change does not affect the 'owned by' relationship. CORE2net Behavior Model script assumes EFFBD representation AR Number: New Feature Description: When using the CORE2net Behavior Model script to review a functional architecture, there is no way to specify the default view. The EFFBD representation is used by default. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 7 or later. When selecting a functional architecture to review, the user is now also prompted for a default representation to use while traversing the functional model. Available views are EFFBD, FFBD, IDEF0, N2, and Text. Cannot configure update polling interval in Enterprise AR Number: New Feature Description: The interval with which a CORE Enterprise client polls for signals and updates is not configurable. The would be useful to balance server load versus commit record backlog and (in "standard" update mode) update latency. Resolution: Apply CORE Enterprise 4.0 Service Pack 7 or later. It is now possible to configure the polling interval (in milliseconds) CORE Enterprise clients use to detect GemStone signals (default 3000). It is also possible to configure the maximum number of polls after which, if no transaction control has occurred, an abort is issued to release old commit records held by the client (default 12). The latter parameter only applies to the broadcast and backchannel update mechanisms. In standard mode, an abort is issued with every poll. ______________________________________________________________________ Service Packa 7 and 8 include the following changes from Service Packs 1-6. Impossible to Find/Replace across fields AR Number: New Feature Description: Although it is possible to spell-check an entire project, the Find... and Replace... menu commands only work within a single control or field. Resolution: Apply CORE 4.0 Service Pack 6 or later. The Find and Replace dialogs now offer options to search within the: 1) active window 2) selected elements 3) selected element folder 4) selected project Too much whitespace in SSS sections 2.1 and 2.2 AR Number: CR.1267 Description: Extra white space appears in Sections 2.1 and 2.2 of the SSS report when there are a large number of applicable documents. Resolution: Apply CORE 4.0 Service Pack 6 or later. Incidental errors generated by Bookmarked HTML script AR Number: CR.1268 Description: Although the Bookmarked HTML script produces the correct output, it writes error messages to the transcript when generating diagrams if the elements are only in subfolders (with no elements in the root folder of the class). Resolution: Apply CORE 4.0 Service Pack 6 or later. Imported user may lack permissions assigned to its groups AR Number: CR.1269 Description: After importing users and groups, users may lack permissions assigned to groups in which they are members until they are removed from the groups and re-added. Occurrences are semi- random, but can be reproduced in a virgin CORE Enterprise repository using User_01 (password 'TestTest') and Group_01. Resolution: Apply CORE 4.0 Service Pack 6 or later. Cannot set time scale below 100 in COREsim Timeline window AR Number: CR.1270 Description: In simulations with very short durations, there is no way to set the time scale to less than 100, resulting in illegibly small event graphs if the results are printed at a small scale or lots of wasted pages if the results are printed at a larger scale. Resolution: Apply CORE 4.0 Service Pack 6 or later. The time scale can now be set as low as the major tick increment. Vertical scales do not work properly in COREsim AR Number: CR.1271 Description: Vertical scales in the COREsim Results window do not properly handle very large or very small values. For example, if the total amount of a resource produced during a simulation is 0.001, the result is not graphed. If the amount of resource increases dramatically and suddenly (e.g., by 1,000,000 at a time), such a large number of tick marks is drawn that CORE hangs for an extended period of time and the result is illegible. Resolution: Apply CORE 4.0 Service Pack 6 or later. "Value specified is not a possible value for this enumeration." AR Number: CR.1272 Description: When switching classes selected in the Database Editor, one can encounter the message "Value specified is not a possible value for this enumeration." This can be reproduced by creating and selecting a Constraint element. In one of the attribute drop- down lists in bottom section of the Database Editor window, select Paragraph Title. Then switch to the Originating Requirement class. Resolution: Apply CORE 4.0 Service Pack 6 or later. Problem inserting certain characters into text field AR Number: CR.1273 Description: When text containing left or right single or double quotation marks, bullets, or short or long dashes is inserted into a rich text field, the inserted text from that punctuation to the next space character is not visible. Resolution: Apply CORE 4.0 Service Pack 6 or later. One level missing from SSDD Section 3.4.3 AR Number: CR.1274 Description: In the System/Segment Design Document report (SSDD version 1.5), one level of subsection numbering is skipped in Section 3.4.3, System Internal Interfaces. Resolution: Apply CORE 4.0 Service Pack 6 or later. Lost precision in Result Detail for narrow graphs in COREsim Timeline AR Number: CR.1275 Description: In the COREsim Timeline window, clicking on a rectangular result graph populates the Result Detail fields with information about the corresponding event in the execution of the simulation model. If the duration of the event is very short (and its rectangle very narrow), the displayed values lose precision (e.g., a duration of 0.01 will be represented as 0.0). Resolution: Apply CORE 4.0 Service Pack 6 or later. Removal of element structure not reflected in change file AR Number: CR.1276 Description: If, after erasing history, the entire network structure of an element (i.e., a Function's FFBD) is removed, then, when an incremental export is performed, neither the empty structure nor any representation of its removal is included in the change (.RDT) file. Importing the file has no effect on the corresponding Function--it's structure and associated relationships are not removed. Resolution: Apply CORE 4.0 Service Pack 6 or later. Structure import fails to delete defunct 'decomposed by' relationships AR Number: CR.1277 Description: If a Function element has a structure that contains a certain number of Functions in its decomposition and an .RDT file is imported that contains a structure for the same Function with fewer Functions in its decomposition, then, after import, the Function's structure is correct (as per the .RDT file), but defunct 'decomposed by' relationships remain for Functions that are no longer in the decomposition. Resolution: Apply CORE 4.0 Service Pack 6 or later. Spelling checker accepts invalid words AR Number: CR.1278 Description: The main spelling dictionary includes many invalid words. Resolution: Apply CORE 4.0 Service Pack 6 or later. IDEF0 slow in Enterprise AR Number: GS.157 Description: Complex IDEF0 diagram views are very slow to open in CORE Enterprise. Resolution: Apply CORE 4.0 Service Pack 6 or later. Time to open complex IDEF0 diagrams in Enterprise has been cut by over 75%. CORE Expression Language 'folders' operator does not work in Enterprise AR Number: GS.158 Description: Using COREscript to iterate over the collection returned by the CORE Expression Language 'folders' operator (a valid operator for Element-type objects) fails in CORE Enterprise. Resolution: Apply CORE Enterprise 4.0 Client Service Pack 6 or later. Incremental import into Enterprise cannot delete Relationship AR Number: GS.159 Description: Importing a change file (incremental .RDT file) containing a Relationship deletion command into CORE Enterprise fails. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 6 or later. "Erase History on Import" option fails in Enterprise AR Number: GS.160 Description: When using the Export Database command to generate an .RDT file, the user has the option to specify that, when the file is imported, the recipient's system should "Erase History on Import". Enabling this option sets a flag in the preface of the .RDT file. When CORE imports an .RDT file with this flag set, it automatically performs the Erase History command on completion of the import. This is not working in CORE Enterprise. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 6 or later. Cannot import file with long path into Enterprise AR Number: GS.161 Description: An import failure message is produced attempting to import an .RDT file with a long path into CORE Enterprise. Resolution: Apply CORE Enterprise 4.0 Client Service Pack 6 or later. The Windows API invoked during file opening was OpenFile(), which fails to open a file with path length exceeding 184. ______________________________________________________________________ Service Packs 6-8 include the following changes from Service Packs 1-5. Documents not sorted in various reports AR Number: CR.1252 Description: Applicable documents listed by categories in sections 2.1 and 2.2 of the Interface Requirements Specification, Software Requirements Specification, System/Segment Design Document, System/Segment Specification, and Test & Evaluation Plan reports are not sorted. Resolution: Apply CORE 4.0 Service Pack 5 or later. Cannot produce full RDT file using Advanced CSV Parser AR Number: CR.1253 Description: Selecting the full format in the Advanced CSV Parser script results in the file contents of an incremental export. Resolution: Apply CORE 4.0 Service Pack 5 or later. Advanced CSV Parser doesn't properly handle folders AR Number: CR.1254 Description: The Advanced CSV Parser script has problems with creation of, addition to, and removal from element folders. Resolution: Apply CORE 4.0 Service Pack 5 or later. Some Functions listed twice in SDD section 7 AR Number: CR.1255 Description: Some (atomic) Functions may be listed twice in section 7 of the System Description Document report. Resolution: Apply CORE 4.0 Service Pack 5 or later. Some PerformanceIndices may not be listed in SDD section 4 AR Number: CR.1256 Description: PerformanceIndices for non-allocated intermediate Functions are not listed in section 4 when the System Description Document report is generated on a lower-level Component. Resolution: Apply CORE 4.0 Service Pack 5 or later. Assign Doc PUID output cannot be imported into Enterprise AR Number: CR.1257 Description: The Assign Documentation PUID script produces an .RDT file which uses a time stamp format in the preface that is incompatible with CORE Enterprise 4.0. Resolution: Apply CORE 4.0 Service Pack 5 or later. Assign Doc PUID misuses Last Modified AR Number: CR.1258 Description: The Assign Documentation PUID script outputs a Last Modified value for each element being assigned a Doc. PUID value. This is more properly assigned upon import of the change file. Resolution: Apply CORE 4.0 Service Pack 5 or later. Display of long element lists slow AR Number: CR.1259 Description: Display of long element lists is slow. Resolution: Apply CORE 4.0 Service Pack 5 or later. Listing of elements within a folder (with or without subfolders) has been optimized. Unneccesary add_to_category commands in RDT files AR Number: CR.1260 Description: Exported .RDT files always include an add_to_catagory command for each element to add it to the root folder. Files without this extra command import correctly, since create_element always creates the element in the root folder. Thus, the .RDT files are unnecessarily large and require more processing than necessary to import. Resolution: Apply CORE 4.0 Service Pack 5 or later. Incorrect version number in .CFT preface AR Number: CR.1261 Description: The version number in the preface of conflict files generated by CORE 4.0 is always 2.0, regardless of the version number of the imported file. Resolution: Apply CORE 4.0 Service Pack 5 or later. COREsim Function timeout can make Resources unavailable AR Number: CR.1262 Description: If a Function captures or consumes a Resource with the Acquire Available relationship attribute value set to true and, during a COREsim simulation, a construct representing the Function times out waiting for a sufficient Amount of the simulation Resource to become available, the simulation Resource is no longer available to any other Function construct (or subsequent re-entries into the same Function construct) for the remainder of the simulation. Resolution: Apply CORE 4.0 Service Pack 5 or later. Spell checker does not work on element names or attributes of type Symbol AR Number: CR.1263 Description: The spell checker does not work on element names or attributes of type Symbol. Resolution: Apply CORE 4.0 Service Pack 5 or later. Relationship creation can be slow AR Number: CR.1264 Description: Using the Database Editor to create a relationship from an element in a long list (i.e., a source element in a folder of many elements) takes a long time. Resolution: Apply CORE 4.0 Service Pack 5 or later. Optimizations have been made in relationship creation. "'extent' not understood" on login AR Number: CR.1265 Description: An "'extent' not understood" occasionally occurs on login. The workaround has been to delete the user account and recreate it. Resolution: Apply CORE 4.0 Service Pack 5 or later. Problems deleting multi-exit Function AR Number: CR.1266 Description: Create an FFBD containing a 2-exit Function. Add 2 or more constructs on one exit branch. Then delete the Function. In Enterprise, this produces an error. In Workstation, this may result in an inconsistent structure state or memory leak, though no error is produced. Resolution: Apply CORE 4.0 Service Pack 5 or later. Error saving ScriptSpec after running it in Edit ScriptSpec Window AR Number: GS.156 Description: Open a TextView on a Function in CORE Enterprise. Edit the value of the Query Criterion attribute such that the script has at least one script construct. Use the context menu on the script list pane to invoke the Run Script command. Then click Ok on the Edit ScriptSpec Window. A "previous flush did not complete" error results. Resolution: Apply CORE Enterprise 4.0 Service Pack 5 or later. CSV Parsers incorrectly parse some Excel files AR Number: N/A Description: Microsoft Excel, when saving a CSV file, may omit comma separators between right-most empty columns. Previously, the Basic and Advanced CSV Parser scripts assumed that all comma separators were present. Resolution: Apply CORE 4.0 Service Pack 5 or later. ______________________________________________________________________ Service Packs 5-8 include the following changes from Service Packs 1-4. Error hopping into While Do construct in Script Debugger AR Number: CR.1237 Description: In the Script Debugger, hopping into a While Do Construct results in an error ("'executionConstructs' not understood"). Resolution: Apply CORE 4.0 Service Pack 4 or later. COREsim drops items when sufficient Link capacity unavailable AR Number: CR.1238 Description: In COREsim, if an Item instance is carried by a Link and is output from a Function at a time when the Link does not have sufficient capacity available for the Item instance, then the Item instance is dropped and never rescheduled. Resolution: Apply CORE 4.0 Service Pack 4 or later. For every ItemInstance carried by a SimulationLink, #transmitting, #transmitted, #receiving, and #received auxiliary events are posted on the simulation transcript, not necessarily in that order. (The #receiving auxiliary event may occur before #transmitted.) If there is not sufficient capacity available on the SimulationLink when the ItemInstance is output, it is queued until sufficient capacity becomes available, and a #backlogged auxiliary event is posted. Note that these auxiliary events are listed in the simulation transcript prior to the main event during which handling they occur. Cannot export advanced filter definition AR Number: CR.1239 Description: After saving an advanced filter definition, exporting settings with filter definitions results in an error: "A HierarchicalNumber cannot be compared to a ObjectReference." Resolution: Apply CORE 4.0 Service Pack 4 or later. Load Script command does not work in advanced filter definition dialog AR Number: CR.1240 Description: In the advanced filter definition dialog, the Load Script command flashes the window but does not load the specified script into it. Resolution: Apply CORE 4.0 Service Pack 4 or later. Remove Element from Folder script construct doesn't work AR Number: CR.1241 Description: The Folder parameter of the Remove Element from Folder script construct is not listed in the script pane of the Script Editor. It is not imported when the script is saved and reloaded. It is ignored during execution. Resolution: Apply CORE 4.0 Service Pack 4 or later. Error converting large floating-point number to integer AR Number: CR.1242 Description: In the CORE Expression Language, it is impossible to send #truncate, #round, or #asInteger to a Float if the result will not fit in a 32-bit signed integer (the value must be less than or equal to 2^31 - 1). Resolution: Apply CORE 4.0 Service Pack 4 or later. First two simulation Functions contending for Resource monopolize it AR Number: CR.1243 Description: In a COREsim simulation, when three or more Functions are contending for a Resource, the first two functions monopolize it, even if other Functions have been waiting longer. Resolution: Apply CORE 4.0 Service Pack 4 or later. Error duplicating Element in subfolder AR Number: CR.1244 Description: An attempt to duplicate an Element in a subfolder within the Database Editor produces the error "index: 0 is outside of collection bounds". Resolution: Apply CORE 4.0 Service Pack 4 or later. Error using Set Element Attribute script construct AR Number: CR.1245 Description: Attempting to set an Element's text attribute to a FormattedText object using the SetElementAttribute script construct produces the error "'asFormattedTextForAttribute:' not understood". Resolution: Apply CORE 4.0 Service Pack 4 or later. Split bar problems when using multiple windows AR Number: CR.1246 Description: When a split bar is moved in one window, the corresponding split bar of another window of the same type can become hidden or can become a phantom. This can be reproduced in the Database Editor by opening two of them. After both are open, in one of them move the split bar between the folder list and the element list. Then move the split bar between the element list and the relation-target lists. Then move the split bar between the relation and target lists. Then move the split bar between the list panes and the attribute panes. Then try to repeat the same steps in the other Database Editor. Resolution: Apply CORE 4.0 Service Pack 4 or later. Error selecting IDEF0 diagram background AR Number: CR.1247 Description: Clicking just above and to the left of the end of an IDEF0 arrow results in a "'relativeLocation:' not understood" error. Resolution: Apply CORE 4.0 Service Pack 4 or later. Table number and title missing in SSS Section 3.2.2 AR Number: CR.1248 Description: The number and title are missing from the table output in Section 3.2.2 of the System/Segment Specification report script. Resolution: Apply CORE 4.0 Service Pack 4 or later. Some VerificationRequirements missing in SSS Section 4.2 AR Number: CR.1249 Description: System/Segment Specification report section 4.2 does not include VerificationRequirements for Constraints appearing in Section 5. Resolution: Apply CORE 4.0 Service Pack 4 or later. Some list items not indented in SSS AR Number: CR.1250 Description: If, in the System/Segment Specification report script output, an item in a lettered list is augmented, subsequent items are not indented. Resolution: Apply CORE 4.0 Service Pack 4 or later. Script Hierarchy Report fails to list some scripts AR Number: CR.1251 Description: The Script Hierarchy Report output does not include references to scripts that return values. Resolution: Apply CORE 4.0 Service Pack 4 or later. Error importing SVD frozen for publication AR Number: GS.154 Description: A CORE Enterprise database import fails if the .RDT file contains a stored view description that has been frozen for publication and if the element on which the view description was stored does not exist in the target project. Resolution: Apply CORE Enterprise 4.0 Service Pack 4 or later. "'extent' not understood" on Enterprise login AR Number: GS.155 Description: Occasionally, an "'extent' not understood" error occurs on login to CORE Enterprise 4.0. It is then impossible to obtain a CORE Control Panel when logging in to that account. Using another account with System Admin privilege to delete and recreate the problematic account will again permit login to that account. Resolution: Apply CORE Enterprise 4.0 Service Pack 4 or later. ______________________________________________________________________ Service Packs 4-8 include the following changes from Service Packs 1-3. CORE2net cannot handle requests via HTTP v1.0 proxy server AR Number: CN.11 Description: CORE2net logs an error when it receives a request message from an HTTP/1.0 proxy server and sends an error response back. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 3 or later. Wrong behavior diagrams in SSS Appendix C AR Number: CR.1227 Description: The wrong behavior diagrams are output in Appendix C of the System/Segment Specification report. Resolution: Apply CORE 4.0 Service Pack 3 or later. Duplicate Links in SDD Section 11 Part III AR Number: CR.1228 Description: Links can get listed twice in Section 11 Part III of the System Description Document report. Resolution: Apply CORE 4.0 Service Pack 3 or later. Publication permission doesn't work AR Number: CR.1229 Description: Granting Publish permission to a project does nothing, while granting Folder permission actually grants Publish permission. Resolution: Apply CORE 4.0 Service Pack 3 or later. Error exporting database after deleting hierarchy definition or class AR Number: CR.1230 Description: An error can be reproduced by the following steps: 1) Put a CORE project in schema mode, create a new class, and give it a description. 2) Switch the project back to database mode. Open a Database Editor. Switch it to the All Classes facility, if necessary, so that the new class shows up in the list. Create an element of the new class. Open an ER diagram view on the new element and reposition the owner node or customize the diagram by some other means. Invoke the Layout >> Save View Settings Now command to store the view description. 3) Switch the project back to schema mode. Delete the previously created class. 4) Switch the project back to database mode. 5) Attempt to export the database. The error occurs at the beginning of the export when the system attempts to purge defunct (though hidden) stored view description group corresponding to the defunct class. The same error can be produced by saving a hierarchy definition, storing a view description using that definition, and then deleting the definition. Resolution: Apply CORE 4.0 Service Pack 3 or later. Cannot parse time with separator other than colen (':') AR Number: CR.1231 Description: A computer set with Italian regional settings fails to import an .RDT file exported from same machine. The time separator for the (Italian) regional settings is the period ('.'). CORE exports in a language-neutral format. But the import process introduces some region-specific elements. Resolution: Apply CORE 4.0 Service Pack 3 or later. Hard error using script Database Update Constructs AR Number: CR.1232 Description: If a database error occurs during the execution of a script Database Update construct and the construct is not within an Update Block construct, a hard error is invoked. The error should be written to the Script Transcript. Resolution: Apply CORE 4.0 Service Pack 3 or later. Duplicate elements listed in Connection Dialog AR Number: CR.1233 Description: When a connecting element and/or its two connecting relationships are created via the Connection Dialog (e.g., using the Connect via Trigger command with two function nodes selected in an EFFBD), the element appears twice in the connection list. Resolution: Apply CORE 4.0 Service Pack 3 or later. Diagram notes lost during database import AR Number: CR.1234 Description: If multiple notes are added to a diagram view, then, after exporting the database and importing it into a clean project, only one of the notes is retained. Resolution: Apply CORE 4.0 Service Pack 3 or later. Cannot create relationship to read-only element AR Number: CR.1235 Description: In a project with normal (element-level) permissions, attempting to establish a relationship between an element to which the user has write permission and another element to which the user has read permission but not write permission fails. Moreover, one of the elements shows the relationship while the other doesn't. Resolution: Apply CORE 4.0 Service Pack 3 or later. Inaccurate error message AR Number: CR.1236 Description: When using the COREscript New Element construct without element creation permission to the project, the error message refers instead to element creation user privilege. Resolution: Apply CORE 4.0 Service Pack 3 or later. Job Monitor progress meter not cleared when job purged AR Number: GS.150 Description: When a job selected in the Job Monitor is purged, the progress meter gauge is not cleared. Resolution: Apply CORE Enterprise 4.0 Service Pack 3 or later. Waiting job not removed from Job Monitor when purged AR Number: GS.151 Description: When a waiting job is purged, it is not removed from the Job Monitor list. Resolution: Apply CORE Enterprise 4.0 Service Pack 3 or later. Stack overflow importing .RDT with invalid date in preface AR Number: GS.152 Description: A stack overflow occurs when CORE Enterprise Server attempts to parse an invalid Date from a String (e.g., the timeStamp property of the preface record in an .RDT file). Resolution: Apply CORE Enterprise 4.0 Service Pack 3 or later. Folder element list breaks on element with OOP > 536,870,912 AR Number: GS.153 Description: Element lists such as those used in the Elements pane of the Database Editor and Database Browser cannot handle elements with object IDs greater than 536,870,912. This limit is theoretical and has never been approached. Resolution: Apply CORE Enterprise 4.0 Service Pack 3 or later. CORE Enterprise now fully supports over 2 billion objects. Rich text fields do not support hyperlinks AR Number: N/A Description: Cannot insert, paste, or load working hyperlinks into rich text field values. Resolution: Apply CORE 4.0 Service Pack 3 or later. Hyperlinks are now supported in rich text fields and can be stored in and retrieved from the repository as part of rich text values. They can also be included in the output of report scripts. ______________________________________________________________________ Service Packs 3-8 include the following changes from Service Packs 1 and 2. Restore Defaults button does not reset Maximum Sessions in CORE2net Monitor AR Number: CN.6 Description: In the CORE2net Monitor, the Restore Defaults button on the Settings tab does not reset the Maximum Sessions. Resolution: Apply CORE Enterprise 4.0 Service Pack 2 or later. Error clearing HTTP Server field in CORE2net Monitor AR Number: CN.7 Description: In the CORE2net Monitor, an error--"'endsWith:' not understood"--occurs attempting to clear the HTTP Server field on the Settings tab after first saving a non-empty value there. Resolution: Apply CORE Enterprise 4.0 Service Pack 2 or later. Cannot save settings twice in CORE2net Monitor AR Number: CN.8 Description: After saving changes in the Settings tab of the CORE2net Monitor, subsequent changes made in the same CORE2net Monitor may get lost, though they appear correct until a new CORE2net Monitor is opened. Or subsequent changes may appear to get lost, though they are actually saved. Resolution: Apply CORE Enterprise 4.0 Service Pack 2 or later. No way to bind CORE2net to specific NIC AR Number: CN.9 Description: If a CORE2net server has multiple network interface cards, there is no way to bind CORE2net to only one of them. Rather, it always uses all of them, which can cause a problem if you want to run another web server on the same port on one of the adapters. Resolution: Apply CORE Enterprise 4.0 Service Pack 2 or later. Now the HTTP Server field on the Settings tab of the CORE2net Monitor is a combo box. From the drop-down list, the user can select any dotted decimal IP address available on the CORE Enterprise server. The user can also manually enter either a dotted decimal IP address or a symbolic name. If the field is left blank, or if its value is '127.0.0.1' or 'localhost' (case- insensitive), then CORE2net binds to all IP addresses on the CORE Enterprise server. If a value from the drop-down list (or a symbolic name that resolves to one of them) is selected or entered, CORE2net binds only to the selected interface, and other services can bind to the same port number on other available interfaces. If a dotted decimal address or symbolic name of a host other than the CORE Enteprise server is entered, the CORE Enterprise server attempts to start CORE2net on the remote host. In that case, even if the remote CORE2net server has multiple network adapters, CORE2net will only use the specified one. Note that Micrsoft Internet Information Server conflicts with CORE2net if they are assigned to the same port, because IIS always uses all available IP addresses even if its web sites are assigned to specific addresses. CORE2net scripts cannot specify expiration time for their output AR Number: CN.10 Description: There is no way for a CORE2net script to specify the expiration time for its output. The expiration time is included in the header of the HTTP response rather than in the body. After the expiration time, a client browser should not refresh the item from its cache, but should request an updated version using the same URI with which it was originally obtained. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 2 or later. An Expire Output script construct has been added. It accepts as a parameter or argument a String containing an HTTP-date (e.g. Thu, 01 Dec 1994 16:00:00 GMT). During execution, the construct will attempt to convert the contents of the input String to HTTP-date format if no valid HTTP-date is found within the String. An error will be generated if it is unable to do so. This time stamp will be used to expire the script output from CORE2net. The construct will do nothing when executed outside the CORE2net environment. Errors occur after closing inspector window with no element selected AR Number: CR.1207 Description: An element inspector window tracks the element selection of its parent window. If no element representation is selected in its parent, then the inspector is blank. When an inspector is closed while in this state, it is not unregistered, resulting in errors when the project is closed, when the user logs out, or when the saved image is restored. Resolution: Apply CORE 4.0 Service Pack 2 or later. Cannot shift to database mode after renaming attribute in abstract class AR Number: CR.1209 Description: If an attribute definition is renamed in an element definition that has subclasses, then it is impossible to shift the project back to database mode. Resolution: Apply CORE 4.0 Service Pack 2 or later. Problems using system font selected in User Preferences dialog AR Number: CR.1210 Description: When you set the CORE system font in your user preferences, not all database, schema, and user/group information appears in the new font. The item height in relation list panes is unaffected, and items begin to overlap at face sizes greater than or equal to 14 points. Resolution: Apply CORE 4.0 Service Pack 2 or later. Duplicate element not added to same folders as original AR Number: CR.1211 Description: When duplicating an element, if the Duplicate Element command is selected from a menu bar, the duplicate is placed in the same folder as the original. However, if the command is selected from a popup menu, the duplicate is placed in the root folder associated with its class. When an element is duplicated, the duplicate should be added to all folders (and only those folders) in which the original is a member. Resolution: Apply CORE 4.0 Service Pack 2 or later. Change to collection attribute in duplicated element affects original AR Number: CR.1213 Description: After duplicating an element with a collection attribute (such as the Fields attribute of an Item element), any changes made to the duplicate attribute also affect the corresponding attribute of the original element. Resolution: Apply CORE 4.0 Service Pack 2 or later. Activating Project Editor changes project status AR Number: CR.1214 Description: After opening or closing a project using the Status radio buttons in the Project Editor and then reversing the status in the CORE Control Panel, returning to the Project Editor (without manipulating any controls there) will switch the state of the project again. A closed project will be opened and an open project will be closed. Resolution: Apply CORE 4.0 Service Pack 2 or later. Exit CORE command cannot be added to toolbar AR Number: CR.1215 Description: The Exit CORE command is not available for adding to the Control Panel or to a toolbar. Resolution: Apply CORE 4.0 Service Pack 2 or later. Cutting branch from FFBD construct doesn't break 'decomposed by' relationships AR Number: CR.1216 Description: Cutting a branch of a parallel or other FFBD construct does not properly break the 'decomposed by' relationships between the parent Function and any nodes on the removed branch. Resolution: Apply CORE 4.0 Service Pack 2 or later. Cutting construct from FFBD doesn't break 'related to' relationships AR Number: CR.1217 Description: Cutting an iterate or replicate construct from an FFBD does not properly break the 'related to' relationship between the parent Function and the construct's DomainSet. Resolution: Apply CORE 4.0 Service Pack 2 or later. Error creating and deleting target of new relation in ER diagram AR Number: CR.1218 Description: An error is produced by the following sequence: 1) Open an ER diagram. 2) Enable the Show All Relations toggle. 3) For a relation with no targets, select the dummy target. 4) Right-click and select Edit Targets. 5) Create a new target and click Ok. 6) Select the new node, right-click, and select Remove Target. Resolution: Apply CORE 4.0 Service Pack 2 or later. Error saving Quick Filter that uses Number AR Number: CR.1219 Description: A walkback error, "A [Wild]HierarchicalNumber cannot be compared to a String," occurs when attempting to save a QuickFilterDefinition that uses the #number attribute. Resolution: Apply CORE 4.0 Service Pack 2 or later. Create Relation toolbar button causes error AR Number: CR.1222 Description: Issuing a Create Relation command from a toolbar results in an error. Resolution: Apply CORE 4.0 Service Pack 2 or later. Spurious errors due to invalid window handles AR Number: CR.1224 Description: A variety of errors occasionally crop up due to operations on invalid window handles. Resolution: Apply CORE 4.0 Service Pack 2 or later. Steps have been taken to mitigate the effects of this problem, but their source remains unclear. Typo in Tip of the Day AR Number: CR.1225 Description: A Tip of the Day refers to Functions represented in a Physical Block Diagram, which represents only ImplementationUnits. Resolution: Apply CORE 4.0 Service Pack 2 or later. Check Spelling command does not work on diagrams AR Number: CR.1226 Description: Adding the Check Spelling command to a diagram view toolbar causes an error. Resolution: Apply CORE 4.0 Service Pack 2 or later. Note that the error has been eliminated only. It is not possible to check spelling in diagrams except for the attributes portion of the ERA view. Enterprise cannot import 2.0 RDT files AR Number: GS.144 Description: CORE Enterprise 4.0 cannot import .RDT files in 2.0 format (e.g., those generated by the Advanced CSV Parser script). Resolution: Apply CORE Enterprise 4.0 Server Service Pack 1 or later. Can modify element locked by another Enterprise session AR Number: GS.145 Description: It is possible to renumber an element that is locked by another session (if that session is logged in to the same user account). It is similarly possible to rename an element and delete pieces of an FFBD structure. Resolution: Apply CORE Enterprise 4.0 Service Pack 2 or later. Transform Element Class command fails in Enterprise AR Number: GS.146 Description: Using the Transform Element Class command in CORE Enteprise produces an error message "'accessControlList' not understood", and the element class is not transformed. Resolution: Apply CORE Enterprise 4.0 Client Service Pack 2 or later. Enterprise loses imported sort block definitions AR Number: GS.147 Description: Sort block definitions imported via the Import Settings command are lost on logout from CORE Enterprise. Resolution: Apply CORE Enterprise 4.0 Client Service Pack 2 or later. One broadcast update received by each client NIC AR Number: GS.148 Description: When a client uses the broadcast update mechanism (or when autodetection of the optimal update mechanism selects the broadcast update mechanism), the client receives and processes one copy of each update for each of its network interface cards. If the client has two network adapters, for example, an element creation will result in the element being listed twice. Resolution: Apply CORE Enterprise 4.0 Service Pack 2 or later. Can modify collection attribute values of unlocked element AR Number: GS.149 Description: Items in a collection attribute list can be selected and removed from the list even if the element is not locked by the current user. Resolution: Apply CORE Enterprise 4.0 Client Service Pack 2 or later. Inaccuracies in CORE Enterprise User Reference Guide AR Number: N/A Description: The CORE Enterprise User Reference Guide is out of date, lacking descriptions of new features, containing incorrect GUI images, etc. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 1 or later. ______________________________________________________________________ Service Packs 2-8 include the following changes from Service Pack 1. Project permission level not enforced on import of RDT files from old versions AR Number: CR.1174 Description: When importing an .RDT file from CORE 3.1 or an older version into a CORE 4.0 project, the permission level of the project may not be honored. That is, attribute access control lists in the .RDT file may be added to projects created with normal (element-level) and coarse (project-level-only) permissions, and element ACLs in the .RDT file may be applied in projects created with only project-level permissions. These ACLs cannot be viewed, modified, or deleted, but their presence can cause some errors (e.g., when attempting to duplicate an element with an attribute ACL in a normal or coarse project). Resolution: Apply CORE 4.0 Service Pack 1 or later. Attribute enhancement type property value always exported as string AR Number: CR.1178 Description: During a schema export, an attribute enhancement's type property value will always be exported as string even if the attribute's type is not string. Resolution: Apply CORE 4.0 Service Pack 1 or later. Cannot delete elements from projects with coarse access control AR Number: CR.1179 Description: An error is encountered deleting elements from projects created with coarse (project-level-only) access control. Resolution: Apply CORE 4.0 Service Pack 1 or later. Obtaining subfolders in COREscript yields bag AR Number: CR.1180 Description: The COREscript documentation states that the subfolders operator returns a set of folders, when, in fact, it returns a bag. Resolution: Apply CORE 4.0 Service Pack 1 or later. ReferenceSpec not output as link in RTF AR Number: CR.1181 Description: When COREsript outputs a ReferenceSpec to HTML, it generates a live anchor (hyperlink), but the same is not true when outputting in RTF format. Resolution: Apply CORE 4.0 Service Pack 1 or later. Deleted users and groups appear in ACLs AR Number: CR.1183 Description: If a user or group is granted permissions to an object (element, attribute, or project) and is subsequently deleted, it still appears in the object access control list. Resolution: Apply CORE 4.0 Service Pack 1 or later. Importing 4.0 RDT file in "full" format modifies ACL of target project AR Number: CR.1185 Description: This is by design. A full database export in CORE 4.0 .RDT file format now includes the access control list of the source project and applies it to the target project into which it is imported. The only problem arises when the importing user is not granted administrative permission to the project by the ACL. In that case, the importing user doesn't have permission to perform any of the commands executed by the rest of the import, resulting in a large conflict file and no data imported. Resolution: Apply CORE 4.0 Service Pack 1 or later. Now the importing user is never demoted by the import in terms of project permissions. Permissions level mismatch importing any 4.0 RDT file into coarse project AR Number: CR.1186 Description: Importing any CORE 4.0 .RDT file into any project created with coarse (project-level-only) access control generates a permissions level mismatch conflict when it gets to the project access control list in the .RDT file. Resolution: Apply CORE 4.0 Service Pack 1 or later. Users may lack permissions of groups in which they are members AR Number: CR.1187 Description: Users and groups are imported from .ACF files (automatically on launch in Workstation; explicitly through User/Group Manager in Enterprise). After import, though a group may list a user as a member, the user may not know it belongs to the group. Then the user may not obtain permission to an object that is granted to the group. This can happen when the user is imported before a new group of which the user is a member. When the user is finalized, the group ID is stripped, because it does not exist, yet. Resolution: Apply CORE 4.0 Service Pack 1 or later. Progress meter behaves strangely at end of .RDT file imports into Enterprise AR Number: GS.140 Description: At the end of .RDT file imports into CORE Enterprise 4.0, the progress meter, instead of showing completion, reverts to a semi-complete or even empty state. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 1 or later. Names and comments of existing users and groups not updated on import AR Number: GS.142 Description: If two Enterprise servers have the same set of users and groups, a user or group is renamed or given a new comment in one system, and the users and groups are exported from that server and imported into the other, the changes are not reflected. Resolution: Apply CORE Enterprise 4.0 Service Pack 1 or later. Error parsing some floating-point numbers in RDT file AR Number: GS.143 Description: The algorithm used to convert a string to a floating-point number fails in CORE Enterprise 4.0 server when a string equal to '0' is parsed from an .RDT file. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 1 or later. ______________________________________________________________________ 8. VITECH CORPORATION SUPPLEMENTAL END USER LICENSE AGREEMENT This service pack and the documentation updates, supplements, or replaces functionality of the CORE 4.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.