=====Version 19.4.=====

[[http://www.produmex.name/PmxVersions.php|Produmex Download page]] \\ [[http://builds.produmex.name/ProdumexScan/19.4/|Download version 19.4.]]

<WRAP round info>
**Tested SAP B1 versions**
  * SAP B1 9.3 PL10 (MSSQL 2017, HANA 122.22)

//Note: Older and newer SAP B1 versions will usually also work, but have not been specifically tested in this version.//
</WRAP>

<WRAP center round todo 100%>Before the upgrade, make sure that you check the [[implementation:scan:releasenotes|release notes]] of the intermediate versions between the current version and the version you want to upgrade to.</WRAP>

<WRAP center round important 100%>If you use UDF values in document lines and/or heads that are copied by Produmex Scan, make sure that you **manually activate the Copy UDF Values to Target Document setting** on the Produmex Scan General tab of the Produmex Scan Settings screen.</WRAP> 

===New Functions===

1. **Copy UDF Values to Target Document** setting 
    * The //Copy UDF Values to Target Document// setting has been added to the Produmex Scan General tab of the Produmex Scan Settings screen as a workaround for an SAP Business One bug (for more information on the bug click [[https://launchpad.support.sap.com/#/notes/1382856 |here]]).
    * If the setting is enabled, the UDF values of the base document are copied to the target document when the target document is being created. The data copy is applied on a head and line level as well.
    * The setting applies to the following cases:
         * Purchase Order > Goods Receipt PO
         * A/P Reserve Invoice > Goods Receipt PO
         * Sales Order > Delivery
         * A/R Reserve Invoice > Delivery
         * Pick List > Delivery
         * Inventory Transfer Request > Inventory Transfer
         * Sales Order > Inventory Transfer
         * Delivery > Sales Return
         * A/R Invoice > A/R Credit Memo
    * <wrap em>Exception</wrap>: \\ If a UDF is filled in on the base document and it is also configured as a custom field on the Produmex Scan client, **user queries must be created** to have the default value of the UDF copied from the base document to the target document.
    * <wrap em>Important</wrap>: \\ By default, the setting is disabled because it causes a loss in performance. If you use UDF values on a head and/or line level and they are copied while using Produmex Scan, make sure that you **enable the setting to avoid potential data loss**.
    * Documentation: [[implementation:scan:settings#produmex_scan_general_tab|Produmex Scan General settings]]

2. **Connection timeout for Client application** 
    * The //Timeout (sec)// setting has been added to the Advanced tab of the Client Configuration Parameters as an initial timeout setting for the Client application.
    * The Client application requests its configuration (including the Kill Time value) from the application server and for this first-time communication the Client application uses the Timeout setting.
      * If the application server does not respond within the time limit defined by the Timeout setting, the Client application aborts the connection. 
      * If this first communication is successful, that is, the application server responds to the Client application within the time limit, the Kill Time setting is applied to define the timeout for future communication among the Client application, the application server and the database.
    * The default value of the setting is 15 seconds. If your application or database server is slow, it is recommended to change the value to a higher number.
    * Documentation: [[implementation:scan:client_configuration&#advanced_tab| Configure Produmex Scan / Advanced tab]]

3. **Italian version**\\
  * Initial support for the Italian localization has been added to Produmex Scan.

===Produmex Scan for Android===

1. **Customization**\\
    * **Customization Assist Mode** \\ The setting can be enabled on the Advanced tab and the general [[implementation:scan:customizationtechnology|customization guidelines]] applies to it. Exception: using external form and data positioning (see below).
    * **On External Form**\\ If you select Yes in the On External Form column of the Customization Fields screen, the Extra button is displayed on the given screen and if you click the button, it opens the external screen with the fields and buttons positioned to the external screen. 
    * **Data positioning** \\ In addition to the //x, w// and //lines// values, the possible values for data positioning include //row// and //fullrow//.
      * //Row//: The row where the field is positioned to. If a field is customized, but no row value is defined, the field is automatically displayed as the last field on the screen. Empty rows are not displayed on the screen. 
      * //Fullrow//: Its value is 1 (fullrow:1). By default, if no //x// or //w// value is defined, the given field is displayed in its full width. If you define the //x// or //w// value for a field and no other field should be positioned next to it, the //fullrow// value can be used.
      * The vertical position (y), the screen height (h) and the font size (f) are not applicable.
      * If a field has buttons, there is no need to customize the buttons with the field. Once a field is customized, its button(s) are automatically positioned accordingly. 
    * Documentation: [[implementation:scan:install_guide:scan_android_apk#customization|Customizing Produmex Scan for Android]]

2. **Additional advanced settings**\\
    * **Smaller controls**: If the setting is enabled, the size of controls is reduced and the Data Repeater list has more space on the screen.
    * **Connection Timeout (sec)**: An initial timeout setting for the Client application with a default value of 15 seconds. 
       * First the Client application requests its configuration (including the Kill Time value - 30 seconds by default) from the application server and it uses the Connection Timeout setting. If the application server does not respond within the time limit defined by the Connection Timeout setting, the Client application aborts the connection.
       * If this first communication is successful, that is, the application server responds to the Client application within the time limit, a **total timeout value** is applied to define the timeout for future communication among the Client application, the application server and the database. The total timeout value is defined by the sum of the (Initial) Connection Timeout and the Kill Time with a default value of 45 seconds (15 sec + 30 sec). 
       * If your application or database server is slow, it is recommended to change the value of the (Initial) Connection Timeout to a higher number.
    * Documentation: [[internal:scan:install_guide:scan_android_apk#installation_and_initial_setup|Produmex Scan for Android: Initial Setup]]

3. **Logs**\\
    * The Logs tab has been added and it is divided into two parts:
       * On the top of the screen the system displays general errors, for example unsuccessful login. When you log out in the main menu, this log is sent to the Service Broker and cleared.
       * On the second part of the screen unexpected events and their causes are displayed and with the Send logs button the logs are sent to the Produmex Service Broker, which saves them among its own log files. These files can be sent to the Produmex Support Team. 
       *A Clear logs button has been added to the screen to clear logs on both parts of the screen.
    * Documentation: [[internal:scan:install_guide:scan_android_apk#logs|Produmex Scan for Android: Logs]]

===Documentation Maintenance===

  * [[implementation:scan:installguide|Produmex Scan Fresh Installation]] - screenshots and documentation structure updated
  * [[implementation:scan:install_guide:scan_android_apk#scanning_barcodes_with_camera|Produmex Scan for Android]] - scanning barcodes with camera


===Bugfixes===
^Ticket^Description^
|98811|Batch assignment disappears when you bind the inventory counting|
|91521|Customization validation of Quantity field does not work when pressing Enter|
|92266|Scan Quantity screens - Quantity text field validation error|
|93564|Quick Counting - DataRepeater size is wrong in the Quick Inventory Counting Quantities screen with customization|
|93889|Picking - Not enough serial quantity for item|
|94113|Stock Transfer Request - Insufficient quantity|
|94773|Stock Counting - Data Repeater customization fails|
|95850|Barcode - Allow GS-128 barcodes on document filter screens|
|96196|Sales Order - Wrong quantity displayed in case of delivery draft documents|
|98984|Delivery - On posting document number is shown from delivery instead of draft table|
|99315|Barcode - Allow scanning of items with the same barcode on document filter screens|
|99774|Customization - Tab is not working for customization fields on Transfer Stocks Quantities Serial screen|
|101050|Inventory counting - Serial number quantity mismatch on posting|
|101624|Picking - UDF value for lines is not moved to the delivery document [[http://builds.produmex.name/ProdumexScan/19.4/19.4.00003/|19.4.00003]]|
|102709|Sales order - Shipping Address components are empty on the delivery after posting|
|103530|Customization - Events are not receiving the field values on the external form|
|104819|Goods receipt - Issue with the New button after entering the last serial number|
|107298|Scanning - Application crash after using scan with camera [[http://builds.produmex.name/ProdumexScan/19.4/19.4.00003/|19.4.00003]]|