Current Release¶
What’s new or changed in EDI 3.2025.5.5
Release Version: 3.2025.5.5
Release Date: 2025-05-15
Total # Work Items: 18
Features¶
This section contains a table that lists the features that are included in this release when available. We might update this article to include features that were added to the build after this article was originally published.
| ID | Title |
|---|---|
| 3218 | Add table name and record identification to the event records |
| 3219 | Make it possible to ‘export’ electronic report on trigger by event record |
| 3230 | Make it possible to specify the wanted HTTP method on the processor |
| 3240 | Telemetry add more to other locations |
| 3262 | Copy the error log from DMF export to the smart connect log (and queue) |
| 3272 | Move retries to processes |
| 3504 | Make it possible to add a path for a fileshare to each label layout |
| 3506 | Link smart connect created records in FO with the message id in the queue for follow up purposes |
| 3521 | Add if not exist, create - parameter to connecter |
| 3552 | Add more dedicated security privileges |
| 3672 | OAuth Token Cache |
Bugs & Fixes¶
This section contains a table that lists the bugs and fixes that are included in this release when available. We might update this article to include features that were added to the build after this article was originally published.
| ID | Title |
|---|---|
| 3242 | Telemetry parameter record not found |
| 3257 | Max Retries - unwanted behaviour |
| 3259 | Infolog empty after read |
| 3270 | Event retry on queue looping |
| 3509 | HttpStatus Created/Accepted seen as failure |
| 3586 | SFTP Setup and non-certificate support |
| 3593 | Telemetry newFromEventIdName method is obselete |
Detailed Notes¶
This section contains the workitems mentioned in the above sections, with additional details and applicable notes
3218¶
- Title: Add table name and record identification to the event records
- 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
- 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.
3230¶
- Title: Make it possible to specify the wanted HTTP method on the processor
- 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
- 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
- Type: Bug
- Notes: The bug regarding the initialisation has been resolved.
3257¶
- Title: Max Retries - unwanted behaviour
- Type: Bug
- Notes: The unwanted behaviour for the retries is resolved.
3259¶
- Title: Infolog empty after read
- 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)
- 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
- Type: Bug
- Notes: The bug of the event retry on queue looping is resolved
3272¶
- Title: Move retries to processes
- 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.
3504¶
- Title: Make it possible to add a path for a fileshare to each label layout
- 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.
3506¶
- Title: Link smart connect created records in FO with the message id in the queue for follow up purposes
- 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
- 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
- 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
- Type: User Story
- Notes: Some more dedicated security roles and privileges were added.
3593¶
- Title: Telemetry newFromEventIdName method is obselete
- Type: Bug
- Notes: This method is removed
3672¶
- Title: OAuth Token Cache
- Type: User Story
- Notes: The option to cache the OAuth Token was added, the Token will only be renewed upon expiration.