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

The Job-Step TradeItemManagerDirectSql has been extended by the option „Article CustomObject“ to update the CustomObjects.

Extension of the mapping functions GetArticleDetailsByEAN andGetArticleDetailsByArtNumber to load the CustomObjects.

Extension of the interface IEnvironment by the method:

void ChangeExecutionNode(INode node);

For changing the job execution to a sub-node. Application example in the web service:

[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;
}

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.

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.

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.