History

Including all features, bugs and fixes released up until 3.2025.8.3

Features

This section contains a table that lists the features that were included in our releases. This article will be update with each release.

Release Version	ID	Title
-	2654	DMF export incremental on multi entity
-	2786	Creation of new Classe for Importing Peppol E Invoice Romania
-	2894	Azure File Share move file with same name
-	2842	“Is purchase order” and “Purch Id” validation on import
-	3105	Babelway connector
-	3106	POC - E-invoicing
-	3223	Make it possible to add Raptor generated document to ER
-	3505	Make Tungsten invoice inbound base handler
-	3217	Make UBL invoice inbound API based handler
-	3503	Store outbound ER UBL Sales invoice and UBL project invoice in Raptor
3.2025.5.5	3504	Make it possible to add a path for a fileshare to each label layout
3.2025.5.5	3218	Add table name and record identification to the event records
3.2025.5.5	3219	Make it possible to ‘export’ electronic report on trigger by event record
3.2025.5.5	3506	Link smart connect created records in FO with the message id in the queue for follow up purposes
3.2025.5.5	3521	Add if not exist, create - parameter to connecter
3.2025.5.5	3552	Add more dedicated security privileges
3.2025.5.5	3672	OAuth Token Cache
3.2025.5.5	3230	Make it possible to specify the wanted HTTP method on the processor
3.2025.5.5	3240	Telemetry add more to other locations
3.2025.5.5	3262	Copy the error log from DMF export to the smart connect log (and queue)
3.2025.5.5	3272	Move retries to processes
3.2025.3.1	3107	Add Telemetry to smart connect
3.2025.3.1	3137	Add data entities for smart connect (Connectors and Processors)
3.2025.3.1	3138	Create data entity to export/import process configurations
3.2025.3.1	3140	Create a clean up job to automatically delete records in the queue after a specified time range
3.2025.3.1	3166	DMF import upgrade
3.2025.3.1	3198	Updated logging levels
3.2025.3.1	3098	Add the GLN number to the address
3.2025.3.1	3126	Add a privilege to send smart connect messages into the queue
3.2025.2.1	3096	Queue UI and UE upgrades
3.2025.2.1	3112	Add printer specific text to outgoing labels
3.2025.2.1	3114	Add API authorisation type to include audience
3.2025.1.4	2962	Upgrade Queue UI en UE
3.2025.1.4	2963	Add more flexibility to the outbound configuration
3.2025.1.4	3014	Add external service smart connect option for label printing (e.g. BarTender integration)
3.2025.1.4	2956	Create business event when a message in the queue fails
3.2025.1.4	2889	Move certain variables to the connecter
3.2024.9.1	2686	DMF import did not run
3.2024.8.7	2593	EDI - Report license variable and pipeline update
3.2024.4.1	2307	Extension issues on data processors
3.2024.4.1	2314	DMF entity name on export too short
3.2024.11.6	2809	Readsoft connecter
3.2024.10.5	2767	AS2 protocol
2022	2548	FTP/SFTP connector
-2146826246	2359	DMF export no staging computed column empty file
-2146826246	2579	NANVendTable and NANCustTable DeleteAction

Bugs & Fixes

This section contains a table that lists the bugs and fixes that were included in our releases. This article will be updated with each release.

Release Version	ID	Title
	2904	Import UBL object not set to a reference
	2957	RO object not set to the instance of an object import (DMS)
	3087	File name bug for reprocessing processor using the NANHandlerInDMSUbl_RO handler (DMS)
	3224	DMS RO import failes due to missing node ‘InvoiceTypeCode’
	3248	Missing node ‘InvoiceTypeCode’ for NANHandlerInDMSUbl_RO
3.2025.5.5	3509	HttpStatus Created/Accepted seen as failure
3.2025.5.5	3586	SFTP Setup and non-certificate support
3.2025.5.5	3593	Telemetry newFromEventIdName method is obselete
3.2025.5.5	3242	Telemetry parameter record not found
3.2025.5.5	3257	Max Retries - unwanted behaviour
3.2025.5.5	3259	Infolog empty after read
3.2025.5.5	3270	Event retry on queue looping
3.2025.3.1	3135	Re-processing failed DMF import (non excel) in the queue not working
3.2025.3.1	3163	Manual Reprocessing when max amount of retry not possible
3.2025.3.1	3187	Name of exported files when multiple data entities in one project is wrong
3.2025.3.1	3188	Process out event looping and queue
3.2025.3.1	3192	Retry count issues
3.2025.2.1	3133	Label printing through processor not working from document routing
3.2025.2.1	3101	File not moved to FailDirectory of SuccessDirectory when using SAS Credential
3.2025.2.1	3092	Label changes
3.2025.2.1	3094	Message content changes can not be saved
3.2025.2.1	3108	API Connection failed on ER OUT processor
3.2025.2.1	3109	Authorization types (API, Storage account, …) Not cleared when changing connector type
3.2025.2.1	3120	Parent Path Error when directory doesn’t exist (ER - OUT handler in combination with a Fileshare)
3.2025.2.1	3122	failed XML (import or export) can sometimes not be reprocessed
3.2025.1.4	2965	issues with the processors which were using the “Use Queue” parameter
3.2025.1.4	2966	9A Smart Connect missing label for license report usage
3.2025.1.4	3004	Empty error message when error is thrown in event processing
3.2025.1.4	3037	Strange behaviour when DMF import
3.2025.1.4	3038	When DMF import process message is in error in the queue, and the same processor is triggered, its runs infinitely
3.2025.1.4	3048	Auto Create directories if not exist in DMF export
3.2025.1.4	3050	When reprocess an failed DMF export message (non excel) The name of the export file is wrong
3.2025.1.4	3052	Filter on top of page is not working when a view is saved with another sort by column
3.2025.1.4	3059	File share SAS credentials fail on instantiation
3.2025.1.4	2950	Connector setup issue
3.2024.12.1	2869	Lookup on Connecter key vault value not working
3.2024.12.1	2880	Move to failure folder not working
3.2024.11.6	2829	Object reference not set to an object error
3.2024.10.5	2733	Dll update for version 41

Detailed Notes

This section contains the workitems mentioned in the above sections, with additional details and applicable notes

2894

• Title: Azure File Share move file with same name|
• Release:
• Type: User Story
• Notes When exporting or copying files to Azure file storage you may have a file that was previously processed with the same name and as such the system fails to copy or export the file 

2904

• Title: Import UBL object not set to a reference|
• Release:
• Type: Bug
• Notes When importing an invoice where there is no ID for the OrderReference the ID is therefore null causing the error. Check if the ID on the OrderReference exists before reading the value. 

3087

• Title: File name bug for reprocessing processor using the NANHandlerInDMSUbl_RO handler (DMS)|
• Release:
• Type: Bug
• Notes Now, when reprocessing a failed import with the processor using the NANHandlerInDMSSUbl_RO handler, the correct reference name is used. 

2842

• Title: “Is purchase order” and “Purch Id” validation on import|
• Release:
• Type: User Story
• Notes If there is an order reference present in the invoice then set the IsPurchaseOrder to Yes. When importing with order references that do not exist as purchase orders then leave the field empty. Auto matching after import activated
  

3505

• Title: Make Tungsten invoice inbound base handler|
• Release:
• Type: User Story
• Notes It is now possible to use smart connect to get the Kofax invoices in the all invoices table of raptor. There is a dedicated connector type and a dedicated handler for this. 

3217

• Title: Make UBL invoice inbound API based handler|
• Release:
• Type: User Story
• Notes The UBL inbound invoice handler was created based on the UBL sales invoice ER format. This  handler requires the all invoice functionality of raptor to be able to work. 

3503

• Title: Store outbound ER UBL Sales invoice and UBL project invoice in Raptor|
• Release:
• Type: User Story
• Notes It is now possible to store the outbound ER (and embedded pdf) in raptor for the ER type UBL sales invoice and UBL project invoice

3248

• Title: Missing node ‘InvoiceTypeCode’ for NANHandlerInDMSUbl_RO|
• Release:
• Type: Bug
• Notes The node has been added to resolve this issue. 

3504

• Title: Make it possible to add a path for a fileshare to each label layout|
• Release: 3.2025.5.5
• Type: User Story
• Notes It is now possible to add an extension of the base path for each label, this can be done on the label layout form. 

3218

• Title: Add table name and record identification to the event records|
• Release: 3.2025.5.5
• Type: User Story
• Notes It is now possible to see the table name and some record info in the event table. 

3219

• Title: Make it possible to ‘export’ electronic report on trigger by event record|
• Release: 3.2025.5.5
• Type: User Story
• Notes We added a function to export an ER on event trigger, however if not needed we do not recommend to use this as MS is shutting down the access to the ER triggers. 

3506

• Title: Link smart connect created records in FO with the message id in the queue for follow up purposes |
• Release: 3.2025.5.5
• Type: User Story
• Notes By adding the form on the processor, it is now possible to see from that form what queue record created the record in the form. 
  
  Example: 
     A handler creates a sales order (EDI message), on the processor the salestable form is specified. When opening the sales table and navigating to the created sales order, there will be the option under the 9A smart connect Tab to view the queue record that was associated with this sales order. (like this it will be easier to find error if they would occur). 
  
  

3509

• Title: HttpStatus Created/Accepted seen as failure|
• Release: 3.2025.5.5
• Type: Bug
• Notes The bug were HttpStatus Created/Accepted was seen as failure is resolved. 

3521

• Title: Add if not exist, create - parameter to connecter|
• Release: 3.2025.5.5
• Type: User Story
• Notes A parameter on the connector was added to activate the functionality: if Update (PUT) doesn’t work (because the record doesn’t exists) create (POST) the record through the API connection. 

3552

• Title: Add more dedicated security privileges |
• Release: 3.2025.5.5
• Type: User Story
• Notes Some more dedicated security roles and privileges were added. 

3593

• Title: Telemetry newFromEventIdName method is obselete|
• Release: 3.2025.5.5
• Type: Bug
• Notes This method is removed

3672

• Title: OAuth Token Cache|
• Release: 3.2025.5.5
• Type: User Story
• Notes The option to cache the OAuth Token was added, the Token will only be renewed upon expiration. 

3230

• Title: Make it possible to specify the wanted HTTP method on the processor|
• Release: 3.2025.5.5
• Type: User Story
• Notes It is now possible to add an event type triggering different API methods on processing of the event to an API Connector: 
  
  • Insert - POST
  • Update - PUT
  • Delete - DELETE
  • None (empty) - POST

3240

• Title: Telemetry add more to other locations|
• Release: 3.2025.5.5
• Type: User Story
• Notes It is now possible to activate the telemetry per processor (by activating the parameter in he processor setup)

3242

• Title: Telemetry parameter record not found|
• Release: 3.2025.5.5
• Type: Bug
• Notes The bug regarding the initialisation has been resolved. 

3257

• Title: Max Retries - unwanted behaviour|
• Release: 3.2025.5.5
• Type: Bug
• Notes The unwanted behaviour for the retries is resolved. 

3259

• Title: Infolog empty after read|
• Release: 3.2025.5.5
• Type: Bug
• Notes The bug causing the infolog to be empty is resolved. 

3262

• Title: Copy the error log from DMF export to the smart connect log (and queue)|
• Release: 3.2025.5.5
• Type: User Story
• Notes It is now possible to see the error log from DMF in the smart connect queue. The link to the DMF project is also added as a hyper link. 

3270

• Title: Event retry on queue looping|
• Release: 3.2025.5.5
• Type: Bug
• Notes The bug of the event retry on queue looping is resolved

3272

• Title: Move retries to processes|
• Release: 3.2025.5.5
• Type: User Story
• Notes In the previous version the amount of retries was specified in the general parameters, meaning it was for all processors or for none. As the setup of retries will be in most of the cases processor specific this field is is changed to the processor. 

3107

• Title: Add Telemetry to smart connect|
• Release: 3.2025.3.1
• Type: User Story
• Notes Telemetry has been added for the smart connect module. 

3135

• Title: Re-processing failed DMF import (non excel) in the queue not working|
• Release: 3.2025.3.1
• Type: Bug
• Notes Re processing for DMF import after a fail is now possible. (This means you can edit the import file in the queue and reprocess it). 

3137

• Title: Add data entities for smart connect (Connectors and Processors)|
• Release: 3.2025.3.1
• Type: User Story
• Notes Data entities are added to export and import smart connect configurations, the following ones are included: 
  
  
  • 9A Smart Connect - connecters
  • 9A Smart Connect - processor groups
    
  • 9A Smart Connect - processor variables
    
  • 9A Smart Connect - processors
    
  • 9A Smart Connect - queue 
    

3138

• Title: Create data entity to export/import process configurations|
• Release: 3.2025.3.1
• Type: User Story
• Notes A data entity has been added to easily export/import process configurations (the link between customer (group)/ vendor (group) en the processors when using business processes)

3140

• Title: Create a clean up job to automatically delete records in the queue after a specified time range|
• Release: 3.2025.3.1
• Type: User Story
• Notes A clean up job is added to clear the queue for records older than the specified time. 

3163

• Title: Manual Reprocessing when max amount of retry not possible |
• Release: 3.2025.3.1
• Type: Bug
• Notes The bug that blocked manually processing of messages that reached their max retries in the queue has been resolved. 

3166

• Title: DMF import upgrade|
• Release: 3.2025.3.1
• Type: User Story
• Notes If a file is imported but not processed to staging, then the DMF import hangs waiting for a status change. This working has changed now
  

3187

• Title: Name of exported files when multiple data entities in one project is wrong|
• Release: 3.2025.3.1
• Type: Bug
• Notes A bug causing names and extensions for DMF export entities to be wrong when multiple entities are included in one export project has been resolved. 

3188

• Title: Process out event looping and queue|
• Release: 3.2025.3.1
• Type: Bug
• Notes A bug causing an infinite loop has been resolved. 

3192

• Title: Retry count issues|
• Release: 3.2025.3.1
• Type: Bug
• Notes A bug regarding retry counts has been solved. 

3198

• Title: Updated logging levels|
• Release: 3.2025.3.1
• Type: User Story
• Notes Logging is now included on no content and if the data handler indicated a NoGo, previously this was not included. 
  

3098

• Title: Add the GLN number to the address|
• Release: 3.2025.3.1
• Type: User Story
• Notes It is now possible to add a GLN number to the addresses, this can be used for EDI integrations. This fields is also included in the following data entities: 
  
  • Vendors V2
  • Customers V2
  • Customers V3
  • Global address book V2
  • Party postal address V2

3126

• Title: Add a privilege to send smart connect messages into the queue|
• Release: 3.2025.3.1
• Type: User Story
• Notes A privilege has been added to sending messages in the queue (inbound messages) using the following url: resource/api/services/NANProcessServiceGroup/NANProcessInService/setQueue. This means that from now on you can easily only assign this privilege to the users linked to the entra ID shared with the sender of these messages (as processing of them is done in batch by a different user - often an admin user). Working like this increases the safety of the integrations. The privilege is named Process in - set queue (AOT name: NANProcessInSetQueue) 

3101

• Title: File not moved to FailDirectory of SuccessDirectory when using SAS Credential|
• Release: 3.2025.2.1
• Type: Bug
• Notes The bug when import from a fileshare while using SaS is fixed. 

3092

• Title: Label changes|
• Release: 3.2025.2.1
• Type: Bug
• Notes Some spelling mistakes are resolved. 

3094

• Title: Message content changes can not be saved|
• Release: 3.2025.2.1
• Type: Bug
• Notes It is now possible to save changes made to message content in the queue. 

3096

• Title: Queue UI and UE upgrades|
• Release: 3.2025.2.1
• Type: User Story
• Notes The standard view has been changed to display more relevant data. 

3108

• Title: API Connection failed on ER OUT processor|
• Release: 3.2025.2.1
• Type: Bug
• Notes The bug for ER OUT in combination with API connector is resolved. 

3109

• Title: Authorization types (API, Storage account, …) Not cleared when changing connector type|
• Release: 3.2025.2.1
• Type: Bug
• Notes The connector is not taking unrelated columns into account to generate the displayed view. 

3114

• Title: Add API authorisation type to include audience|
• Release: 3.2025.2.1
• Type: User Story
• Notes It is now possible to use an API connection that requires audience for authorisation. 

3120

• Title: Parent Path Error when directory doesn’t exist (ER - OUT handler in combination with a Fileshare)|
• Release: 3.2025.2.1
• Type: Bug
• Notes This bug is resolved by creating the complete directory path on the fly (if it doesn’t already exist). 

3122

• Title: failed XML (import or export) can sometimes not be reprocessed|
• Release: 3.2025.2.1
• Type: Bug
• Notes The issue that blocked the reprocessing has been resolved.  

2962

• Title: Upgrade Queue UI en UE|
• Release: 3.2025.1.4
• Type: User Story
• Notes The queue UI and UE got an upgrade including:
  • Standard queue lay out 
  • Multi select cancel option
  • More filter functionality
  • Better logging layout

2963

• Title: Add more flexibility to the outbound configuration|
• Release: 3.2025.1.4
• Type: User Story
• Notes There is added more flexibility to the outbound configuration: 
  
  On the processor it is now possible to select a business process, that business process is a trigger to place a record in the event table when certain conditions are met. 
  The event contains the record id and the table id of the created record, that reference can be used by the handler on the processor to create an export message.  For now 4 business processes are added: 
  • Sales order confirmation (custConfirmJourTable)
  • Packing slip creation (custPackingSlipJourTable)
  • Sales invoice creation (custInvoiceJourTable)
  • Purchase order confirmation (vendPurchOrderJourTable)
  These business process can be extended. 
  
  There are multiple condition that can be added to trigger, for each customer or vendor it is possible to ‘activate’ the processor by adding a relation between the customer/vendor and the processor, next to that a relation can be made between customer/vendor group and the processor. The processor can also be default on for all vendors/client by setting the Enable for all accounts parameter to yes. 
  
  More information will be provided in the manual. 

2965

• Title: issues with the processors which were using the “Use Queue” parameter|
• Release: 3.2025.1.4
• Type: Bug
• Notes The bug is fixed where in some cases the queue parameter was automatically set to No while Yes was needed.

2966

• Title: 9A Smart Connect missing label for license report usage|
• Release: 3.2025.1.4
• Type: Bug
• Notes The bug where some labels were missing for license report usage is fixed

3004

• Title: Empty error message when error is thrown in event processing|
• Release: 3.2025.1.4
• Type: Bug
• Notes The bug is fixed where empty error messages was thrown in the event processing.

3014

• Title: Add external service smart connect option for label printing (e.g. BarTender integration)|
• Release: 3.2025.1.4
• Type: User Story
• Notes The standard external service instance has been extended with a processor field. 
  This makes it possible to send labels (custom labels, document routing labels, wave labels) to a connector (e.g. Fileshare, Blob, Container, … ).
  This makes it possible to send labels to on premise label processors (e.g. bartender). 
  
  Needed setup: 
  
  • Create a processor that will process the labels
  • Use the NANHandlerOutDR handler
  • Fill in the variable information on the processor that is linked to the selected connector
  • Create an external service definition
  • Create an external service operations
  • The http information is not relevant
  • As ‘request body type’ select Raw
  • As request body (raw)
  • select content type plain/text
  • request body = \(label.body\)
  • For ZPL labels and variable script labels, fill in the previously created service in the print operation en the variables print operation field of the definition
  • For Variables tables the script needs to be filled in. 
  • Create an external service instance
  • Add the previously created definition to the instance
  • Add the previously created processor the the instance 
  • The other information doesn’t need to be filled in
  • Create a label printer
  • Select connection type = External label service
    
  • Select as Label print service instance the previously created external service definition 
  Now on printing to that printer the labels will be placed in the directory of the connector. 

3037

• Title: Strange behaviour when DMF import|
• Release: 3.2025.1.4
• Type: Bug
• Notes The strange behaviour when performing the DMF import is fixed: 
  
  • Files are moved to the correct folder
  • On failed, the state in the queue is changed to Error

3038

• Title: When DMF import process message is in error in the queue, and the same processor is triggered, its runs infinitely|
• Release: 3.2025.1.4
• Type: Bug
• Notes This bug is fixed. 
  
  Note: 
  Using the queue in combination with DMF import/export of excel files is not possible. 

3048

• Title: Auto Create directories if not exist in DMF export|
• Release: 3.2025.1.4
• Type: Bug
• Notes When a directory is specified in the directory path of the processor that doesn’t exist, it is now created on the fly. 

3050

• Title: When reprocess an failed DMF export message (non excel) The name of the export file is wrong|
• Release: 3.2025.1.4
• Type: Bug
• Notes The bug where the name of the export file on reprocessing a failed DMF export record in the queue was wrong is solved.

3052

• Title: Filter on top of page is not working when a view is saved with another sort by column|
• Release: 3.2025.1.4
• Type: Bug
• Notes The bugs with the filter on top of the page are solved.

3059

• Title: File share SAS credentials fail on instantiation|
• Release: 3.2025.1.4
• Type: Bug
• Notes The bug that SAS credentials fails on instantiation for a fileshare is solved.

2950

• Title: Connector setup issue|
• Release: 3.2025.1.4
• Type: Bug
• Notes When a the type of a connector is changed, the previously used credentials are now cleared from the connector table. 

2956

• Title: Create business event when a message in the queue fails|
• Release: 3.2025.1.4
• Type: User Story
• Notes When a record in the queue fails to process (entering the error state), a business event can be send out. This business event can be picked up by a power automate, logic app, … 
  This makes it possible to send communication (email, teams message, etc.) to dedicated persons when the records fails to be processed in the queue. 
  Name of the business event: NANQueueErrorBusinessEvent
  
  Fields included: 
  • BusinessEventId
    
  • BusinessEventLegalEntity
    
  • EventTime
    
  • Info
    
  • Filename
    
  • QueueId
    
  • Direction
    
  
  
  

2889

• Title: Move certain variables to the connecter|
• Release: 3.2025.1.4
• Type: User Story
• Notes Variables are very specific to certain connecters and handlers and as such have been split to the correct classes. This will ensure that no erroneous variables are created  Azure file share requires directories  
  
  But an API does not require directories
  

2869

• Title: Lookup on Connecter key vault value not working|
• Release: 3.2024.12.1
• Type: Bug
• Notes When selecting ‘Use Keyvault’ in the parameters, the connection string field lookup was not applying the dropdown to the keyvalut values. Issue has been resolved

2880

• Title: Move to failure folder not working|
• Release: 3.2024.12.1
• Type: Bug
• Notes When importing files and there are failures the files are not moved to the failure folder, this issue has been resolved