What is new in the quarterly-release 2022-Q1?

This is how you achieve “Creating a New Version” in GEFEG.FX faster than before

When you have published a development status of data, it makes sense to “freeze” it and initiate the next development stage with a new data package. For this new version of the data package, the function Create new version is often used. In this case, all existing properties and references are transferred to the new objects in GEFEG.FX and only a new alias (short name, version, variant) is assigned. If this function is executed from a folder, several objects can also be created at the same time. Within this folder, all connected objects are automatically adjusted to the new names. This also applies to reports and publishing projects. So from now on, you no longer have to check all objects individually and adjust the properties subsequently and individually.

The Create New Version function has also been extended to allow you to append, prefix, replace, partially replace, or suffix replace for all elements of the version name – i.e. short name, version, or variant.

More comfort when creating a new version in GEFEG.FX

Suppose you have several models and associated EDI standard code lists in a folder. All of them have the suffix “preview” and the version “v1.0” in the short name. You are now using the improved function Create New Version and want to assign a new status for editing version v2.0. This should also no longer have the status Preview, so you want to remove the string “preview” in the short name and replace the version with “v2.0”.

In the wizard, to customize the short name, use the “Replace suffix” option and delete the “preview” text, leaving the field empty. To change the version name, use the “Replace” option from old “v1.0” to new “v.2.0”. With the start of the function now on the one hand the aliases themselves are adapted and on the other hand these new names are taken over also in the connected objects automatically.

Try it out: A really helpful and time-saving function when creating new data packages.

Update large working copies in GEFEG.FX now at high speed

Many users successfully use the repository functions of GEFEG.FX to develop data together in a team. You benefit from the advantages of this approach compared to the usual document use in network drives.

• Version control: Restore previous work statuses and file versions with just a few clicks
• Tracking: Check the logs to see which folders and files were last edited
• Access: All users of the repository access the latest editing status of a file

When using Subversion (SVN) repositories, you can use GEFEG.FX as a Subversion client and do not need any additional version control software. The first step in using repositories on a daily basis is to update your working copies in GEFEG.FX to retrieve the latest changes to files locally for yourself. Depending on the size of the repository and the size and type of files, this process sometimes took quite a long time.

We are pleased to report that we have achieved a major performance improvement at this point: Customers report that the update time for large repositories has improved by about 50%.

We will continue to optimise the work with repositories. Feel free to share your experiences with us: What’s going well? What concrete suggestions do you have for improvements?

Conveniently define settings for the comparison of EDI standards with the new wizard

Even though the functional scope of GEFEG.FX is quite comprehensive, the creation of a company- or organisation-specific EDI guide remains one of the most important tasks. EDI guides are primarily used for human-readable documentation, logical mappings to other formats or for the validation of test messages. As a basis for an EDI Guide, users first select the appropriate EDI standard, for example a UN/EDIFACT Directory provided by GEFEG.FX, or they develop their standard themselves by creating a company-specific flat file standard in GEFEG.FX.

Since EDI standards are updated regularly, it is necessary to check frequently whether and how standards differ:

• Have all the desired changes actually been implemented in the new release?
• What are the differences between the currently used standard and a new release of the same standard?
• Two standards have the same name: Are they actually identical or have changes been made to one standard?
• Do these two standards use the same code lists and code repository?

With the new release, a wizard guides you through the settings of the EDI standard comparison. The wizard dialogue assists you with the settings and then records the differences between two EDI standards. As a result, you receive, for example, a decision-making aid as to which of two possible EDI standards you want to use for your EDI Guides.

Our recommendation: From now on, use the wizard for comparing EDI standards and avoid the more tedious manual comparison in the EDI standard editor.

By the way: Users are now also guided through the settings in the check dialog for EDI standards with a wizard.

New data packages in GEFEG.FX

UN/EDIFACT D.21B

• New version
• UN Locode 2021-2 included

GS1 EANCOM® Implementation guidelines 9.2

• New: In agreement with GS1 Germany, the application recommendations in GEFEG.FX are now provided as a separate module.

ISO 20022

• Model/Schemas 2021-08
• ISO 20022 External code lists 2021-11
• ISO 20022 External code lists 2022-03

VDA Recommendations

• Current status of the VDA recommendations 2021
• VDA Invoice form

Also read our Release-Notes

From now on, GEFEG.FX supports the development of APIs on the basis of OpenAPI 3.x. And the best thing is: you can reuse your data in APIs and use your existing messages.

GEFEG.FX is known as the ‘hidden champion’ for design, documentation and mapping software when it comes to classic EDI(FACT) messages, XML messages, data models and standards. In short: GEFEG has been supporting the digitalisation of companies around the globe for almost four decades. Therefore, it is the natural next step to also accompany the transformation into the world of web APIs. With the new version of GEFEG.FX, you can reuse your data in APIs.

Successful pilot projects from automotive to BlockChain to marketing

When it comes to developing and setting standards, this must be optimally supported by the software used. GEFEG.FX is permanently being further developed and new functionalities added. However, the support of APIs has been a major step. A separate programme area has been created and is still being expanded. It is therefore particularly important for GEFEG to offer the usual reliability and quality here. We were able to win several pilot projects in which we were able to successfully test the new modules. The feedback from our customers was thus immediately incorporated into the development and ensured the usability of the new API module.

Support of OpenAPI 3.0 and OpenAPI 3.1 in Swagger and YAML format

For many, “Swagger” is a household name. Why? Because for many years Swagger was one of the standards on the web for APIs. Therefore, there is still a lot of software on the market that supports the Swagger 2.0 format. But this format has been obsolete for a few years and OpenAPI is the successor. Since spring 2021, OpenAPI is available in version 3.1. Of course, GEFEG.FX fully supports the new standard, but can also export the Swagger 2.0 format.

What makes GEFEG.FX different?

The strength of GEFEG.FX lies in its design-time support for electronic data exchange. Governance is on everyone’s lips today – and has been standard at GEFEG.FX for decades. Thus, data models or a message can of course be developed from scratch. In addition, existing standards can also be used or imported. Transparently tailored to the respective profile or mutually mapped to each other, this results in a significant advantage when using GEFEG.FX. It becomes easily and immediately apparent whether and where gaps exist or what special features the respective implementation requires. GEFEG.FX transfers this strength to the world of APIs.

So how can I reuse my data models in APIs?

Existing standards can also be used for APIs. Existing APIs in OpenAPI or Swagger format can be easily imported into GEFEG.FX. Either directly or via GIT and SVN support.

In addition, however, the UML data models or the UN/CEFACT reference data models as well as any XML format can be used to define an API from them. And the special thing: The connection remains intact. If the underlying data model or the linked message structure is updated, this can directly affect the API if desired.

A central point for the maintenance of data models, XML and API

This means, in particular, that GEFEG.FX can effectively be used on several tracks. If there is a need to change the electronic connection of the business partners, it is no longer necessary to adapt each mapping and each profile individually. The adjustment can be made centrally and has an immediate effect on the data models, XML messages and the API specification. This is how simple the implementation of compliance requirements can be.

What is New in the Quarterly Release 2021-Q3?

New data packages in GEFEG.FX

• UN/EDIFACT D.21A
  • New version
• GS1 EANCOM® Implementation Guidelines
  • New: In coordination with GS1 Germany, the application recommendations in GEFEG.FX are now provided as a separate module.

Easily transform EDI to APIs? Reuse your data models in APIs now. Think model-First with GEFEG.FX

From now on, GEFEG.FX supports the development of APIs on the basis of OpenAPI 3.x. And the best thing is: you can reuse your data in APIs and use your existing messages.

Read more

Clearer error messages and further improvements in message validation

For a business process to run smoothly, a message must be error-free – that is, compliant with company-specific EDI guidelines. For this reason, checking incoming or outgoing business messages for errors is a standard task for EDI teams. Our GEFEG.FX software supports EDI teams in this task, for example, by allowing messages to be validated in a test environment, by systematically checking test scenarios, or by providing error messages that clearly and unambiguously indicate the error. The following advancements support you even better in validation and testing.

Faster correction of errors through more understandable error messages!

The result of a validation in GEFEG.FX is an error log that outputs human-readable error messages in addition to technical meta information. Based on the error message, the user not only recognizes the position where an error occurred, but also immediately understands the deviation in content from the specification. In GEFEG.FX, the note “Check” is used for the error message as well as for the output of the error location. For example, a standard error description for the date format reads like this:
“The date format is incorrect. Specify “ram: DateTimeString” in the format CCYYMMDD.”

As of the current GEFEG.FX, you can describe error messages even more precisely. Build understandable identifiers into your “Check” note by embedding a link to any other note in the error message. If you describe a date field more precisely with a GEFEG.FX note, for example with the information “Delivery date” from the note “Definition”, the above error message would be output with the following text:
“The date information is incorrect. Specify the “delivery date” in the format CCYYMMDD. “

Thus, the error message is more understandable and the correction will be faster, since the user will immediately recognize the correct place in the message.

Document your test messages with one click!

Usually messages, and mostly also test messages of data formats of the classic EDI, for example ASC X12, EDIFACT, IDOC, Flatfile etc. are opened in a text editor.

As a GEFEG.FX user, you can also visualize your test messages using GEFEG.FX reports, in particular the GEFEG.FX Transaction Analyzer: Both experienced EDI experts and EDI beginners can use the crosscheck between the sample message and the standard to evaluate the contents of the message, interpret them more accurately and read off any errors.

From now on, you can also conveniently generate the GEFEG.FX Transaction Analyzer report from the reports directory of the test data folder and create the test message similar to the EDI segment report as documentation.

No XML file ready for testing? Create your XML test files from your GEFEG.FX schema!

Validation in the XML schema environment involves checking whether an XML file, often also called an XML instance, meets the specifications of a schema, i.e. is valid in the sense of the XML syntax. If the XML test file cannot be provided by the EDI partner or internal applications, GEFEG.FX can help with the following XML export: XML sample file.

This export generates an XML file based on the structure of the GEFEG.FX schema. If example values for elements and attributes have been specified in the GEFEG.FX schema, these are taken over and output as element and attribute values of the XML file.

This procedure has now been extended. From now on, you can also control the output of sample values for element and attribute variants. With variants you create slightly different versions of elements, for example buyer and seller for the party roles. Decide whether to output examples for all variants, i.e. buyer AND seller, or only for the first variant, i.e. buyer only. We recommend outputting the example values for all variants, so that there is as large a representation as possible of the possible elements in the XML file.

Would you like further explanations about variants in XML Schemas? Our support team will be pleased to assist you.

How do I recognize unused data elements and data element groups?

The EDI Guide Editor in GEFEG.FX lists the message structure as a data tree in the data area. Unused data elements and data element groups at the end of a segment are grayed out and therefore immediately visible. But how can I recognize unused data elements that are present in the middle of a segment? Until now, this was only recognizable via the GEFEG.FX note “Status”. An “N” or “X” marks the non-use of a data element or data element group.

With the current release you will find the following innovation: with the status assignment “N” or “X” a cross is shown at the data element or data element group, so that the non-use is made clear at first glance. Especially when revising an EDI Guide or in a mapping project, it is now possible to quickly determine whether a data element is used or not.

In the following example, the action code is not needed in the ORDERS Guide: The status is therefore set to “N”. The cross next to the data element tag 1229 visualizes the non-use.

What is New in the Quarterly Release 2021-Q2?

New and updated data packages in GEFEG.FX

VDA-Standards (VDA Recommendation Flatfile)

• Corrections to format, length and status according to descriptive text

• Messages, fields and code lists marked with version or variant, if they are not one-to-one across all standards

• In the code lists an English translation was added

VDA-Standards (VDA Recommendations EDIFACT)

• Released D.20B replaces the previous draft version

• In the code lists an English translation was added

TRADACOMS

• New: a consolidated separated code list that is used by all guides.

ZUGFeRD 2.0.1 and 2.1.1

XRechnung 2.0.0 and 2.0.1

ZUGFeRD 2.x and XRechnung 2.x

Invoices are increasingly being received and sent electronically, replacing paper invoices more and more. This is not least due to legal guidelines and requirements, such as the e-invoice regulation. In principle, all public sector customers must accept electronic invoices if they conform to the European standard EN16931. In Germany, the obligation to send invoices electronically is regulated at federal and state level. Currently, invoices to federal or state public-sector customers in Bremen must be sent electronically.

In addition to legal reasons, the use of electronic invoices also makes sense in terms of interoperability. With the EN16931 standard, a standard exists that standardizes the understanding of an invoice and thus ensures efficiency in invoice processing, for example by specifying the mandatory fields of an invoice.

With the current format versions of ZUGFeRD and XRechnung, two electronic e-invoice formats are now available in GEFEG.FX. Use these ZUGFeRD and XRechnung schemas and create:

• customer-specific invoice fields via customization of the ZUGFeRD and XRechnung structures.

• documentation (PDF, DOC) in company-specific design

• special verification rules, in addition to already integrated business rules of the EN standard EN16931

You can find more information on the topic of e-invoicing at:

Invoice.fans

In focus: You want more than simple documentation of your EDI guidelines?

With the publishing functions of GEFEG.FX, much more is possible!

By publishing documentation, you support your EDI partners in providing exactly the information that is required and thus facilitate the implementation of business messages. The core of a documentation consists of the specifications of message structure, formats or mandatory fields. Less technical aspects, such as the usage rules for a message or a process description, can also be output in supplementary sections. Your documentation is then not only aimed at technical EDI experts, but also supports business-oriented team members in particular in understanding the technical content of the EDI specifications.

You decide what the scope of your documentation will be, with the following options available in GEFEG.FX:

Generation of simple documentation at the click of a mouse

If you do not want to issue a comprehensive application recommendation, but decide to document a subsection, for example a structure overview, select this individual report and generate a Word or PDF file with a mouse click. Likewise, you can start a preview of your documentation at the click of a button to generate changes before the final generation.

Generation of extended documentation via Publishing Project

Use the Publishing Project in GEFEG.FX to output both the technical description of your specification (GEFEG.FX Guide) and external, static documents (PDF, DOC). This allows you, for example, to include a company profile in the introduction to the documentation to illustrate your competencies and activities. Or you can place an externally created process description in front of your specification to explain in more detail in which context the described message is used.

Generating exports using publishing projects

In many cases, GEFEG.FX guides are exported in order to make the GEFEG.FX work results available to other applications and interfaces. Exports can be used, for example, to fill internal systems (middleware) with data or to supply EDI partners with XSD and CSV formats.

If you now revise message structures in your GEFEG.FX guides, exports must be regenerated. Depending on the number of your GEFEG.FX specifications and the frequency of changes, export generation can quickly become very complex and unnecessarily time-consuming.

Including the respective export option in the publishing project makes exporting easier, faster and almost automatic. Include all GEFEG.FX guides and all desired export interfaces in the publishing project and generate all exports, for example XSDs, sample messages or separator-separated text files, at the click of a button. In summary: You update your specification(s) and receive all documentation and export output at the click of a button.

We will shortly present the full scope of the Publishing Project functions in a webinar, so that you can obtain complex documentation quickly, automatically and conveniently. Ask for a workshop or presentation on the following topic:

Documenting EDI guidelines – GEFEG.FX’s publishing functions let you do much more!

At the end of 2020, the World Customs Organization released a new version of its Data Model. GEFEG.FX users of the WCO Data Model version 3.10 can now access the new version. What is new in 3.10? Requirements due to new or amended legislation submitted as change requests by customs authorities and WCO Data Model users have been added or have been modified.

The involvement of customs authorities from around the world supports an important objective of the data model: Requirements of national and regional legislations or guidelines for implementation are considered and incorporated in the WCO Data Model. There is no new information package in this version, so that the new version is backward compatible. Extensive changes are expected in the next major version of the WCO Data Model. As it currently stands, this major version is expected to be released towards the end of 2022.

Effectiveness and efficiency of customs authorities around the globe will be improved

It is an important objective for the WCO Data Model to create and further develop a global standard for seamless crossborder transactions for all customs administrations worldwide. What are the benefits of the data model, which is intended to be the basis for information exchange of crossborder processes in a global world?

The data model opens the possibility to achieve interoperability and collaboration in single window and other implementations by customs authorities. Data flow and integration of business data for customs procedures should be simplified and harmonized. The main components of the WCO data model consist of “Base Information Packages.” These information packages compile information that is submitted by economic parties and processed by customs for typical customs processes and procedures in single window implementations or at the virtual border. This includes, for example, declarations, licenses, permits, certificates, or other types of regulatory cross-border trade documents.

Delivery of the WCO Data Model in a structured, reusable format in GEFEG.FX

In cooperation with the World Customs Organization, GEFEG has been delivering the WCO Data Model with GEFEG.FX software since the early 2010s. Thus, new possibilities for joint development work and user-specific use of the WCO Data Model opened up for Customs authorities, governmental organizations, traders and other parties involved in cross-border processes. For users, the reuse of the WCO data model is simplified and streamlined with GEFEG.FX. A ready-to-use XML schema export also contributes to this.

Easy and effective use of the WCO Data Model

Many users of the WCO data model packages in GEFEG.FX have been impressed by the simple and efficient methods for reusing the WCO data model and planning their country-specific policies. With each new release, it is important for users to determine if their existing implementations need to be modified to incorporate the latest WCO definitions of objects and customs procedures to ensure compliance with the Data Model. In this release, there are 11 new Compositions, 2 new Attributes, 3 new Classes, and 1 new Code List that are being maintained and approved by the WCO’s Data Model Project Team and applied in GEFEG.FX by GEFEG’s Implementation Support Team.

The EU Customs Data Model (EUCDM) is the new data and interface model for trans-European customs systems and for Member States’ national customs clearance systems. Its overall objective is to be the single and true source of information for modelling data requirements. It provides a technical tool that models the data requirements laid down in EU customs legislation. Thus, it sets the guideline for the technical developments of the various IT systems used for data processing by customs in the EU.

The EUCDM in machine-readable format

GEFEG is the only company to offer the EUCDM in the machine-readable GEFEG.FX format for application.

The unique GEFEG.FX software makes it easy for Member States and the private sector to adapt the EUCDM to national requirements and their own business through reuse and customisation.

Alignment of the EUCDM with own data structures

In doing so, GEFEG.FX supports both the overview of the structures of the EUCDM and the own data structures in-house. It enables easy mapping and thus supports data harmonisation between these structures.

This is done with the innovative and unique methods developed by GEFEG for using and building messaging standards.

The core of these methods is the development of so-called guidelines to define data structures and interfaces based on available message standards. Furthermore, it supports the creation of publications.

EUCDM governance and data quality assurance

Governance is a particularly important issue in cross-border data exchange. GEFEG.FX supports compliance with governance and ensures data quality. Implementations can be validated against the specifications of the customs data model as early as the development phase.

But this support is not limited to the customs data model. Data harmonisation also works with own interfaces based on other standards in this environment. This makes it possible to improve the value chain and the interaction of upstream and downstream partners.

Cost savings and efficiency gains

The increased complexity means that companies often no longer know the data structures of their systems. They do not know what happens when a field is changed in the application or how to get the information they need. In a European or even international context with many national requirements, the challenge becomes even greater. Alignment with the EUCDM leads to significant cost savings here:

The impact of legislative changes on the overall “customs” system becomes transparent.

Examples of publications in the customs environment

Examples of publications created with GEFEG.FX in the customs environment are:

• The European Customs Data Model (EUCDM) itself
• The CITES data model, which is based on the data model of the World Customs Organisation (WCO) (from p. 34)
• The interface to the Customs Management System (ECMS) of the Dutch Customs

More than 6 offers from GEFEG around the EUCDM

The methods and software systems developed by GEFEG are used by both customs administrations and the private sector, such as logistics companies.

GEFEG’s offers on the EUCDM include:

• GEFEG.FX to define the interfaces based on the EUCDM and to harmonise your data structures and interfaces against the EUCDM (and other standards).
• GEFEG.FX.Cloud: GEFEG.FX in the Amazon Workspace Cloud with application of GEFEG.FX in the web browser in any operating system without installation
• GEFEG.Portal as a cloud solution for community building and on-boarding support, e.g. for validation of data, publication of interfaces as well as sharing of information and collaboration.
• GEFEG.Packages with more than 30 other data packages, including the WCO data model, EDIFACT, UN/CEFACT CCTS, GS1, UBL etc. for the development of guidelines and data harmonisation
• GEFEG.Support with workshops and support (not only) for EUCDM and WCO data model implementers who want to customise predefined EUCDM datasets, create guidelines or perform data harmonisation
• GEFEG.API as the latest and worldwide unique component of the GEFEG product family. It allows the creation of APIs based on message standards. In this case, based on the schemas of the EUCDM, but also on any other schemas. This ensures that your API is compliant with a desired message standard.

With our offer, all kinds of digitisation projects can be carried out in the EUCDM environment: Integration projects, API projects and even AI projects can be carried out in a time- and cost-saving manner, as knowledge and complete control over all data are guaranteed at all times.

Of course, this also applies to all projects beyond the EUCDM that are based on the WCO data model or other standards. When will you start your GEFEG project?

The updated Object Check function … and more in the new GEFEG.FX Release

What’s New in the GEFEG.FX 2021-Q1 Quarterly Release?

New and updated data packages in GEFEG.FX

• EDIFACT D.20B in GEFEG.FX

New: IFTSTA as RECAST VERSION Message

• UN/LOCODES Version 2020-2

The code list for coded place names in 249 countries worldwide is updated twice a year and also delivered with GEFEG.FX.

• Automotive standards
  • New versions for Odette EDIFACT Messages
  • Finished Vehicle Logistics
  • Packaging Messages
  • Code list update
  • New version of auto-gration schema messages
• VDA standards (VDA recommendations)
  • New or revised logistics message VDA 4933, VDA 4984, VDA 4985, VDA 4987, VDA 4989, VDA 4990
  • Code list update
• WCO Data Model Version 3.10

Get on the track of structural problems with the Object Check function

If you make structural changes to project folders, this can directly affect your objects in GEFEG.FX. In the worst case, you can no longer open GEFEG.FX guides. What is the reason for this?

In many cases, objects in GEFEG.FX are linked to code lists or are based on basic standards. If these necessary objects are not linked in the GEFEG.FX Manager or have been moved/deleted outside of GEFEG.FX in Windows, GEEFG.FX guides cannot be opened properly. Multiple objects are also problematic: In such cases, GEFEG.FX cannot establish a clear assignment and cannot open the GEFEG.FX object.

Solve your problems with linking, duplicates or moved objects using the object check function

Use the object check in the manager to identify problems in linking, duplicates or moved objects. Regardless of the format (EDI guide, XML schema or data model), the result of the object check is output as an error list and can now be saved as a separate file for further analysis.

Navigate data model and schema structures quickly

A GEFEG.FX schema or data model can take on very complex structures. It is useful to define the used components (elements, types, attributes, classes) of a message globally, if required.

The advantages of such a global design include:

• Reuse

Reuse components so that structures, contents and constraints are adopted and not re-entered

• Systematic error correction

Mit der Korrektur an einer Stelle werden alle Wiederverwendungen automatisch mit korrigiert

From now on, an extension for the navigation within global objects is available, which should be especially relevant for schema and data model developers: “Show usages in messages“. Jump from a global component directly into the element structure and save time and effort without having to track every single usage.

What is a typical example of how this feature is used? You have defined a global type ‘Party’. With “Show Usages in Messages” you skip the intermediate levels and get directly to the positions of ‘Buyer’ or ‘Seller’ in the message.

GEFEG.FX Quarterly Update – What is New?

Data packages in GEFEG.FX

• ISO20022 – Data model and Code lists, 09/2020 Updates
• OAGIS 10.6 Standard and Enterprise Edition

FACELIFT for GEFEG.FX: Now with ribbons (menu bands)

GEFEG.FX now presents itself with a new face. Menu functions are clearly grouped in ribbons. As known from other software applications, ribbons are used to group related functions and commands, allowing you to edit your specifications faster and more efficiently. For example: the commands for delete, rename and insert are bundled in the Organization group. By means of the icons you can recognize the linked function at first glance and do not have to navigate through the context menu.

When opening a test data layout, it is not necessary to select a test file

When testing incoming or outgoing messages in GEFEG.FX, you will save a lot of effort that would otherwise be required for the analysis of structure or format deviations of faulty messages. Use the results of the tests in the log files as a basis for subsequent error correction.

If you want to discuss or forward your test files afterwards, you can create test message documentation in GEFEG.FX and use layouts to create a user-specific, uniform presentation.

The test scenario may comprise a single message or a set of several hundred messages. You can also use test data layouts for the targeted output of selected information of a test message.

In the new release we have optimized the layout editing: Until now, to edit test data layouts, a test file had to be determined in advance, which was used to display the layout. Now test data layouts are opened for editing without having to call up test files.

Improve navigation in your HTML documentation with modern drop-down menus

Many GEFEG.FX users create human-readable HTML documentation of their specifications in addition to PDF and Word documentation. For this purpose GEFEG.FX automatically generates hyperlinks within the structure of your object at the push of a button.

HTML documentation is particularly suitable for publication on web pages. By publishing your specifications in HTML format, you enable your partners to browse in a user-friendly way and quickly find the information they are looking for in your complex or extensive specification(s). Instead of laboriously flipping back and forth in a PDF or Word file, your partners can easily click through the documentation.

From now on, drop-down menus are also available in HTML documentation. This makes navigation clearer and easier, as the following example shows: You use variants of schemas or data models that differ slightly from each other. Use dropdown menus to group these variants together and select them from a drop-down list.

With the new GEFEG.FX Quarterly Update 2020-Q3 the following new or enhanced functionalities are available.

New data packages in GEFEG.FX

EDIFACT D.20A in GEFEG.FX

Create human-readable documentation using GEFEG.FX

For many users the functions of GEFEG.FX are important and extremely helpful for the generation of human readable outputs of the GEFEG.FX guides: the generation of documentation for the publication of specifications. In the new release our development focus is on the documentation of specifications.

A documentation consists of layout and report files. Layouts define how information is to be presented. Reports define which information is to be documented. In the following section, we present extended formatting options that enable you to process your documentation more quickly.

Select own Notes as identifiers for elements and attributes

When generating schema or data model documentation, the element or attribute name is the most important field in the respective report. The element or attribute name, that is, the tag, is used to map the structure or display a restriction. Previously, only the element tag could be displayed as the element name. From now on, you can overwrite the name of an element or attribute in reports. If you do not want to output default names of a B2B standard in specifications for your customers or for internal departments, simply overwrite them with a preferred note from the GEFEG.FX Guide.

Use stylesheets to format your documentation quickly and easily

Transferring stylesheet formats

When editing layout fields, you can use stylesheets to quickly apply predefined formatting. This formatting is adopted in the documentation and, among other things, reflects the contents of a GEFEG.FX object according to the font and color scheme of the stylesheet. New functions for stylesheets simplify and accelerate layout editing:

As of the current release, you can transfer the format of a field to another field, as known from other text editing programs. You don’t have to repeat format editing, which saves time when creating the layout.

Duplicating stylesheets

You do not need to create and build stylesheets manually. In addition to copying, you can now also duplicate and adapt existing variants in the list of stylesheets. A classic use case for slightly different formatting is the visual delimitation of element levels. If you want the display to differ in a few characteristics, it is recommended that you duplicate the stylesheet and adapt it easily.

Link components of your specification in the table of contents

You can determine the scope of the table of contents via table of contents entries. Previously, you could specify these for the beginning of a report (Branching Diagram or Component Report).

As of Release 2020-Q3, the table of contents can now be extended – in addition to or instead of the reports – for individual detail components.

A use case in the EDIFACT environment would be to list all segment identifiers in the table of contents, so that the EDI partner no longer has to comb through the Segment Detail Report to obtain details on a selected segment. For example, the LIN segment could be called directly from the table of contents. In the schema environment, an element group could be output in an extensive table of contents, so that users could jump directly to the detail view for the parent element “Party”, for example.

Avoid warnings, error messages and waiting times during documentation generation by using the consistency check

Before generating documentation (Word, PDF or HTML format), we recommend that you perform a consistency check to identify any missing base objects or incorrect links. As of the new release, you can configure the consistency check and deactivate individual messages or the entire consistency check. For example, if you do not want to check the Word file extension, deactivate this entry. The consistency check then runs faster and does not include unwanted messages. You can also deactivate warnings in the consistency check to keep the focus on actual errors.

If you generate documentation from the open publishing project, you can now deactivate any previous consistency check.

Find the following new or further developed functionalities in the latest GEFEG.FX quarterly release 2020-Q2.

Data packages in GEFEG.FX

• GS1 XML 3.4.1 and code lists
• ISO 20022 models, schemas and code lists as of 04/2020

GIT-Support in GEFEG.FX

Collaboration on documents and folders using the version control system GIT is enjoying growing popularity and, along with Subversion (SVN), represents one of the most common repository solutions. GEFEG.FX now also supports GIT repositories and can therefore be used as a GIT client. Link GIT-controlled folders in GEFEG.FX and apply proven functions of version control systems to your data, for example adding or checking in files.

Subversion (SVN) is also still supported in GEFEG.FX, of course, so SVN and GIT can be used as version control systems for your repository management in GEFEG.FX.

Faster selection of types in schema development

Types, elements and attributes are essential components of an XML schema, with which a schema structure can be built. Elements are always based on types, which are used to restrict and format elements.

In schema development or editing, each element must therefore be assigned to a type. Local or global types are available for this, depending on the selected schema design principle. In the new release, we make it easier for you to select a suitable type via a search field, so that you no longer have to scroll through a possibly long list of types. By entering the type name, you jump directly to the desired type and select it.

New diagram variant for data model or schema: Output without attributes possible

Diagrams make it easier to understand the message structure and show the structure of a message with only few technical details. For the GEFEG.FX data objects Data Model and Schema and their guides, diagrams can be generated in the GEFEG.FX Manager and exported as image files.

The current release gives you the option of outputting a diagram variant without attributes, as an alternative to the more comprehensive display with attributes. This is especially relevant if a more business-oriented view of the message is desired. This variant is also useful if existing attributes are only relevant at a later date and can be hidden for the time being.

Output of attribute paths in data model or schema reports now also for linked objects

In data modeling, attributes are used to describe properties and characteristics. Similarly, attributes are used in XML structures to transmit metadata. Since the last release, attributes with short and long name paths and the IndexPath are also output in data model and schema reports. This facilitates the classification of the attribute in the overall structure of the message as the position of the attribute in the message can be read at a glance.

In the current release we have extended this function so that the output of paths is not only possible within the GEFEG.FX object itself, but also for linked objects. Links between GEFEG.FX data objects exist, for example, in mapping projects. Previously, separate reports were necessary to output path names and IndexPath for attributes in involved mapping objects. Now, the specifications of the mapping partner can be accessed in a single report. This saves work steps and thus leads to more work efficiency.

New design function for background layouts in documentation

Documentation in GEFEG.FX can be designed very flexibly. Layout and report files form a unit in GEFEG.FX to generate Word or PDF files, for example.

The interaction of layouts and reports defines the various design options with respect to colours, fonts and font sizes in the layout file and thus provides the basis for the report. In the current release, a new setting for the page background can now be made: The opacity of the background colour can be set individually as a percentage.