2
When looking at the performance for CPOS here in Norway, I can see that it can take a bit of a time to complete a transaction.
After the last payment is registered then the following happens:
- HardwareStation/LineDisplay/DisplayText
- RetailServer/Commerce/GetFiscalIntegrationTechnicalProfilesBySearchCriteria is called from the POS
- RetailServer/Commerce/GetFiscalIntegrationServiceStatus is called from the POS
- RetailServer/Commerce/Carts()/Checkout is called from the POS
- HardwareStation/PaymentTerminal/Unlock
- RetailServer/Commerce/GetFiscalIntegrationFiscalDocument is called from the POS
- RetailServer/Commerce/SubmitFiscalIntegrationDocument is called from the POS
- RetailServer/Commerce/SaveFiscalIntegrationRegistrationResult is called from the POS
- RetailServer/Commerce/SalesOrders()/GetReceipts
Would it be possible to avoid all this ping <-> pong and make it more like this?
- HardwareStation/LineDisplay/DisplayText
- RetailServer/Commerce/Carts()/Checkout is called from the POS
- HardwareStation/PaymentTerminal/Unlock
Where the "Checkout" does all the heavy lifting and returns the cart info and also the receipt info. So, one call instead of seven (1 instead of 7).
Benefits:
- Fewer web calls and less data flowing over the wire
- Less code needed to run in the client.
- Better checkout performance times
STATUS DETAILS
New