eBiss 3

In the job step TradeItemManagerBookCache the custom items were not booked if the “No Insert” option was set in conjunction with “Partial article update”. Unfortunately, there were no unit tests for this combination. The bug has been fixed and the relevant unit tests have been created.

The RestPush job step now creates an entry in the “State history” for the attachments sent.

Extension of OAuth2 authentication to include authentication with Google OAuth2.

Extension of the REST server address to include the client ID and client secret.

Extension of OAuth2 authentication with a JSON body to include the parameters grant_type, Client ID and Client Secret and the option to include further parameters in the JSON body via a list.

When authenticating via OAuth2, the Username and Password were used for the Client ID and Client Secret respectively, if these were not set. For example, if the Client Secret was not set, the Password that had been set was used. This logic worked during the transition period, but is now no longer usable and has been removed. This is because it is now more common for, for example, the Client Secret and the Password to be passed.

In the previous eBiss version, Where-used list were only active if the user had read access to jobs, partner channels and mappings.

This has been changed: from this version onwards, Where-used list are always active and you can only navigate to those elements for which you have at least read access.