Freedom/Visio Allfusion 2E Visio - Fix Notes Version 2.0 *********** New release. Version 2.1 *********** DGM 30/01/2004 Intermitent Security Error Error HFU0239 was being incorrectly reported with the following parameters: &1 = 99999999 &2 = 1005 &3 = *BLANK DGM 30/01/2004 Include Used By Relations A new parameter has bee added to the Create VISIO ERD Import File (HCRTVSOERD) command to enable optional export of entity used by relations. This now follows the standard for documentation as seen in the Document Model Files (YDOCMDLF) command for displaying usages and references of entities. Version 3.0 *********** DGM 22/11/2004 Allow term based licencing Version 4.0 *********** DGM 01/03/2005 Shareware Limit changed In past versions the generator would stop mid-generation once the limit of 5 entities had been generated. This produced an CSV file that may not be imported into Microsoft Visio. This has been changed to now continue to generate the CSV or XML file, but exclude the attributes and relationships once the limit has been reached. The resultant CSV or XML file can then be imported into Microsoft Visio. DGM 01/03/2005 Support for XML for Visio Earlier versions of Freedom/Visio used the CSV import facility within Microsoft Visio to build the diagrams. From Microsoft Visio 2003 the CSV import facility is no longer supported. From Microsoft Visio 2002 there has been the facility to import using XML for Visio formatted import files. For this reason we have enhanced Freedom/Visio to include a new FORMAT command parameter to allow the user to specify either *CSV or *XML as the output file format. The XML for Visio format has significant improvements over the CSV format in that it provides a lot more control over the manner in which shapes and connectors are imported into the Microsoft Visio diagram. DGM 01/03/2005 < Implicit Entities > Page Freedom/Visio in XML format exports all details for the explicitly selected entities in the Allfusion 2E data model. Implicit entities are those included as a result of a relationship from an explicit entity. For implicit entities only the key file entries are exported as attributes. To make implicit entities more visible in the Microsoft Visio diagram we have included a new page - called < Implicit Entities >. Implicit entities will be added to this subject area during the generation of the export XML file. This feature is not supported for the Freedom/Visio in CSV format file. DGM 01/03/2005 Import File Default Library Name The default library name for the import file on the Create VISIO ERD Import File (HCRTVSOERD) command has been changed from QTEMP to *GENLIB. Generating the the import file to QTEMP meant that it would have to be moved to another library before it could be moved to the IFS or PC. This improves the productivity in building ERD diagrams by removing an unnecessary step in the process. DGM 01/03/2005 Implementation Names A new parameter has bee added to the Create VISIO ERD Import File (HCRTVSOERD) command to enable optional export of implementation names for entities and attributes. Implementation names will appear enclosed in brackets at the end of entity and attribute names in Microsoft Visio. DGM 01/03/2005 Dynamic Connections and Plow Code Freedom/Visio for XML format provides better control over the loading of the Microsoft Visio diagram page. Relationship connections are now able to fully support dynamic connection and plowing when moving objects around the diagram. Plowing and fully dynamic connections allow placeable shapes to move away from shapes that are dropped or moved on the diagram. This feature is not fully supported for the Freedom/Visio in CSV format file. Version 4.1 *********** DGM 16/02/2011 Command level help text Pressing F1 when prompting the HCRTVSOERD command was not displaying any help text. The command help from the User Guide has been created as a Panel Group and associated with the HCRTVSOERD command so that product documentation is now available when using the F1=Help on the HCRTEVSOERD prompt. DGM 16/02/2011 Support for IBM i 6.1 and beyond Certain objects did not have sufficient information to enable migration to IBM i6.1 and beyond. This has been rectified and all objects can now be successfully migrated to IBM i6.1 and beyond. DGM 16/02/2011 Support for MS Visio 2007 Some minor formating changes were requird to enable XML files to imported into Microsoft Visio without warnings. Recursive relationships were not importing the text for the relationship correctly. This seems to be an error with Visio and the short term solution was to remove the code from recursive relationships. DGM 16/02/2011 Recursive Relation Connections There was an outstanding issue with recursive refers to relationships being imported into Microsoft Visio from the import file. They were defined as normal refers to relations starting and ending on the same connection point. This has been fixed so that the start and end points of the relation do not use the same connection point. DGM 16/02/2011 Truncated File names When the include implementation names option is used some file names were being truncated. This has been fixed in this release. DGM 16/02/2011 Support for CA 2E pre-8.0 The tool no longer works with pre-8.0 versions of CA 2E data models. Although the tool may work for some earlier versions, it is not supported and the exported XML may contain corruption entries. DGM 16/02/2011 Support for IBM i5.1 and earlier The tool can no longer be installed on IBM i5.1 or earlier as we have prepared the tool to support customers on the newer releases. Version 4.2 *********** DGM 08/11/2012 Layer File Types and Relationship Types Each file and relationship will be allocated to a layer on the page for the associated file type or relationship type. This allows you to hide and display objects on the page based on the file or relationship type. DGM 08/11/2012 Fixed Issue with Security Violation Security check was not performing the correct checks and exits program with security violation error. This is now fixed.