===== Version 3.10.362 (3.8.26) =====

==== Message size greater than 2 GB ====  

The size of messages larger than 2 GB is now displayed correctly in the user interface. 

{{:images:sign_warning.png?nolink|}} To this end, the 'Size' property in the 'Message' and 'Attachment' classes within `eBiss.Data.dll` has been altered. **Plug-ins that use eBiss.Data.dll** may need to be recompiled. This is definitely the case if the 'Message' and 'Attachment' classes are in use.

**Note:** In most cases, it is sufficient to simply reference the eBiss.Api.dll. Messages are then accessed via the IMessage and IAttachment interfaces defined there. In the interface,
the 'Size' property has not been altered; instead, the 'Size64' property has been added and 'Size' has been marked as deprecated:
<code>
[Obsolete("Use Size64 instead.")]
int Size { get; }
</code>


====  Message attributes ====

eBiss messages have been extended to include attributes that can be set and queried in the mapping. The mapping functions for this are as follows:

  * [[en:transformation:mappings:funktionen:schreibfunktionen:settargetmessageattribute|]] and
  * [[en:transformation:mappings:funktionen:abfragefunktionen:get:getmessageattributes|]].

====  RestGet/ RestPush ====

The option "As variable ${BearerToken} in the HTTP header" for transmitting the Bearer token has been introduced. 
This means that the bearer token can be referenced in the HTTP header via ${BearerToken}, see [[en:prozessdefinition:jobs:jobsteps:webservice:rest_common|]] .




====  Supplier TradeItemManager ====

The Supplier TradeItemManager used to mark items as modified if the ValidFrom and ValidTo dates were not set. This issue has been resolved.

Furthermore, when posting a CustomObject, it was sometimes recognised as modified even though no changes had been made. This issue has also been resolved.

==== New mapping function ReplaceSpecialChars ====

New mapping function [[en:transformation:mappings:funktionen:string:replacespecialchars|]] for replacing umlauts and non-7-bit characters.

==== eBiss.WinClient32 ====

The eBiss.WinClient32 for a 32-bit eBiss.WinClient was no longer included in the setup. However, as it is still required in a few cases,
the 32-bit client has been re-included in the release.
====  eBiss.Industry, addresses expanded  ====


We extended the structure for addresses in eBiss.Industry to include the following fields:
  * Street2,
  * Street3,
  * Email und
  * Phone


==== Proxy URL for RestGet/ RestPush JobSteps ====

The RestGet/ RestPush job steps have been extended to allow a proxy URL to be specified.

In the case of a 'SaveResult', the added **File Name** property is used in RestPush to specify the file name of the imported result.

====  Restoring the previous version of eBiss ====

Instructions on how to restore the previous version of eBiss can be found at [[en:ueberblick:installation:restore_previous_version|]].


==== Data Analytics - AnalyzePromoteMessages ====  

Data Analytics was extended to include FailedRuns and the 'Size' field in the PrankeMessageAnalytics table was adjusted.

{{:images:sign_warning.png?nolink|}}Anyone using the Job Step 'AnalysePromoteMessages' must execute the following commands for the 'PrankeMessageAnalytics' table:

<code sql>
ALTER TABLE PrankeMessageAnalytics ALTER COLUMN Size bigint;
ALTER TABLE PrankeMessageAnalytics ADD FailedRuns int DEFAULT 0 NOT NULL;
</code>





==== Error with MapTriggerParent and Debug Log ====

When the MapTriggerParent attribute was set in the plug-in, an error occurred whilst analysing messages with debug tracing enabled. The error has been fixed.






==== Azure Blob Storage Send Channel ====  

[[en:kommunikation:kanal:azureblobsend|]] was extended to include the **Use attachment subdirectory** option.
If this option is enabled, the value of the Directory property of the relevant attachment is used as a subfolder within the storage account.
==== EntityAnalyzer job step, defined analyser ====  

The analyser defined in the EntityAnalyzer job step can now also be selected if the repository is public and is located in a parent node.

==== System-managed types, bulk import ====  

When importing system-managed types, it was possible to select multiple files, but this did not result in any types being imported. The error has been rectified; it is now possible
to select and import multiple individually exported types when importing system-managed types.