pixi
Ask AI
What's an 'Ideas Portal'?
DE

pixi 22.01

pixi 22.01 is available from 11 January 2022. It includes several bug fixes, new features, enhancements and optimizations.


The Java logging library Log4j is not used in any pixi product. Therefore, pixi is not affected by the Log4Shell vulnerability.


API

🟩 Bug fix: API call pixiCheckPixiUserLogin returned inactive users as active users. (570242)

🟩 Bug fix: The documentation for API call pixiReportShippedOrders was revised, because the parameters @StartDate and @EndDate had the same description ("Start for shipped out orders"). (580529)

🟪 Enhancement: API call pixiReportShippedOrders was added to the API documentation. Additionally, the call was optimized to reduce loading times in the new Dashboards feature. (549057)

🟪 Enhancement: The documentation for API call pixiGetInvoices was updated and enhanced. (548394)

  • Specify which rows should be returned (pagination) via parameters @StartKey and @RowCount.

  • The parameter @StartKey is not included in the result set. It is used to set the starting row (e.g. @StartKey = 0 returns results from row 1)

  • The parameter @RowCount is used to set how many rows should be returned (e.g. @StartKey = 0, @RowCount = 50 returns rows 1-50)

  • The result TotalRows only returns the number of returned rows. It does not return the total number of all rows in the table.

    • Example with 130 rows:

      • @StartKey = 100,

      • @RowCount = 50

      • "TotalRows" = 30 (rows 101-130)

  • The iteration stops when there are no more rows in the table or the limit that was set with RowCount is reached.

🟦 Optimization: Various procedures were optimized, so that API calls pixiReportGetUnshippableOrders and pixiReportGetShippableOrders return responses faster. During an internal test with huge amounts of data (open orders that were not yet shippable), the API call pixiReportGetUnShippableOrders returned results after 1 instead of 6 minutes.
The API Call pixiReportGetShippableOrders (open, shippable orders) was optimized. As a result, the CPU load reduced and reading request times significantly decreased from minutes to seconds. (549057, 562506)


pixi Messaging

🟩 Bug fix: When the shipping label setting of a shipping vendor was set to "Use External Label" and the ship-out was carried out in pixi Web, the messaging event pixiEXRequestPackageLabel was not called. (580751)


pixi Mobile

Pick to Box & Scan-In

🟩 Bug fix: Due to a false configuration in user permissions, users that did not have administrative rights could only scan certain barcodes. (488258)


Put to Stock & Take from Stock

🟪 Enhancement: The Suggested Bins list retains collapsed or unfolded, depending on what was set during the last session on the device, (467034)


Returns

🟩 Bug fix: When (a) several identical items were returned (b) and they were split between two or more order lines, (c) the desired number of articles could in some cases not be returned at scan in. pixi Mobile now selects the order line with the highest item quantity to clear the return. (498516)


Web Application

Administration

🟪 Enhancement: The delivery note template was updated. (551679)


Controlling (Dashboards)

User Permissions

🟪 Enhancement: In Control Center, administrators can activate widgets for each user individually. (517398)


Logistics

🟩 Bug fix: The widget visibility is retrieved every time the page is refreshed. Before, permissions were cached and only refreshed at night. (551932)

🟪 Enhancement: Three new widgets were implemented in the Logistics Dashboard. (551932)

  • Shipped Orders within 24h

  • Order Lines Scanned-in Today - by Period

  • Shipped Orders Today - by Period


Sales

🟪 Enhancement: A new dashboard was implemented: Sales. (550188)
It features the following widgets:

  • Net Sales Value of Shippable Orders

  • Net Sales Value of Non-shippable Orders

  • Net Sales This Month

  • Net Sales This Month - per Shop

  • Net Sales Last Month


System

🟪 Enhancement: A new dashboard was implemented: System. (562580)
This dashboard features widgets that were previously displayed on the pixi Web landing page.
It features the following widgets:

  • Auto Emails

    • Service Status

    • Drafts

    • Outbox All

    • Outbox Failed

    • Sent Last 3 Days

  • Amazon IDU

    • Error

    • Waiting

    • Processed


Customer Service (Orders)

🟩 Bug fix: There was no scroll bar when there were more items on the list than there could be displayed. (525709)


General

🟩 Bug fix: When a filter was applied, the number of results did not update automatically. Affected features were Orders, Returns, Goods Receipts and Amazon IDU. (563824)

🟪 Enhancement: jQuery UI Libraries (auto complete, dialog, tooltip) were updated to version 1.13. (563437)

🟪 Enhancement: The Auto Emails and Amazon IDU widgets were removed from the pixi Web landing page. They are added to Dashboards > System. (562580)


Items (Item Management)

🟩 Bug fix: When multiple items were selected and all were unselected except one, the application did not display the item details of the row that was active. (523801)


Logistics (Picklists)

🟪 Enhancement: A new parameter named For box range use was added for picklist creation. When selected, all boxes are excluded from the picklist if they are used for unfinished or only partly finished orders at that time. These orders are included in picklists only if either All or Only used boxes is selected as a parameter. To increase usability, the parameter selection was redesigned to a drop-down menu. (515658)


Logistics (Ship-Out)

🟩 Bug fix: When the Weight input was toggled off, pixi returned an error message after the next ship-out. This error was caused because a minus sign (-) was passed in the weight field. Now, pixi passes an empty field when the weight input was disabled. (566501)

🟩 Bug fix: In some cases, two shipping labels were printed: Background: In case a shipping label cannot be generated, the process will restart automatically after 2 seconds, although the initial generation was not processed fast enough. The second label print-out is now delayed by 10 seconds. (574977)


Desktop Applications

Connector

🟩 Bug fix: Logging into the Connector was not possible when the database name was written in lowercase letters and the username was written in upper case letters at sign-in. Irrespective of the input, the database name will be written in uppercase and the username will be written in lowercase letters in the log file. (551977)

🟩 Bug fix: In some cases, the Connector cannot be found. Deleting the browser cache resolved the problem. (564330)


Control Center

User Management (User permissions for pixi Web Dashboards)

🟪 Enhancement: In Role Settings, Dashboards was added as a new group. Administrators can now define which widgets are visible for each user. By default, all dashboards are hidden for normal users. (517398)


Import & Export

🟩 Bug fix: If a stock export was done for stock in multiple locations, the stock did not get exported for locations that had the setting Use For Stock Export activated. (526179)

🟪 Enhancement: The setting Process Bundle Items As Normal Items does not influence the stock calculation. In addition, for stock export, only items that have Use For Stock Export activated will be exported to the shop. (514048)

🟦 Optimization: Various procedures concerning item import and stock calculation were optimized. Additionally, the item import was split into two steps. Firstly, XML files are parsed and secondly, the data is imported to pixi. (522955)


Customer Service

🟩 Bug fix: Due to a broken procedure, there could be multiple entries of the same customer in a database. This behavior did occur when there was no value passed in a certain field. pixi now sets the value to "N" by default in case there is no value passed to prevent multiple entries for the same customer. (437914)


General

🟦 Optimization: INI files will no longer be stored in the Windows directory (e.g. C:\Windows\...). They are now stored in the user-specific app data path (e.g. C:\Users\<User>\AppData). This optimization was concluded because security settings could in some cases compromise with the use of pixi desktop applications. (518296)


POS

fiskaly

🟩 Bug fix: An issue was resolved that prevented the cash register from closing after updating pixi to 21.11. (551934)

🟩 Bug fix: The POS register could not be closed if the user who created it was different from the user who started the session.
TSS could not be disabled with API V2. (565217)

🟪 Enhancement: Enhanced logging was implemented for the cash register closing. In some cases, the error message was not visible in the log because the request exhausted the character length (4,000 characters) for the log entry. (551934, 565217)


Updates, New Client Versions and Installer

Contact our support team for an update appointment

  • Via email: Click the following link, fill out the email template and send it to servicedesk@descartes.com.

  • Via the portal: Log in to the Portal and open a Ticket.

Updates can either be done from Monday to Friday between 7:00 am and 5:00 pm or overnight. Ask the pixi Support team for an appointment.

Back to top