With the new 2019-Q4 release, the following new or enhanced functionalities are now available.
Data format upgrade
Objects in GEFEG.FX are stored in a specific data format type. Existing objects are raised to a new data format version whenever new functions are used that require a data format change. In the previous release 2019-Q3, the new Spell Check and Unique Overwrite Notes (Model and Schema) functions required saving the used GEFEG.FX objects in a new data format. New GEFEG.FX objects can be saved directly in the current data format to apply the full functionality of GEFEG.FX.
Please note that a GEFEG.FX object with the new data format type cannot be opened and edited with older releases. If you work with the same GEFEG.FX objects in a workgroup, a company and an organization and save them with the new data format, it is necessary that all other GEFEG.FX users who use the same object also update to the GEFEG.FX 2019-Q4 release to open and edit the updated objects.
If you as a user save, manage and distribute GEFEG.FX objects in repositories, please inform all other users promptly about the change of the data format type and the need to update to GEFEG.FX 7 2019-Q4 Release.
Automotive Standards: New recommendations and improved code list management
The data packages for the automotive industry have been updated.
- Update of the VDA Recommendations: New messages and new versions of the EDIFACT-based VDA Recommendations have been published and can now be referenced in EDI guides.
- Restructuring of ODETTE EDIFACT Messages: "Speaking" names now make it easier to select and reuse ODETTE guides.
- Re-organization of the code lists: Code list sets have been combined into one master code list for ease of use. For JAI, VDA, ODETTE, UN/EDIFACT a code list including all previous versions is now available. This makes it easier to use because, among other things, there is no need to search for codes in the "year slices" code lists.
Individual default settings for GEFEG.FX Notes
In GEFEG.FX Notes are used to describe guides. Notes can be used to output example values, notes and descriptions in documentation. Sometimes there is a requirement that Notes must be assigned user-specific default values. From now on, default values for Notes can be defined in the guide properties. This eliminates the tedious task of inserting the same note content. Such a default value can be, for example, a static text selected by you or the current date. These default values can be overwritten if required.
Updating multiple working copies in one step
To make collaborative work on documents and folders more efficient, many organizations use collaboration environments with repositories. The collaboration environment for GEFEG.FX supports version-controlled work across borders. A large number of working copies can be connected to GEFEG.FX, e.g. if departments of an organization maintain their own repositories or if standard body's work is carried out with the support of repositories. Updating these working copies is a regular matter. From now on, all working copies can be updated in one step. You can do this:
- Starting from the manager ALL working copies in one go or
- Update all working copies in subfolders from one folder.
Simplified validation of a test file
In complex test scenarios, a large collection of test data is stored in one or more test data folders. Often, however, the test case arises that only one test file is to be checked against an internal guide. This is now also possible without a test data folder. The validation is started directly from the test file. As with the use of test folders, an error log can be generated for the test file or the test data editor can be called for correction.
Creation of reports and export options now also in publishing projects
With the Publishing Projects functionality, human-readable documentation formats (e.g. PDF, DOCX, HTML) can be output at the push of a button. The documentation is defined via a publishing project, in which reports and export options for the objects are compiled - if available in the manager.
Now there is also the reverse gear: If reports and export options that are not available in the manager are needed in the publishing project, they can be created in the publishing project and immediately used for your documentation. These newly created components are then also available in the Manager and can be used for further publishing projects.
More flexibility for table of contents entries in documentation
A guide documentation usually consists of a set of reports. When creating documentation, table of contents entries can be generated that provide an overview of the reports used within the documentation. In addition to user-defined descriptions, aliases and start elements can now also be specified for these entries. If several objects are to be documented in a publishing project, it is now possible to assign the table of contents entries via the alias.
Advanced consistency check in publishing project
The contents of guides are output in reports. Reports use the Notes in the Guide, among other things. In unfortunate cases, information may be missing in reports if there is no report link to guide notes. This can be caused, for example, by copying a guide report into another guide. From now on, an error message is displayed in the object check when a report wants to access Notes that do not exist in the guide. This facilitates troubleshooting if expected fields are missing in reports.
As usual, you may find a complete list of new features and improvements in our Release Notes.