Vitech Corporation CORE Enterprise 4.0 Client Service Pack 1 Released 8 February 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 (SP1) is an update to CORE Enterprise 4.0 client. SP1 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, and CORE2net. Please obtain the appropriate Service Pack (CORE Enterprise 4.0 Client Service Pack 1) from our website. See section 3, "OBTAINING THE SERVICE PACK", for further instructions. The Service Pack contains the following files: File Target Directory ---- ---------------- SP4001e.sll \CORE Enterprise 40 Client (abbreviated CE40) CORE40e.bnd \CE40 SP1Readme.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 sss.rpt \CE40\Reports\Formal Documentation\SSS SSShelp.doc \CE40\Reports\Formal Documentation\SSS Update.txt \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 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 ______________________________________________________________________ 2. SERVICE PACK SERVER COMPATIBILITY CORE Enterprise 4.0 Client Service Pack 1 has a corresponding server- side service pack. Clients that have the client-side Service Pack 1 installed will not be able to use a server that does not have the server-side Service Pack 1 installed. Neither will a client to which Service Pack 1 has not been applied be able to use a server to which Service Pack 1 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.vtcorp.com/updates.html If you are having difficulty downloading a service pack, call us at: (703) 883-2270 Or email us at: support@vtcorp.com ______________________________________________________________________ 4. INSTALLING THE SERVICE PACK To install CORE Enterprise 4.0 Client Service Pack 1, follow these steps: 1. Download the entclient40SP1.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 1 is complete. Please click "OK" to finish the setup. ______________________________________________________________________ 5. UNINSTALLING THE SERVICE PACK The following files should be removed: File Default Location ---- ---------------- SP4001e.sll \CORE Enterprise 40 Client CORE40e.bnd \CORE Enterprise 40 Client SP1Readme.txt \CORE Enterprise 40 Client ______________________________________________________________________ 6. DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. ______________________________________________________________________ 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.