eBiss 3

Fixed errors when writing mappings, jobs and partners to the GIT directory, among others:

• The menus for versioning are also active again in the menu bar and not only in the context menu.
• Jumping back to an older version is possible for mappings and jobs.
• The Deploy Package is created.
• The display of the history as well as a version from the history is possible (for partners, jobs and mappings).
• The file names stored in GIT have been revised so that there can no longer be any overlaps.

New Mapping Function GetAllTasks.

When generating types from the XSD, the references to already created types were sometimes only created on the fact of the same name. Which is wrong and has been fixed.

References to other elements, e.g. the template partner at the partner, were not recognized when entering via copy/paste and also when typing in the reference, the selection was difficult, which has been significantly improved with the current version. The coloring on a valid link (blue) and an invalid input (red) was improved and is now always correct. When exiting the input, invalid values are removed, so that the absence of a reference is visible before saving. The cursor for clicking on the link is now only visible above the blue text.

Too many requests were sent to the database to display the partners. These have been reduced considerably using joins/refetches.

The Excel Reader discards empty rows at the end of the table if they do not contain a value. Such rows can be retained in Excel by cell formatting, for example, and were previously imported as blank rows.

Extension of the searches in the trading, system and template partners to include the search for the backend reference.

Files reported by the FileEvent Listener and in connection with the HarddiskChannelReceiver and moving by renaming files 'timestamped' were not recognized as processed, so the FileEvent Listener did not trigger new changes. This error is fixed.

Extension of the eBiss.Api by the MessageState to IInterchange and IAttachment.

Both the caching of counters and the finding of the counter in the correct node has been revised. Previously, it could happen that a counter once found was reused after it was renamed. And a restart of the eBiss service was necessary to clean the cache. The counters are now found in the node of the executing job and when caching the old value is used during the update (FieldKind.UpdateCheck), so that:

• the selects could be reduced and
• no gaps can occur in the surface due to changes of the counter

The use of the counter is visible during execution via the inserted trace output.