1       Release Details

Release version: UF 32.1

Date of production synchronization server patch: 10th April 2024 / 18:00 Geneva time

Latest user rights files updated: UF32.0 can be found here

Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.

JIRA filter for all integrated tickets: https://jira.unifield.org/issues/?filter=12504

2       Supply

2.1         (US-12853) E-Packing List file import on IN blocked

An issue was spotted by OCB that meant it was not possible to import a VI file (E-Packing list) on INs by using the manual “Process IN and Pick and Pack” option for INs which were linked to a synched flow/FO. This is linked to Python 3 migration and is now corrected.

2.2         (US-12802) IN PDF cannot be generated for certain flows

This issue spotted by several OCs meant that in the case of certain flows – e.g. when some lines were Cancelled & Resourced by Supplier instance, at requesting instance level, the PDF could not be generated on closed IN. This is linked to Python 3 migration and is now corrected.

2.3         (US-12787) French version of some PDF reports, thousand separator compressed

Issue spotted by OCP, when User Interface is viewed in French, some PDFs generated (e.g. PO Allocation Report, Cash Reconciliation) do not show amounts in thousands clearly as the 1,000 separators has been compressed. This is linked to Python 3 migration and is now corrected.

2.4         (US-12786) PDF dates appearing in English when UI in French

Issue spotted by OCG, When User Interface is being viewed in French, for some PDFs (PO, IR) the dates are appearing in English. This is linked to Python 3 migration and is now corrected.

2.5         (US-12871) Prevention of Validation of Picking when already converted to OUT

This improvement is to avoid blocking issue faced by OCB that a Shipment was blocked from being validated due to Pick having been converted to OUT and then (Pick) being validated. This is possibly linked to Python 3 migration and action causing issue should no longer be possible.

2.6          (US-12823) Non-Stockable product in own Pack in PPL causing negative quantities in stock

This issue, present already in previous releases and spotted by OCA and OCB led to negative stock quantities in certain stock locations (Distribution) which needed Data fixes to correct. The issue was due to incorrect Source and Destination locations being assigned by system on SHIP PPL lines for the case of Non-stockable products which were in their own Pack. This has now been corrected.  

2.7         All Supply tickets integrated in UF32.1

KeySummaryDetailed
US-12871Prevent Validation of Picking when already converted to Out (via multiple tabs)X
US-12853E-PPL import file blocked on IN when option import with Pick & pack used.X
US-12823Non-Stockable product in own Pack Stock move to have correct source & destination locationsX
US-12802OCBBD101: PDF generation error IN5229X
US-12787French version of some PDFs – thousand separator compressed: Allocations Report, Finance cash reconcilliation etc large amounts unreadable.X
US-12786Dates printed in French on pdf English versionX

3       Finance

3.1         (US-12848) OCP HQ: Impossible to import HQ entries file at HQ

Following migration to Python 3, we had to do a fix on formatting and uf8 encoding to enable to import the HQ entries csv file format.

3.2         (US-12833) E-Validation: PO PDF Backup Signature Text Unexpected Behavior

Following the release of the ticket US-12173, when the “back up” tick box was selected for the e-signature on the PO the following behavior was expected: “In the PDF, when back up is ticked, write “as back up of” the role it is backed up.”

During testing of the feature, it was discovered that this text was not consistently displayed on the PDF in alignment with what is selected in UF.

It seems that when the Technical Responsible user is ticked as backup, the “as back up of” text appears in all signature fields to the right even if those role/function are not ticked as back up, or even if the role/function is not active on the PO.  This happens AFTER the tech responsible signs.  Before the signature, the text does not appear on the PDF.

When only the Finance Responsible role/function is ticked as backup, the text does not appear on the PDF at all.

We corrected the behavior of the “as back up of” text on the PDF.  Only display at header level of the Roles/Functions column if ticked as backup.

3.3         (US-12773) UF32: Change in the csv exports format

Following migration to Python 3, csv export format under windows got impacted and were fixed. Usual exports coming from the selector are now fixed.

3.4         (US-12753) UF32 release: code fix in the “Field balance specifications report”

Following migration to Python 3, we applied a code fix to fix the field balance specifications report. The link to this report is this: Accounting/Reporting/Accounting reports/Field Balance specification report.

3.5         All Finance tickets integrated in UF32.1

KeySummaryDetailed
US-12848OCP HQ: Impossible to import HQ entries file at HQX
US-12833E-Validation: PO PDF Backup Signature Text Unexpected Behavior

X
US-12773UF32: Change in the csv exports formatX
US-12753UF32 release: code fix in the “Field balance specifications report”X

4       Non- functional

4.1         (US-12758) – OCBHQ vertical integration XMLRPC webservice issues for Vertical Integration

Python 3 releases disrupted OCB webservices linked to UniField HQ Vertical Integration. A code fix has enabled to reestablish the webservices. Few changes on OCB Middleware were also needed to fix HQ entries webservices.

4.2         All Non-functional tickets integrated in UF32.1

KeySummaryDetailed
US-12855OCBHQ vertical integration XMLRPC webservice issues for HQ EntriesX
US-12810Hardware Id cannot be saved in Windows Registry 
UniField v32.0 Release Notes
UniField v33.0 Release Notes