These are the notes from the latest version of the system.
Here you will be able to view the documentation showing all changes that have been made to Vision Commerce.
...
| Info | ||
|---|---|---|
| ||
Existing customers on v2.13 or v2.14 will be entitled to upgrade to v3 with only standard upgrade charges until 31 December 2020 (where their live system must be on the latest version) SQL Version will be v2016 or later for this release of Commerce |
Testing Vision
Suggestions for how to test vision are contained on the following page Testing Vision
It is important for customer to test their basic functionality before signing the release to install to live, this should include items within the Sales Administration menu.
Previous Versions are linked below
| Child pages (Children Display) |
|---|
...
| Version | 3.2.0 |
|---|---|
| Release Date | 28/02/2020 |
| Other Application Requirements | Running the latest version of the Microsoft .NET Framework for the new 'Vision Suite Launcher' See the REQUIRES column |
| Warnings or Notices | Sage Line 50 v26 (2020) will be the last supported version of Sage Line 50, customers are encouraged to consider migrating to Xero / Sage cloud platforms. For customers switching to cloud accounts platforms, please speak to the support team for further information When upgrading to this version, please update the new email address field within 'Warehouse Group Maintenance' to receive the regular PDF files by email. |
| Issue key | Summary | Issue Type | Description | Linked Issue | Configuration Needed | Requires |
|---|---|---|---|---|---|---|
| VC-2109 | SOP, POP & Producer - Attachments | New Feature | Our attachment manager application has been incorporated into VC allowing all types of documents and images of your choice to be stored against purchase orders, sales orders and producers and recalled at any time. | RFC-631 | YES | |
| VC-2078 | Horizon - maintenance | New Feature | Horizon - the ePOS solution Changes to the User / Group maintenance screen to allow users to maintain devices & users for our new ePOS system, Horizon. Wiki updated - [https://visionsoftware.atlassian.net/wiki/spaces/VC/pages/569311303/Frequently+Used|https://visionsoftware.atlassian.net/wiki/spaces/VC/pages/569311303/Frequently+Used|smart-link] | VC-1740 | No | |
| VC-1928 | Product Images + Web API | New Feature | Photos / images can now be uploaded in Product Maintenance which are also available in the Price List PDF output. Each image will be categorised, we store one image per each category (note: historical images of the same product for the same category are not retained): * Case shot * Single Shot * Multi Single shot * Front Label * Back Label * Additional Label * Capsule API [https://visionsoftware.atlassian.net/wiki/spaces/VC/pages/526549234/Outbound+Web+API|https://visionsoftware.atlassian.net/wiki/spaces/VC/pages/526549234/Outbound+Web+API|smart-link] * The existing Web CSV exports are now also available via the API in a slightly different format offering more information. * Images are also available from API from a new service. * Producer information is also available direct from VC via the API now, with producer images too which can be uploaded through VC using the attachment manager screen. * In API maintenance, ‘General’ add field ‘Producer Image Attachment Type’ with a combobox allowing the user to choose which user defined attachment type the API will retrieve for producer images. The license options for electronic integration with VC have changed as follows, customers may use any one of the following options: # “API In” - Utilisation of the VC API to post orders into the system electronically, plus the existing Web CSV for data exported from VC to your website. # “API Standard Limited” - APIUtilisation of the VC API to post orders into the system electronically, plus the API to extract data from VC in the same way, limited to a single daily request. # “API Enhanced Limited” - Option 2 above plus access to the product image download API service (real time, no daily request limit). # “API Enhanced” - Option 3 above without limits providing realtime information direct from VC to your website. Wiki updated - [https://visionsoftware.atlassian.net/wiki/spaces/VC/pages/548143290/Product+Creation|https://visionsoftware.atlassian.net/wiki/spaces/VC/pages/548143290/Product+Creation|smart-link] | YES | Require, INS 1.1.1 HZN 1.0.2 | |
| VC-2207 | Xero accounts - postings | Issue | Various errors when posting to accounts system | No | ||
| VC-2178 | Purchase Order - non latin | Issue | The pickup address fields do not support non latin characters, and these are defaulted from the supplier which does. | No | ||
| VC-2185 | BI Enquiries - improvements | Improvement | 201 - Addition of standard product sales price/case and single 301 - Product description has been expanded | No | ||
| VC-1985 | Allocation screen | Improvement | Improvements to the Allocation Screen Please see wiki page - [https://visionsoftware.atlassian.net/wiki/spaces/VC/pages/552960013/Processing|https://visionsoftware.atlassian.net/wiki/spaces/VC/pages/552960013/Processing] Allocation tab. Allocation screen improvements # new button 'Commit Green' will commit only those which are GREEN (perhaps put a matching green colour somewhere in the button too) # new button 'Commit Yellow' will require you to select a specific line and it will commit just that single line (perhaps put a matching yellow colour somewhere in the button too). # Existing Commit renamed as “Commit Selected” will require a specific order to be selected for committing and can be used for any colour of order # A refresh button will be added to the form # A warning about the risks with multiple allocators for the same group will be added - text line only “Multiple user warning: Ensure only one user has this screen open at a time“ # Closing the form will automatically unallocate the lines waiting for the next time you run the allocation (unallocate means undo any data changes done to the DB if the ‘allocate’ buttons have been used). # Transfer PO’s will no longer be created at allocation stage, instead at delivery (from [https://visionsoftware.atlassian.net/browse/VC-2065|https://visionsoftware.atlassian.net/browse/VC-2065|smart-link], see [https://visionsoftware.atlassian.net/browse/VC-1986|https://visionsoftware.atlassian.net/browse/VC-1986|smart-link] too. # Do [https://visionsoftware.atlassian.net/browse/VC-1986|https://visionsoftware.atlassian.net/browse/VC-1986|smart-link] first, then from [https://visionsoftware.atlassian.net/browse/VC-1908|https://visionsoftware.atlassian.net/browse/VC-1908|smart-link] “At the time of allocation have an option where a warehouse does not use files to confirm delivery that those being allocated are considered delivered with no need to confirm delivery“. So use the same queries as we have in the deliver orders screen which will automatically deliver orders as well, but only if new ‘Optional Feature’ “Deliver” is ticked. # Send design changes to JW for approval prior to release. | VSUP-12764 | No | |
| VC-1693 | Sales order - customer search screen | Design Change | A customer search screen opens immediately when opening the order screen, this will no longer happen but be available by pressing F10 in the customer code field. [https://visionsoftware.atlassian.net/wiki/spaces/VC/pages/552632364/Sales+Order+General|https://visionsoftware.atlassian.net/wiki/spaces/VC/pages/552632364/Sales+Order+General|smart-link]Â | VC-1692 | No | |
| VC-2194 | Supplier- Hold | Change | In some scenario, tblVisionSupplier.OnHold updated null value. Which causes error loading the supplier. | No | ||
| VC-2192 | Whse submission - Sales price | Change | The sales price will be expanded to allow higher values on the interface to the warehousing system. Previouly 8 including upto 3 after the decimal, now 18 including 3 after the decimal | No | ||
| VC-2171 | SOrder Invoice- Multiple payment method | New Feature | Horizon - the ePOS solution Is now able to handle multiple payment methods on a single sales order | No | ||
| VC-2203 | Whse submission - rtn line no | Bug | If a rotation is specified in SOP and the rotation includes a line number, the line number is being submitted in both the dedicated line number field and also the rotation number, causing the order to fail validation. | VSUP-12688 | No | |
| VC-2188 | Navigation - Search (non latin) | Bug | Sales Order - 'Search Customer' non latin characters When do a customer search with Chinese character in a sales order , It returns nothing | VSUP-12576 | No | |
| VC-2186 | Group maintenance - NEW | Bug | Error when adding a new group into the group maintenance | VSUP-12783 | No | |
| VC-2159 | Sales total - ignoring discounts | Bug | This affects the Customer Product Sales Period Comparison report, in the back end the 'Total Ex VAT' is ignoring discounts making the report values displayed incorrect. | VSUP-12845 | No |
| Version | 3.1.0 |
|---|---|
| Release Date | 10/02/2020 |
| Other Application Requirements | Machines should be running the latest version of the Microsoft .NET Framework for the new 'Vision Suite Launcher' to function. |
| Warnings or Notices | Sage Line 50 v26 (2020) will be the last supported version of Sage Line 50, customers are encouraged to consider migrating to Xero / Sage cloud platforms. For customers switching to cloud accounts platforms, information will either be published on the wiki guiding you through this or be available from the support team. When upgrading to this version, please update the new email address field within 'Warehouse Group Maintenance' to receive the regular PDF files by email. |
...