The new 2024-Q4 release of GEFEG.FX introduces significant enhancements for the JSON Editor. Among the key new features is the ability to not only map JSON Schema Guides but also publish them as structured documentation These functionalities provide a new level of flexibility and efficiency in managing JSON-based data structures.
Link JSON schema guides with other data formats
With the new release, JSON Schema Guides can now be semantically mapped to other data formats in GEFEG.FX. This feature ensures that JSON Schema-based data structures are precisely connected to other data formats, enabling seamless harmonisation of interfaces even with differing terminology:
- For instance, an item number might be described as data element 7140 (UN/EDIFACT) or IDTNR (SAP IDoc).
- The mapping links all identifiers, allowing the JSON tag for the item number to be quickly located across other formats.
Publication of JSON Schema Guides
Soon, it will be possible to publish JSON Schema Guides using a dedicated new template—a functionality already available for other editor types in GEFEG.FX. This new documentation capability supports both internal and external communication through clear and structured presentations of JSON data formats.
What New JSON Features Does the 2024-Q4 Release Offer?
- Optimised data integration: Map JSON schema guides with other data formats.
- Publication and Communication: Publish JSON Schema Guides as structured documentation for internal and external use.
These new features in the GEFEG.FX JSON Editor make working with JSON data structures more efficient and enhance validation capabilities.
Tips & Tricks for GEFEG.FX: Using the Publishing Project File (.man)
A useful feature in GEFEG.FX is the Publishing Project File (.man), which plays a central role in generating outputs such as:
- Documentation in HTML, Word, or PDF formats.
- Exports for XSD generation.
Predefined Publishing Projects: The “Templates” folder within the GEFEG.Distribution contains predefined .man files that allow company-specific specifications to be documented without additional configuration.
Customising Publishing Projects: If the standard templates do not meet your requirements, users can tailor the structure to their needs. A common request is to include individual Word pages in the publishing project, such as a company profile, multi-page process description, or an introduction to the data format being published. These supplementary Word pages can be directly integrated into the Publishing Project File, eliminating the need for manual and time-consuming post-editing.
Performance Improvements for EDI Guides and Standards
Another key highlight of the update is the migration of all “classic” EDI Guides and Standards to a modern database format. This upgrade allows large datasets, such as UN Locodes, to load more quickly.
Important Implementation Notes:
- To take advantage of this optimisation, all data packages for classic EDI standards must be re-downloaded during the update process.
- Editing EDI Guides remains unchanged: Existing guides can still be opened, edited, and saved as usual.
This technical modernisation enhances the efficiency of processing EDI files without affecting the user workflow.
Data packages in the GEFEG.FX distribution
The following new, supplemented or modified data packages are available for download according to your license scope.
- cXML
The package has been extended by these new versions: cXML version 1.2.063 and 1.2.064
- Anfavea RND
These standards have been added to the package:
RND003v03, RND005v02, RND009v01, RND012v08, RND101v01, RND301v00, RND302v01, RND303v00, RND304v02, RND305v00, RND306v00, RND500v00, RND600v01, RND601v03, RND603v01, RND605v00, RND800v00, RND810v00, RND820v00, RND900v01, RND901v00, RND997v01, RND998v01
