eBiss 3

When reading the variables in BackendObjectTransmitter and BackendObjectTransmitterEx, some of the variable names were converted to lowercase letters, but not the ones set in the job step. This could lead to duplicate entries.

The error has been fixed; the variable names are now evaluated uniquely, regardless of upper/lower case.

The EDI reference from the cover can now also be set in the mapping using the Frame Variable eBiss.DocumentVars.InterchangeReference:

SetTargetFrameVariable('eBiss.DocumentVars.InterchangeReference', $MyEdiReference)

Further information on setting the EDI reference can be found at: EntityMessageCreator.

In the SetJobVariable funciton, an XPath expression can be specified as the value, e.g.:

 SetJobVariable('CallWebService', /ExampleRequest/@WebServiceName)

The use of node variables is possible from:

• BackendObjectRetrieverEx and
• BackendObjectTransmitterEx.

The usage is described under Variables of the above-mentioned backend objects.

Variables and Masks can be used in AS2- and Harddisk receive channels.

See also the note “Use of masks in receive and send channels” in:

• Harddisk receive channel,
• AS2 send channel and
• AS2 receiving channel.

Extension of the JobStep ChannelSender by the property ‘Use TypeSet from’ with the following possible values:

• Do not use
• Receiver
• Sender
• Sender or receiver

The Job Step RemoveArticleDetails encountered an error when cleaning up the article data. This error has been fixed.

In the ‘Amazon S3 receive channel’ and ‘Amazon S3 send channel’, the fields for the “AWS Access Key” and the “AWS Secret Access Key” have been converted into password-protected fields, which allows the values to be encrypted and visibility to be restricted via permissions.

If encryption is enabled, the data will only be encrypted in the database when it is saved from this version onwards. This means that Amazon S3 channels created before this version will be hidden as password fields on the interface from this version onwards, but will remain unencrypted in the database until the next save.

When bundling requests in web services Web service request bundling and creating a message in the web service via CreateOutputMessage, a MessageCreated() call is required at the end. The MessageCreated() method has been revised.

Changes to the GLN of the main location in the editing window now also cause it to be updated in a parallel open list of partners.

New mapping funktion GetInterchange.

Introduction of a new category of mapping functions: Changes to existing messages and documents.

New mapping functions ChangeMessageState and changefilename.