eBiss 3

From eBiss version 3.8.306 you need the runtime environment “Microsoft .NET Framework 4.8”, see: Version 3.8.306 (17.7.24)

For the mapping functions SetTargetDocumentFrameTradingPartnerByName, SetTargetDocumentFrameSystemPartnerByName, SetTargetDocumentFrameTradingPartnerByTNr, etc., in the case of a debug log, the set partner is now output in the log.

The BackendObjectTransmitter did not evaluate the FrameVariables Maps.DocumentVars.SystemPartner and Maps.DocumentVars.TradingPartner. This meant that a partner was not recognized if set e.g. via the SetTargetDocumentFrameTradingPartnerByGLN mapping function and if the document was sent directly to the BackendObjectTransmitter without creating a message.

This error has been fixed.

The IDoc Analyzer now also recognizes the type based on the name of the root element in the IDoc.

Inclusion of the SFPT Server and SFPT Client channels in the global search.

New mapping function UUIDGen.

When editing type libraries, the “Programmable components” permission was not evaluated correctly. The error has been fixed.

With the changeover from .NET 4.5.2 to .NET 4.8, the behavior of UNC paths when creating files has changed.

If “\\” was entered as the path for the Harddisk send channel and a UNC path, e.g. “\\MyServer\Data” was also entered for the partner address, then eBiss concatenated this as: “\\\\MyServer\Data”. What runs under .NET 4.5.2 leads to an error under .NET 4.8.

Therefore, and also because it is more correct, it was adjusted in deBiss that if an absolute path is entered in the address, then this is used directly.

The configuration entry MappingDontOverwriteInstance can be used to deactivate the error correction for “Mapping - rule set and lists” from release Version 3.8.302 (3.6.24). Further information can be found under eBiss .config Settings.