===== Version 3.7.289 (6.10.23) =====

==== Supplier article pool in the other node  ====

The supplier article pool can be used across nodes. I.e. the article data from one node can be used in another node. 
be used in another node. For this purpose, the properties in the node define from which node the articles are to be used and saved. This functionality
is possible for the following actions/job steps:
  * TradeItemManagerDirectSql,
  * TradeItemManagerFillCache/TradeItemManagerBookCache,
  * ArticleSubscriptionSelectorDirectSql and
  * TradeItemSelectorDirectSql

==== Supplier article pool - CustomObject ====

=== Job-Step TradeItemManagerDirectSql ===

The Job-Step [[en:prozessdefinition:jobs:jobsteps:supplier:deprecated:tradeitemmanagerdirectsql|]]  has been extended by the option "Article CustomObject" to update the CustomObjects.

=== Mapping functions GetArticleDetailsByEAN and GetArticleDetailsByArtNumber ===

Extension of the mapping functions [[en:transformation:mappings:funktionen:abfragefunktionen:get:getarticledetailbyean|]] and[[transformation:mappings:funktionen:abfragefunktionen:get:getarticledetailsbyartnumber|]] to load the CustomObjects.

==== Extension of the eBiss API ====

Extension of the interface IEnvironment by the method:
<code c#>
void ChangeExecutionNode(INode node);
</code>

For changing the job execution to a sub-node. Application example in the web service:
<code c#>
[OperationContract, WebInvoke(Method = "POST", UriTemplate = "/ExampleCall?subNodeName={subNodeName}&data={data}")] 
public ExampleResponse ExampleCall(string subNodeName, string data)
{
  ExampleResponse rv = new ExampleResponse(HttpStatusCode.InternalServerError);

  using (WaitForInitialization())
  {
    if (string.IsNullOrWhiteSpace(subNodeName) == false)
    {
      INode subNode = Application.Node.SubNodes.Where(n => n.Name == subNodeName).First();
      if (subNode != null) RunningJob.ProcessEnvironment.ChangeExecutionNode(subNode);
    }

    Document = EntitiesBase.CreateJsonImporter().ImportInstance<ExampleRequest>(data);

    if (WaitForMessageCreated())
    {
      rv = new ExampleResponse(HttpStatusCode.OK);
    }
  }
  return rv;
}
</code>
By calling **ChangeExecutionNode** (see code above) the message from the backend is created in the sub-node and job execution continues in the sub-node.

==== SFTP Chanel ====

When logging off after transferring files via SFTP, the error could occur that the connection is already closed. This is no longer reported as an error. 

==== Tasks for new entries in lookup tables ====

When calling the mapping function **LookupGlobalValue**, too many tasks were created for new entries. This error has been corrected.
Furthermore, the property **Tasks for new entries** was added to the lookup table type,
which can be used to control whether tasks should be created. The value is not active for newly created lookup table types. 
So that the behaviour of the current systems does not change, the value is active for the existing lookup table types.