Versie 16.2.0 MplusKASSA Q-line 16.2.0

Releasedatum:
27-06-2019

  • De naam van een prijsgroep kan nu weer gewijzigd worden.

  • Modern stijl icoon ingesteld voor de autorisatieknop op de medewerkerkaart in raadplegen modus.

  • Rechtengroepen kopieren van de ene medewerker naar de andere werkt nu weer.

  • Probleem verholpen waardoor als er met een NetPay-kaart betaald werd het kon gebeuren dat automatisch een deelbetaling gedaan werd. Dit ging alleen mis als de deelbetaling optie en "Direct gepast betalen" optie aan stonden en de NetPay-kaart onvoldoende saldo had.

    In deze versie is tevens de configuratie van de NetPay koppeling verhuist. Deze staat niet langer onder Beheer > Instellingen > Hardware > Pinautomaat maar staat nu onder Beheer > Instellingen > Instellingen > Koppelingen > Netpay.

  • Webhooks: It is now possible to send a customerMessage of two lines to the customer display. The second text line can be separated from the first by a newline-character: \n

  • Webhooks: It is now possible to use messageDisplayTime and customerMessageDisplayTime to pass through a delay time after which the transmitted message or customerMessage respectively will be hidden from view again.

  • Webhooks: It is now possible to respond with a prepayTable property. This can be used to do a prepayment on a table order.

  • Webhooks: It is now possible to respond with an externalCardScan property. This can "simulate" an actual card scan from the POS, with a specific balance and other card details. The card details will be displayed on the POS screen and the customer display, as part of the totals underneath the virtual screen receipt.

  • In the list of purchase orders, the column Delivery Date is now marked red when the date has expired.

  • Webhooks: In case of a manual cancellation of an externalPayment flow, there will be no separate notification of this fact to the webhook endpoint. This is because as part of the externalPayment flow, there will always be a requestCancelExternalPayment that follows the manual cancellation, which basically carries the same message for the endpoint (namely that the payment should be cancelled).

  • It is now possible to lock the session solely for additions (you can still reduce amounts on the session). To trigger this behaviour, respond with the property lockSessionForAdditions in the JSON reply.

  • A new settings has been added that can be used to enable the button "Increase amount" on the line popup.

    Under the settings group "POS" a new subgroup "Receipt (virtual)" has been added that contains settings specifically related to the look and functionality of the screen-based receipt.

  • Webhooks: It is now possible, in a reply where you return a message or customerMessage, to use the property displayTime, messageDisplayTime or customerMessageDisplayTime to set a minimum amount of seconds that you want the message to stay on screen. This can be useful when the POS has been configured to remove the webhook popup as soon as possible, but you still want to display an important message to the user. This setting delays the hiding process with the set amount of seconds.

  • New webhook, backgroundPoll, which is called continously while the software is running.


    Meer info »
  • New webhook, printBill, which is called when printing the bill of a table.


    Meer info »
  • Optie toegevoegd aan het keukenscherm om tussen de weergave met één of twee rijen te kunnen wisselen. Hiermee komt de instelling voor 'Extra rij' te vervallen.

  • Bij afdrukken op bon worden lange tekstvelden in de kop of voet nu automatisch afgebroken.

  • Webhooks: When an article with a question-price is added through lineAdditions, but a price is also included in the response, the price-popup will no longer be shown. wordt met een vraagom-prijs, maar er wordt ook direct een gewenste prijs meegegeven, dan wordt de vraagom-popup nu niet meer getoond.

  • Webhooks: In case of a manual cancellation of a webhook, there will no longer be an error message sent to the POS interface telling the user that the webhook is cancelled. Because the user already knows this, since they were the one that initiated the cancellation manually.

  • Solved an issue where the webhook popup would show earlier than expected (earlier than the configured delay time). The popup will now also be hidden when the webhook responds with a dialog. And after answering the dialog, it will be shown again only after the configured delay time has elapsed again.