With the 2019-Q3 release we introduce new functions in GEFEG.FX 7 to increase the quality of your documentation and to improve performance. In addition, some syntax-specific functions are now available across formats.
Data format upgrade
Objects in GEFEG.FX are stored in a specific data format type. Existing objects are raised to a current data format version if new functions are used that require a data format change. In the new 2019 Q3 release, the new functions Spell Check and Unique Overwriting of Notes (Model and Schema) require 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, company or organization and save them with the new data format, it is mandatory that all other GEFEG.FX users who use the same object also update to the GEFEG.FX 2019-Q3 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 urgency to update to GEFEG.FX 7 2019-Q3 Release.
The correct, error-free description of GEFEG.FX objects is the prerequisite for high-quality documentation. GEFEG.FX now supports you with the spell checker for GEFEG.FX note contents. You can use all languages installed in your Windows system as well as add additional languages via download if required.
Please note that every GEFEG.FX object you check, correct and save with the spellchecker is saved in a new GEFEG.FX internal data format to make the results effective.
Unique overwriting of Notes (Model and Schema) and "Hidden" Notes
Especially in complex mapping projects there are often multiple mapping links to different elements. The new release introduces the uniqueness of Notes. This allows a certain note to be correctly overwritten (e.g. the third note).
In addition, a note can be marked as "hidden". Notes marked as "hidden" are then excluded from the resulting documentation.
Please note that using this function will change the data format type of the respective GEFEG.FX objects.
Breadcrumb navigation now also in the EDI standard editor
In addition to the EDI Guide, Schema and Model Editor, the EDI Standard Editor now also has breadcrumb navigation.
Internal processing in GEFEG.FX has been optimized so that opening and saving GEFEG.FX objects is more powerful and faster.
CSV import for data model types
GEFEG.FX previously enabled the CSV import of Notes for elements of data models and schemas. With the new release, the CSV import was extended to types. Among other things, this functional extension facilitates the editing of data models and schemas in the EUCDM, WCO data model, ZUGFeRD or ISO 20022 environment.
Guide Technology: Show all predecessors
In GEFEG.FX it is possible to use data model or schema guides for the specific implementation of a data model or schema. This approach is particularly used where a data model or schema has been developed as a data format standard by an organization or enterprise, such as by ISO 20022 or the World Customs Organization.
All deviations and changes to an existing data model or schema are made and stored in a guide. From a technical point of view, a transparent layer is created that allows the reuse and adaptation of an existing object. In more complex projects it is common to have model guides based on each other or to use objects from another model guide.
The new release allows the user to trace the origin of an object in the hierarchy to the original. This makes it possible to see where changes have been made or whether an object has been copied from another model and thus replaces the original object.
With GEFEG.FX you can create comprehensive documentations, which for example contain different messages and further documents. Templates are often developed and used as a basis for documentation. Individual documents that are only to be used in specific documentation (e.g. specific process descriptions) cannot be contained in the template and previously had to be integrated separately into the respective documentation. In order to fulfil the user requirement that specific texts be integrated for the individual messages (e.g. an introductory text), the behaviour when using templates has been adapted as follows: If the option for the exchange of the document with a local document is set on the document in the publishing project, the document from the local directory of the message is used for the documentation.
Manager: Description texts for test data folders and test files
Reminder: Since Release 2019-Q2, a description can be saved for each test file and each test data folder. This allows messages such as test scenarios or background information to be added. For example, it turns a test file into a test case. All functions of the test file are available for the test case. If required, you can export the test case back into a text file.
As usual, you may find a complete list of new features and improvements in our Release Notes.