Endevor elements display as gibberish or raw data in Git

Products

• Endevor

Issue/Introduction

When using the Endevor Bridge for Git integration , elements under specific Types exhibit the following behavior:

• Elements are not translated into ASCII/UTF-8 format, resulting in "gibberish" or unreadable text in the Git repository.
• Clicking on certain element types in the Git interface triggers a raw data download instead of displaying the file content directly.

Environment

All supported Endevor version

All supported Bridge for Git version

Endevor web services

Cause

The Data Format in the Endevor Type Definition is set to 'B' (Binary). When the format is set to Binary, the Bridge for Git integration does not perform the necessary character conversion to ASCII/UTF-8  for Git, and browsers treat the files as binary rather than text files.

Resolution

To resolve this issue, update the Endevor Type Definition to ensure the data is treated as text:

1. Log in to the Endevor ISPF Interface.
2. Navigate to the Environment Options menu. 
3. Select Type to request the Type Definition.
4. Specify the Environment, System, and the affected Type.
5. In the Type Definition Panel, locate the Data Format field.
6. Change the Data Format from B (Binary) to T (Text).
7. Save the changes.
8. Repeat these steps for all affected element types.

 

Once updated, new synchronizations to Git should correctly translate the elements to ASCII/UTF-8 and display them as text.

Additional Information

If cache is enabled, the default expiration is set to one day, once the cache expires, the stored definitions (such as type definition) update automatically. To update definitions before expiration, the refresh button can be used.

If cache is disabled, The system queries Endevor directly via the REST API, so no action is needed to update the definitions. To update the Git repository, a manual refresh (sync-back now) can be run.