Vitech Corporation CORE Enterprise 4.0 Client Service Pack 4 Released 11 June 2002 1. ABOUT THIS SERVICE PACK 2. SERVICE PACK SERVER COMPATIBILITY 3. OBTAINING THE SERVICE PACK 4. INSTALLING THE SERVICE PACK 5. UNINSTALLING THE SERVICE PACK 6. DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK 7. VITECH CORPORATION SUPPLEMENTAL END USER LICENSE AGREEMENT ______________________________________________________________________ 1. ABOUT THIS SERVICE PACK This service pack (SP4) is an update to CORE Enterprise 4.0 client. SP4 contains a series of changes for the CORE Enterprise client. Please see section 6, "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 Client Service Pack 4) from our website. See section 3, "OBTAINING THE SERVICE PACK", for further instructions. Service Pack 4 includes all changes from Service Packs 1, 2, and 3 and can be installed either by itself or after Service Pack 1, 2, or 3. The Service Pack contains the following files: File Target Directory ---- ---------------- SP4004e.sll \CORE Enterprise 40 Client (abbreviated CE40) CORE40e.bnd \CE40 Bmps40.dll \CE40 tips.txt \CE40 SP4Readme.txt \CE40\Docs opinfoexmatrix.rpt \CE40\Reports\C4ISR\OpInfoExchange(OV3) Update.txt \CE40\Reports\C4ISR\OpInfoExchange(OV3) tv1.rpt \CE40\Reports\C4ISR\TechProfile(TV1) Update.txt \CE40\Reports\C4ISR\TechProfile(TV1) init-irs.inc \CE40\Reports\Formal Documentation\Irs irs.rpt \CE40\Reports\Formal Documentation\Irs irshelp.doc \CE40\Reports\Formal Documentation\Irs irsrun1.inc \CE40\Reports\Formal Documentation\Irs lot-sec.inc \CE40\Reports\Formal Documentation\Irs Update.txt \CE40\Reports\Formal Documentation\Irs srs.rpt \CE40\Reports\Formal Documentation\srs srsHelp.doc \CE40\Reports\Formal Documentation\srs Update.txt \CE40\Reports\Formal Documentation\srs ssdd.rpt \CE40\Reports\Formal Documentation\ssdd SSDDhelp.doc \CE40\Reports\Formal Documentation\ssdd Update.txt \CE40\Reports\Formal Documentation\ssdd caplnks.inc \CE40\Reports\Formal Documentation\SSS check section 5.inc \CE40\Reports\Formal Documentation\SSS ffbd.inc \CE40\Reports\Formal Documentation\SSS funhier3.inc \CE40\Reports\Formal Documentation\SSS funrqmts.inc \CE40\Reports\Formal Documentation\SSS graphs.inc \CE40\Reports\Formal Documentation\SSS sss.rpt \CE40\Reports\Formal Documentation\SSS SSShelp.doc \CE40\Reports\Formal Documentation\SSS Update.txt \CE40\Reports\Formal Documentation\SSS Update1.txt \CE40\Reports\Formal Documentation\SSS Update2.txt \CE40\Reports\Formal Documentation\SSS verify.inc \CE40\Reports\Formal Documentation\SSS tep.rpt \CE40\Reports\Formal Documentation\TestAndEvaluationPlan Tephelp.doc \CE40\Reports\Formal Documentation\TestAndEvaluationPlan Update.txt \CE40\Reports\Formal Documentation\TestAndEvaluationPlan bdelemdiag.inc \CE40\Reports\HTMLs\HTML childfolders.inc \CE40\Reports\HTMLs\HTML class.inc \CE40\Reports\HTMLs\HTML classlist.inc \CE40\Reports\HTMLs\HTML diagram.inc \CE40\Reports\HTMLs\HTML elemdiag.inc \CE40\Reports\HTMLs\HTML element.inc \CE40\Reports\HTMLs\HTML folderelementsbyname.inc \CE40\Reports\HTMLs\HTML folderelementsbynumber.inc \CE40\Reports\HTMLs\HTML homepage.inc \CE40\Reports\HTMLs\HTML html.rpt \CE40\Reports\HTMLs\HTML initvrbl.inc \CE40\Reports\HTMLs\HTML pgbyname.inc \CE40\Reports\HTMLs\HTML pgbynum.inc \CE40\Reports\HTMLs\HTML README.TXT \CE40\Reports\HTMLs\HTML startclass.inc \CE40\Reports\HTMLs\HTML startdiagram.inc \CE40\Reports\HTMLs\HTML Update.txt \CE40\Reports\HTMLs\HTML bdelemdiag.inc \CE40\Reports\HTMLs\HTMLBook childfolders.inc \CE40\Reports\HTMLs\HTMLBook classfin.inc \CE40\Reports\HTMLs\HTMLBook classlist.inc \CE40\Reports\HTMLs\HTMLBook diagram.inc \CE40\Reports\HTMLs\HTMLBook elemdiag.inc \CE40\Reports\HTMLs\HTMLBook elementlinktobdpage.inc \CE40\Reports\HTMLs\HTMLBook folderelementsbyname.inc \CE40\Reports\HTMLs\HTMLBook folderelementsbynumber.inc \CE40\Reports\HTMLs\HTMLBook homepage.inc \CE40\Reports\HTMLs\HTMLBook htmlbook.rpt \CE40\Reports\HTMLs\HTMLBook initvrbl.inc \CE40\Reports\HTMLs\HTMLBook pgbyname.inc \CE40\Reports\HTMLs\HTMLBook pgbynum.inc \CE40\Reports\HTMLs\HTMLBook README.TXT \CE40\Reports\HTMLs\HTMLBook startclass.inc \CE40\Reports\HTMLs\HTMLBook startdiagram.inc \CE40\Reports\HTMLs\HTMLBook Update.txt \CE40\Reports\HTMLs\HTMLBook if.inc \CE40\Reports\System Engineering\Sdd part2.inc \CE40\Reports\System Engineering\Sdd resource.inc \CE40\Reports\System Engineering\Sdd sdd.rpt \CE40\Reports\System Engineering\Sdd toplvl1.inc \CE40\Reports\System Engineering\Sdd Update.txt \CE40\Reports\System Engineering\Sdd Update1.txt \CE40\Reports\System Engineering\Sdd prsincl.inc \CE40\Reports\Utility\ScriptHierarchy Update.txt \CE40\Reports\Utility\ScriptHierarchy ______________________________________________________________________ 2. SERVICE PACK SERVER COMPATIBILITY CORE Enterprise 4.0 Client Service Pack 4 has a corresponding server- side service pack. Clients that have the client-side Service Pack 4 installed will not be able to use a server that does not have the server-side Service Pack 4 installed. Neither will a client to which Service Pack 4 has not been applied be able to use a server to which Service Pack 4 has been applied. ______________________________________________________________________ 3. 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 ______________________________________________________________________ 4. INSTALLING THE SERVICE PACK To install CORE Enterprise 4.0 Client Service Pack 4, follow these steps: 1. Download the ent40clientSP4.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 client directory must be specified to ensure the service pack is installed correctly. By default, this directory is "C:\Program Files\Vitech Corporation\CORE Enterprise 40 Client". If a different directory was specified during the CORE Enterprise 4.0 client 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. The installation of the CORE Enterprise 4.0 Client Service Pack 4 is complete. Please click "OK" to finish the setup. ______________________________________________________________________ 5. UNINSTALLING THE SERVICE PACK The following files should be removed: File Default Location ---- ---------------- SP4004e.sll \CORE Enterprise 40 Client CORE40e.bnd \CORE Enterprise 40 Client SP4Readme.txt \CORE Enterprise 40 Client ______________________________________________________________________ 6. DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. "'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. ______________________________________________________________________ Service Pack 4 includes the following changes from Service Packs 1, 2, and 3. 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 and 4 includes 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, 3, and 4 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. Service pack not reflected in error text AR Number: CR.1175 Description: Service pack designations are sometimes not included in the text of printed, saved, and emailed error logs. Resolution: Apply CORE 4.0 Service Pack 1 or later. Sending error without MAPI support generates further errors AR Number: CR.1176 Description: Attempting to email an error message to Vitech support from an error notification dialog on a system that lacks MAPI support generates further errors that sometimes mask the real problem. Resolution: Apply CORE 4.0 Service Pack 1 or later. A message box is now displayed rather than another error notifier if CORE cannot initialize MAPI support to email an error message. Non-formatted text panes are not spell-checked AR Number: CR.1177 Description: Non-formatted text panes, such as those used in script editors, cannot be spell-checked. 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. Error editing ReferenceSpec in project with no base path AR Number: CR.1182 Description: Editing a ReferenceSpec path in a project which base path has not been set generates error "'beginsWith:' not understood". More specifically, when working with a non-file-system path (e.g., mailto:, http:, etc.), if the scheme is removed in the editing process then this error is generated. 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. Project Editor unusable when shrunk to minimal size AR Number: CR.1188 Description: The minimum size of the Project Editor window is so small that, when it is at that size, many controls overlap, and the window is an unusable mess. Resolution: Apply CORE 4.0 Service Pack 1 or later. Error using Send Mail Message script construct with non-string priority AR Number: CR.1189 Description: Attempting to send an email message via the Send Mail Message construct in COREscript can result in a MAPI error. This occurs when the specified priority is not a string. Resolution: Apply CORE 4.0 Service Pack 1 or later. Error performing inter-project drag-drop operation AR Number: CR.1190 Description: An error can occur when a user performs a drag-drop operation such as dragging an element representation in one window onto an element representation in another window to establish a relationship between the elements. The problem results when the windows are open on different projects (and, thus, the elements are in different projects). Resolution: Apply CORE 4.0 Service Pack 1 or later. Error adding exit node to FFBD for new CompletionCriterion AR Number: CR.1191 Description: An error is generated by adding an exit node to an FFBD or EFFBD when the selected CompletionCriterion is not already among the 'exits by' targets (i.e., the Add button is used in the Select Completion Criterion dialog). Resolution: Apply CORE 4.0 Service Pack 1 or later. Errors selecting COREscript Element Output construct AR Number: CR.1192 Description: An "'attributeName' not understood" error is produced when an COREscript Element Output construct is selected and the first representation field in the list is an attribute field. A "'relationName' not understood" error is produced when an COREscript Element Output construct is selected and the first representation field in the list is a target field. Resolution: Apply CORE 4.0 Service Pack 1 or later. Problems updating COREscript Element Output construct edit panes AR Number: CR.1193 Description: There are problems updating the literal and target representation field panes when text is updated within the pane and then another item is selected in the representation field list of the COREscript Element Output construct edit pane. Resolution: Apply CORE 4.0 Service Pack 1 or later. Script construct edit pane not properly updated on construct deletion/removal AR Number: CR.1194 Description: Cutting or removing a construct from a script does not properly update the construct pane showing the parameters for the newly selected construct. Resolution: Apply CORE 4.0 Service Pack 1 or later. Error in Script Debugger inspecting variable value which is ElementCategory AR Number: CR.1195 Description: An error occurs when the Script Debugger is set to inspect the value of a variable to which an ElementCategory object (an element folder) has been assigned. Resolution: Apply CORE 4.0 Service Pack 1 or later. Database update constructs unavailable in COREsim AR Number: CR.1196 Description: The COREscript database update constructs are not available for use in ScriptSpec attribute values evaluated by COREsim (used, for example, to specify function duration). Resolution: Apply CORE 4.0 Service Pack 1 or later. Breakpoint not properly handled within Block construct AR Number: CR.1197 Description: COREscript Breakpoint constructs are not properly handled within some Block constructs. Resolution: Apply CORE 4.0 Service Pack 1 or later. Check All and Uncheck All exceedingly slow in Timeline Elements window AR Number: CR.1198 Description: The operation of the Check All and Uncheck All buttons in the COREsim Timeline Elements window is exceedingly slow on a large simulation model that has already been executed and has a Timeline window open. Resolution: Apply CORE 4.0 Service Pack 1 or later. Error opening simulation model containing replicate construct AR Number: CR.1199 Description: A CORE error occurs when opening COREsim on a function which structure contains a replicate construct (or on any of the function's parents that have their execution level set to 'follow decomposition', etc.). Resolution: Apply CORE 4.0 Service Pack 1 or later. Note that COREsim does not currently support replicate constructs. However, now a more helpful message is presented. COREsim always assumes item size to be 1.0 AR Number: CR.1200 Description: In COREsim, item size is ignored and assumed to be 1.0. This can cause the amount of time it takes items to traverse constrained links and the link capacity utilization to be calculated incorrectly. Resolution: Apply CORE 4.0 Service Pack 1 or later. Not all information exchanges listed by Operational Information Exchange Matrix AR Number: CR.1201 Description: Not all information exchanges are listed in the (OV-3) Operational Information Exchange Matrix script. Resolution: Apply CORE 4.0 Service Pack 1 or later. Technical Architecture Profile script lists links rather than interfaces AR Number: CR.1202 Description: The (TV-1) Technical Architecture Profile script lists links rather than interfaces. Resolution: Apply CORE 4.0 Service Pack 1 or later. When script prompts for document to produce, includes documents of wrong type AR Number: CR.1203 Description: When formal documentation scripts prompt for a document element representing the report to be produced, the list includes documents which Document Type attribute values don't match the running script and can't be used by it. This issue affects the following scripts: IRS, SRS, SSDD, SSS, and Test & Evaluation Plan. Resolution: Apply CORE 4.0 Service Pack 1 or later. Performance problems in HTML and Bookmarked HTML Report scripts AR Number: CR.1204 Description: Elements and relationships are unnecessarily accessed from the database multiple times. Multiple files are generated for the same element if it exists in multiple folders. Resolution: Apply CORE 4.0 Service Pack 1 or later. This service pack also provides a user option to omit engineers and 'owned by' relationships from the HTML and Bookmarked HTML Report scripts, improves some progress indicator messages, and widens element lists. Invalid links generated by HTML and Bookmarked HTML Report scripts AR Number: CR.1205 Description: A non-existent file is referenced in anchors (links) generated by the HTML and Bookmarked HTML Report scripts if only class subfolders contain elements for the first class (alphabetically). Resolution: Apply CORE 4.0 Service Pack 1 or later. Bookmarked HTML Report script creates invalid bookmark references AR Number: CR.1206 Description: The Bookmarked HTML Report script creates invalid bookmark references in target lists and diagrams if the referenced element is in more than one subfolder and not in the class root folder. 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. Cannot open Element Extractor AR Number: GS.141 Description: An error occurs opening the Element Extractor in CORE Enterprise 4.0. Resolution: Apply CORE Enterprise 4.0 Client 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. ______________________________________________________________________ 7. 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.