1.1 Changes in ARTS POSLog XML
These changes could affect subscribers of ARTS POSLog XML. Information should be sent to integrated applications before upgrade.
Version | Description |
3.0.0.122 | GrandTotals in ARTS XML End of Day Receipt (Work ID: 189492) GrandTotal and GrandTotalNegative values from EOD POSLog are mapped to two new fields GrossPositiveAmount and GrossNegativeAmount in ARTS XML. (standard fields) |
3.0.0.121 | Historical article and tender lines in ARTS POSLog XML (Work ID: 189492) New parameter has been added to ArtsConfigParams: "RemoveHistoricalArticleAndTenderLines". If set to True, historical tender and article lines (with quantity and amount = 0) will be removed from ARTS XML when converting a customer order with refunded or returned items. |
3.0.0.11902 | Concession sale in ARTS XML (Work ID: 186253) The concession flag in POSLog XML (isConcession) is also included in ARTS POSLog XML in standard field "CommissionGivenFlag". |
3.0.0.11805 | Concession sale in ARTS XML (Work ID: 186253) The concession flag in POSLog XML (isConcession) is also included in ARTS POSLog XML in standard field "CommissionGivenFlag". |
3.0.0.118 | Treatment code in ARTS POSLog XML (Work ID: 177446) Treatment code (Action_LineItem) from POSLog XML was added to ARTS POSLog XML as an extension for item transactions. The new parameter IncludeActionCodeExtension was added to JournalService (in ArtsConfigParams). It is set to False by default. When it is switched to true, the action code from POSLog is included in ARTS POSLog XML. |
3.0.0.115 | Alpha numeric external order number in ARTS POSLog XML (Work ID: 171870) Added support in ARTS receipts for alphanumerical external order number. Example:  The extension is configured in parameter UseExternalOrderNumberExtension. |
3.0.0.113 | Member benefits in ARTS POSLog XML (TFS: 157305) We have added LRS extensions for member benefits in ARTS POSLog XML. |
1.2 Supported POSLog XML version by product
Subscriber | Supported POSLog XML version |
Chain Classic 2.1.1.01 - 2.1.1.07 | 66 |
Chain Classic 2.1.1.08 - 2.1.1.25 | 75 |
Chain Classic 2.1.1.26 -> | 81 is recommended |
Reporting v.50 - v.52 | 70 |
Reporting v.53 - v.55 | 71 |
Reporting v.56 - v.57 | 73 |
Reporting v.58 | 74 |
Reporting v.59 - v.60 | 75 |
Reporting v.61 - 64.1 | 76 |
Reporting v. 65 - 66 | 77 |
Reporting v. 67 - 70 | 79 |
Reporting v. 71 - 74 | 81 |
Reporting v. 75 -> | 82 |
Lindbak Bridge 3.5 | 47 |
Bridge 3.10.1 -> | 66 |
Chain Web | The required version of Chain Web for a specific POS version will always support the latest POSLog XML version. |
1.3 Important technical info when upgrading
The table below describe changes that lead to specific handling when performing the upgrade.
Version | Description |
|---|---|
3.0.0.118 | POSLog XML envelope for subscribers (Work ID: 179561) We've fixed an issue where using OutputFormat other than LRSPosLog on POSLogBatch subscriber would result in an extra envelope around the actual poslog when sending to the subscriber. This would mean you could only use this subscriber with LRSPosLog, and the actual output when using that output format, was not just the POSLog. With the improvements we've made, you can now choose which output format you want, and the output will be according to the configuration, instead of having a hardcoded override of the config. When upgrading JournalService to 3.75.164.0 or newer, the OutputFormat parameter for POSLogBatch subscribertype needs to be changed from LRSPOSLog to LRSPOSLogWithDataHolderGz for existing users. Otherwise the receipts will fail during processing in Azure. SkipTransform should also be set to false(default), but default version should be -1. |
3.0.0.116 | Requires .Net Framework 4.7.2 or higher POS Server must have .Net Framework 4.7.2 or higher to upgrade to 3.0.0.116. |
Please check documentation in Word for changes in older versions than 113. |