EDI v4.0.0
Version Number | 4.0.0 |
|---|---|
Release Date | 14/07/2021 |
Other Application Requirements | VW v6.1.0 |
Warnings or Notices | Receiving files using email is to be withdrawn on 31/12/2025 and no further sending using email will be tested beyond 31/12/2022 to see available methods of sending please look at the information in https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/547586120/EDI+Specifications#Transmission-Methods |
Issue key | Summary | Issue Type | Affects versions | Description |
VEDI-917 | Excise & VAT summary - VAT status | Report | 3.12.4 | VAT status has been moved from the details to the W5(D) header section to make this clearer when VAT is displayed as 0 (which now applies to both ACQ & PVA records). This has allowed more space in the details section to expand the product description and reduce the number of pages the document needs. |
VEDI-851 | API - all services available | New Feature | 3.8.5.1 | File transmission support will be deprecated from this point forwards, all messages will now be possible to submit and receive via the EDI API using XML format. All documentation for consuming the API is published in: API Documentation The existing approval process for integrations continues to apply. Existing “sending XML via email” method will end support 20/07/2024 This item requires a license along with customer token and configuration in order for it to work. |
VEDI-947 | Orders - collection/pick date calculation | Improvement | 3.13.0 | Changes required in VEDI for collection order pick date / time calculation changes introduced in VW-5305. |
VEDI-946 | POC - carrier consignment number | Improvement | 3.12.0 | Added the carrier consignment number added to the proof of collection XML - this way any orders that have been despatched via an integrated carrier solution in Vision (i.e Yodel/APC) can be returned back to the customers upon despatch. |
VEDI-941 | Ordering - order date | Improvement | 3.13.0 | Orders with an order date within the past week will have their date auto set to today, and validation added that if the order date earlier than this then it will fail validation. |
VEDI-900 | API - Specific Request Parameter | Improvement | 3.11.0 | Add an optional 'Document Ref' parameter to the Order Picking Confirmation API and 'PO No' to the Goods Received API, allowing customers to retrieve the data for a specific order, ignoring the flag which the system usually uses to identify if the order has already been sent out in an OPC / GR message. |
VEDI-884 | Intravision PO - now unlicensed | Improvement | 3.10.7 | With the major API improvements introduced in this version, the previously licensed intravision PO (which allows pre advice data to be passed electronically between Vision warehouses) is now available to all customers to use, so any intravision data received in your system can be processed. We will phase in the sending of this information from other systems again throughout the year. |
VEDI-875 | Issue manager - API enhancements | Improvement | 5.0.0 | Enhancements to the API to improve integration with Vision Issue Manager (issuemanager.uk). |
VEDI-848 | API - Rate limiting | Improvement | 3.8.5.1 | Improvement of rate limiting in the API where http response code 429 will be returned to the caller when they exceed the rate limit. See [https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/505544776/Service+new+version+available+May+2021|https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/505544776/Service+new+version+available+May+2021|smart-link] for more information on the limits imposed. |
VEDI-841 | API - OrderStatusByDocRef new fields | Improvement | 3.8.5 | The following fields will be added to the OrderStatusByDocRef service response:
Booked Date - BDT Confirmed Departed - CDP Confirmed Delivered - CDL |
VEDI-822 | Incoming orders - mandatory collection fields | Improvement | 3.8.3 | Validation that the following fields have been populated for collection orders, based on the CollectionDeliveryArea (Collection Group):
Will lookup the 'Order collection fields mandatory' in VW to see if these are required, if not the order will be sent to validation failures. |
VEDI-746 | Ordering - Delivery notification emails | Improvement | 3.7.2 | VEDI supports 2x fields to specify email addresses for customers to receive delivery notifications:
Vision Warehousing only previously supported one of these (the delivery point email), the additional field was added in [VW-4338] and this issue handles the VEDI changes required to finish this. |
VEDI-730 | API security & status codes | Improvement | 3.7.0 | Changes will be made to enhance the API security by introducing token authentication, available for new and existing services. As customers have already integrated with existing services, they will be able to continue using them with the existing authentication mechanism however they must be encouraged to switch over to using the token authentication for them and it’s imperative to do so when developing their applications for the new services published. At the same time, the responses given by the API will also be improved to return the http status code, making it easier for consuming applications to interpret the API response. |
VEDI-662 | Outgoing reports - No recipients | Improvement | 3.6.0 | Modification to the housekeeping job which will automatically deactivate report schedules with no VW contacts setup to receive them, optimising system performance. |
VEDI-534 | API - Integrate POCs into the POD service | Improvement | 3.4.0 | Modifications made to the POD service to also handle POCs. |
VEDI-944 | Order save - no rotation for transfer order | Bug | 3.13.0 | When a transfer order is sent to EDI without a rotation number, it incorrectly appears in Validation Failures as a timeout error. |
VEDI-938 | Pre advices - submitting amendments | Bug | 3.12.3 | When customers submit a PO multiple times (with amendments for example) these result in duplications in VW, changes were previously made to ignore / update existing records but this does not appear to be happening in all instances. |
VEDI-931 | Incoming permissions - VCIS files | Bug | 3.12.4 | Improvements on the security of incoming VCIS files, when incoming permissions are enabled and any file is received from VCIS, the initial checks pass but at the second stage of breaking down the file into individual records, it fails here because the customer within the file doesn't have the permissions setup which they never will. |
VEDI-930 | Incoming files - invalid extensions | Bug | 3.12.0 | Invalid extensions are now going to be checked before a file is loaded into EDI. |
Copyright Ontech Solutions 2017-2024. All rights reserved, no part may be replicated or distributed without the express permission of the owner.