1 Release Details
Release version: UF 42.0
Latest user rights files updated: UF42.0 can be found here
Date of production synchronization server patch: 16th September 2026 / 18:00 Geneva time
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=12579
2 Supply
2.1 (US-15193; US-15666) Local product master data: invalid status combinations blocked and standardization level enforced
Two related master data problems with local products are fixed in UF42.0. At coordination level, the Product Creator and Standardization Level fields now default to “Local” and “Non-Standard” and cannot be changed — this does not apply at HQ. Trying to save a local product with a UF Status of “Archived” or “Forbidden,” from the product card, now raises a blocking error: “The combination of Product Creator ‘Local’ and selected UF Status are not allowed.”
A data fix cleaned up existing records. Active local products sitting as “Archived” or “Forbidden” are moved to Phase Out, with the usual pipe and stock check: if open pipeline or stock exists, the product is marked as Phase Out; if nothing is found, it deactivates automatically. Where automatic deactivation at coordination level is not possible, a Product Mass Update document named “US-15593 Local_Products UF Status Archived/Forbidden Correction” is created automatically so users can handle the remaining cases without having to search for them.
2.2 (US-15656) “New” button added to Supplier Catalogue menu
A “New” button is now available directly in the Supplier Catalogue menu Partners > Suppliers > Supplier Catalogue, allowing users to create a catalogue without having to go through the partner page first; when using this button, the Partner field is editable so the supplier can be selected manually.
2.3 (US-15112) Procurement Method field behaviour updated on IR and FO
The Procurement Method field on IR and FO documents is now blank and non-editable by default, removing the previously confusing pre-filled value that had no operational meaning before sourcing. Once a line is sourced via the OST, the field updates automatically with the procurement method encoded there, and the value is retained even if the line is subsequently cancelled or cancelled-R. In the Order Follow-up (screen, PDF, and XLS), unsourced lines display “N/A” in the Procurement Method column.
2.4 (US-15771; US-16068; US-16054; US-16044; US-15947; US-15922; US-15911; US-15910; US-15909; US-15901; US-15779; US-15664; US-15663) Merge ITOs and Customs & Transport module updates
UF42.0 introduces the ability to merge multiple Inbound Transport Objects (ITOs) into a single ITO via a new “Merge ITOs” action in the Action menu, following the same model as PO merging. For two or more ITOs to be merged, they must share identical Shipment Type (Inbound), Zone Type (International), Supplier Partner, Shipment Flow, Macroprocess, Custom Regime, and Original Cargo Reference (either identical or all empty — mixing filled and empty references is not allowed). Merging is permitted up to the “At Customs Entry Point” status, and only ITOs in the same status can be merged (Draft+Draft, Planned+Planned, etc.). The merged ITO inherits steps and Custom Regime from the template ITO; Transport and Custom fees are carried over in whatever status they held at the time of merging; OTO references are concatenated with a semicolon separator, and a flag is added to indicate when an ITO has already been merged.
This release also includes a broader set of C&T module improvements. A new “Draft” status is introduced for manually created ITOs and OTOs ahead of “Planned,” and several status and dashboard labels are renamed to better reflect the actual process — most notably “Under Pre-Clearance” becomes “Pre-Arrival” and “At Border Point” becomes “At Customs Entry Point.” Steps are now numbered per macroprocess, Track Changes coverage is extended to steps and fees, and the Custom/Transport Fees tabs gain a Status field. Two new printable PDF info notes for Transport and Customs Fees are available from the Action menu, alongside a “Step date definitions” explanation.
2.5 (US-16004) E-Validation: Synced users no longer receive e-signature email notifications by default
Synced user profiles holding the Sign_document_creator_supply or Sign_document_creator_finance UR were receiving e-signature notification emails from all instances where e-validation was active, resulting in inbox spam for system support profiles. A new “Enable e-mail notification” checkbox is now available on synced user profiles (visible only when electronic signature is enabled for the instance and only on synced user): unchecked by default, it can be ticked per instance when email notifications are needed for testing or support purposes.
2.6 (US-15485) E-Validation: Signee modification rules enforced on locked PO
Previously, it was possible to add or change signees on a locked PO after signatures had already been applied, which could result in signing out of sequence or a PO incorrectly showing as fully signed. As of UF42.0, the rules are enforced: signees can still be changed or backed up while a PO is partially signed, but only in sequence and only for users who have not yet signed; the “Manage users allowed to sign” button becomes unavailable once the PO is fully signed, at which point the only option is to unlock the PO and restart the signature process.
2.7 (US-15525) ECU Location Classification: “External System Managed Stock” attribute
A new “Location Classification” sub-module is added under Supply Configuration > Warehouse Configuration > Regular Warehouse Management, allowing users to flag each ECU with a new “External System Managed Stock” attribute. The attribute is mandatory when editing, restricted to Sup_Supply_Config UR. This improvement is used by and useful also for the SDE/SmartScan application.
2.8 (US-12708) New Reason Types and movement restrictions
This ticket restructures reason type logic across several movement flows to make the recorded reason types (RT) match what is actually happening to the stock.
Moves between regular stock locations (IS/LOG/MED/EPREP/ICU) and Quarantine (Analyze) is bidirectional and limited to RT 7 – Internal Move. From Quarantine or directly from stock, moves to Expired / Damaged / For Scrap are restricted to 12.1- Loss/ Scrap, 12.2 Loss/ Sample, 12.3 Loss/ Expiry, 12.4 Loss/ damage and new RT 12.5 – Loss / Batch; no reverse move is permitted from Exp/Dmg/Scrap back to Quarantine or regular stock.
The only valid onward move from EXP/DMG/SCRAP is to the Destruction location, using the new RT 23 – Destruction; the Destruction location is blocked from selection in incoming shipments.
For claim movements during incoming shipments, RT 7 applies when moving from an MSF or Other Supplier to Quarantine; manually created claims going to Exp/Dmg/Scrap keep RT 12.4 – Loss/Damage.
Movement from and to cross-docking are not impacted by new release.
2.9 (US-14170, US-15700) Retrospective RT correction and Expired/Damaged Report update
A patch script has been applied to retrospectively adjust/correct historical stock movements to be in line with the new reason type logic introduced in US-12708.
The Expired/Damaged Report now includes RT 12.5 – Loss / Batch Recall as a selectable filter, pulling the corresponding movements when selected.
2.10 (US-12639) Search Stock Location in reports – Active vs Inactive Locations
Previously, deactivated stock locations were invisible in the location lookup pop-ups of several warehouse reports, meaning that running a report over a historical period could return different results depending on which locations were active at the time of export.
As of UF42.0, Active and Inactive filters are added to the location selection pop-up in the Expired/Damaged Products, Receptions Report, Deliveries Report, and Export IR Follow-up reports, allowing users to include inactive locations (intermediate stocks, ECUs, ICUs) when needed. Active is the default; Inactive can be enabled alongside it, and the filters work in combination with all existing report filters.
2.11 (US-15693) Select Parcel IDs pop-up redesigned as a vertical scrollable list
The Parcel ID selection pop-up has been reworked from a horizontal box layout to a vertical scrollable list with checkboxes, sorted alphanumerically, making it significantly easier to browse and select Pack IDs.
2.12 (US-15991) “Set to Draft” button removed from cancelled Physical Inventories
A cancelled Physical Inventory can no longer be reactivated via “Set to Draft” — if a new count is needed, it must be initiated through the New button, keeping the cancelled record intact for traceability. This is taken into account for the SDE/SmartScan related flows also.
2.13 (US-15989, US-15882, US-15881) Track Changes extended to Physical Inventory, Pack Types, and PPL
Track Changes is now enabled on Physical Inventory document, Pack Types and Pre-Packing List. Please see tickets for detail on exact fields which are tracked for each.
2.14 (US-15753) Delivery Order and Picking ticket: line state filters and Qty in Stock column
A new line state filter is added to the Delivery Order and Picking ticket, aligning with the existing filter behaviour on other supply documents. Ssers can now filter by unprocessed, all, not available, and cancelled lines. The Delivery Order PDF and XLS exports gain a new “Qty in Stock” column showing the real available quantity at the source location, the “Quantity” column is renamed to “Qty to Pick,” and the Asset column is removed.
2.15 (US-15860, US-15840) PO Auto-VI email notifications clarified
Emails pushed for partial or failed PO Auto-VI updates now include the file name in the subject line, with the Job ID moved to the email body for easier identification. In addition, the PO import job report now provides a clear comment message explaining errors on exception lines caused by an Analytical Distribution financial destination that is not accepted for the product, so users can pinpoint the issue directly.
2.16 (US-15859) UniData product pull: fallback nomenclature for missing root
During UniData product pulls, if the expected root nomenclature ( e.g. MED/LOG – L – LEAF – YYYY) does not exist, the product is now automatically linked to the closest existing sequence of nomenclatures (e.g. LIB – L – LEAF – YYYY nomenclature) instead of failing with a linkage error.
2.17 (US-15983) PPL parcel labels: actual sequence and gap notice
The introduction of US-15016 in UF41.0 allowed for PPL sequence to have gaps. The PPL parcel label report now reflects the actual pack sequence, so labels are generated only for parcels that exist in the packing list. Where the sequence contains gaps, a new notice is displayed on the first label listing the missing pack numbers.
2.18 (US-16036) Auto VI PO import: clearer error details on failed or partial imports
When an Auto VI PO import ends in Exception or Partial Process, the import job report now includes the reason a line was rejected. This gives support teams enough diagnostic detail to identify the cause.
2.19 All Supply tickets integrated in UF42.0
| Key | Summary | Detailed |
| US-15666 | To block the selection of Non-Standard-Local standardization during local code creation. | X |
| US-15593 | Local Products UF Status “Archived” and “Forbidden” | X |
| US-15656 | Supplier catalogue add button “New” | X |
| US-15112 | IR: column procurment method | X |
| US-16068 | C&T: to align color code for canceled ITO/OTO | X |
| US-16054 | ITO/OTO: to add info page in the Action menu | X |
| US-16044 | ITO/OTO: remove the possibility to select in ITO/OTO of Cancelled IN and return SHIP | X |
| US-15947 | C&T: update ITO/OTO filters as per US-15911 | X |
| US-15922 | C&T: number steps within macroprocesses | X |
| US-15911 | C&T: request to change statuses | X |
| US-15910 | C&T: Steps name change | X |
| US-15909 | C&T: main Dashboard name change | X |
| US-15901 | C&T: Custom and Transport fees update | X |
| US-15779 | C&T small feedback list | X |
| US-15771 | C&T Merging ITOs function | X |
| US-15664 | C&T: to update filter show all on Custom/transport fees tab | X |
| US-15663 | C&T: update track changes in ITO/OTO | X |
| US-16004 | E-Validation: Prevent Synch Users Receiving Doc Creator Email Notifications | X |
| US-15485 | E-validation: Locked PO Signee Modification | X |
| US-15525 | ECU: Allow Use Case Classification Attribute to be Assigned to ECU | X |
| US-12708 | New Reason Type for Stock Moves into the Quarantine (Analyze) | X |
| US-15700 | To include new RT 12.5 Loss/Batch recallExpired/ damaged report | X |
| US-14170 | DF of reason type to applied retrospectively linked to New-reason type Destruction | |
| US-12639 | Search Stock Location in reports – Active vs Inactive Locations | X |
| US-15693 | Update the “Select Parcel Ids” Pop-up to display parcels in a vertical scrollable list. | X |
| US-15991 | [SDE] Physical Inventory: redefine “Set to Draft” behavior after cancellation | X |
| US-15989 | SDE: Track Changes on Physical Inventory | X |
| US-15882 | SDE: Add Track Changes to Pack Types | X |
| US-15881 | SDE: Add Track Changes to PPL for returned items | X |
| US-15753 | SDE: Delivery Order Improvements: Delivery Order document Line status filter (asset info removed) | X |
| US-15860 | PO Auto VI: to include filename in the pushed email (partial or failed) | X |
| US-15840 | Auto VI PO import: financial destination error – message not display | X |
| US-15859 | UBUNTU – UniData: Linkage errors First API Pull | |
| US-16110 | Searching for a location with the magnifying glass open the wrong popup | |
| US-16108 | INT generated from IN can’t change destination at line level when RT is Internal Move | |
| US-16107 | (US-15664) to rename Fees in Track changes to Custom Fees | |
| US-16058 | C&T: ITO is not created automaticaly when IN available updated | |
| US-16038 | SDE – Banner design and placement | |
| US-16020 | Error in importing e-pl of shipments in PK_ISB | |
| US-15867 | E-Validation: Increase Size and Format of Signature Boxes Text | |
| US-15757 | E-validation: Physical Inventory – Appearing under Finance Filter | |
| US-15755 | Physical Inventory: Adjustment Type Duplication on Screen | |
| US-15530 | Donation/Loan Reports: 2 digits after the decimal | |
| US-16121 | Daily reminder for e-mail notification exceeds 30 days | |
| US-15983 | PPL parcel labels: actual sequence and gap notice | X |
| US-16036 | Auto VI PO import: clearer error details on failed or partial imports | X |
3 Finance
3.1 (US-15944) WACA VI: A Matching report for the integration of UniField Journal Items in WACA’s HQ system
A new Matching Report API has been introduced to support the integration of UniField Journal Items with WACA’s HQ NetSuite system. The report provides reconciliation-related information, including DB ID, Reconcile Number, Reconcile Date, Unreconcile Number, and Unreconcile Date. The API is designed to return only relevant Journal Items based on reconciliation activity and accounting period criteria, enabling a more accurate synchronization of reconciliation statuses between UniField and NetSuite.
This enhancement strengthens the reliability of the reconciliation process between UniField and NetSuite.
3.2 (US-15985) WACA VI: Balances by Account by Instance by Currency along with Monthly Export
A new API has been introduced for WACA to export Balances by Account, Instance, and Currency for a selected mission and accounting period. The export provides the same balance information previously available through CSV files, including starting, calculated, and closing balances in both booking currency and EUR. This enhancement supports the validation of accounting data before and after Journal Item integration into NetSuite, helping ensure consistency between UniField and the external accounting system.
The solution delivers balance data through a paginated JSON-RPC API and is available only for mission-closed periods, ensuring that exported information reflects finalized accounting data.
3.3 (US-15977) WACA VI API for extraction of Journal Items for Integration in HQ accountancy
A new API has been introduced to support the extraction of Journal Items from UniField for integration with WACA’s HQ accounting system (NetSuite). The API provides accounting data by mission and accounting period through a paginated JSON-RPC service and includes all key information required for financial integration, such as journal details, accounting entries, partner and employee references, currencies, amounts, cost centres, destinations, and funding pools. The solution ensures that only eligible mission-closed periods can be exported, supporting a controlled and reliable integration process between UniField and NetSuite.
In addition, a new Export HQ System (WACA) monitoring screen has been added to allow users to track mission-period exports and manage export snapshots. The first extraction creates a frozen snapshot to guarantee data consistency across Journal Items, balances, and matching reports, while authorized users can refresh the export when required. The API was further enhanced during testing with additional fields such as Journal ID and Employee ID.
3.4 (US-15990) Ubuntu: Vertical Integration file UpfileToD365- iteration 2
The Ubuntu Vertical Integration UpfileToD365 export file has been enhanced with two new computed columns: EUR Amount and KES Amount. These columns automatically calculate amounts based on existing export data, applying the required formulas and rounding values to two decimal places. This improvement helps align the export file with Microsoft Dynamics 365 import requirements and reduces manual calculations during the integration process.
To ensure accounting accuracy, the export logic now automatically balances EUR and KES amounts at sequence level by applying any necessary rounding adjustment to the largest amount within the sequence. Additional adjustment information is also available in the raw data export for improved transparency and troubleshooting.
3.5 (US-15969) OCBHQ Unifield job to export to HQ accountancy is in error after v41 update: dev code fix
Following the UF41.0 update, the OCB HQ job used to export financial data from UniField to the HQ accounting system encountered an error due to a regression introduced by a previous change in the XML-RPC API response. The issue caused the export process to fail with a data type mismatch, preventing the successful transfer of accounting information between UniField and the HQ accounting platform.
A code correction has been implemented in UF42.0 to restore compatibility with the export process. The fix addresses the API call finance.hq.vi_get_ocb_export, ensuring that the expected data structure is correctly returned and processed.
3.6 (US-15961) To prevent OCP VI export on a period until all instances of the mission have “Mission close” state
The OCP Vertical Integration (VI) export process has been enhanced to prevent the generation of incomplete accounting export files. Previously, a coordination could export a period as soon as the coordination instance reached the Mission Closed status, even when some active project instances had not yet completed their period-closing process. This situation could result in accounting entries being synchronized after the export had already been generated, leading to discrepancies between exported data and final accounting balances.
3.7 (US-15950) OCP_MR1_COR – Tax name changed after synch in the tax instance creator, is not changed in the other instances
The tax name management process has been improved to ensure consistent tax naming across synchronized instances. The update prevents incomplete multilingual updates and guarantees that tax name changes are correctly propagated between coordination and project levels. As a result, users will now see the same tax names across all synchronized instances, improving data consistency and reducing maintenance effort.
3.8 (US-15887) AJI : to add track changes
Track changes are now recorded for AD modifications on invoices and AJIs, allowing users to review the history of analytical distribution updates directly through the existing tracking mechanism. The enhancement applies to changes made after the creation of the AJI and is not retroactive to historical data. This provides stronger auditability and helps finance teams identify and review AD modifications when required.
3.9 (US-15873) To add the template of the manual “Journal entry import” into the form
Users can now download the Journal Entry Import template directly from Accounting > Journal Entries > Import Entries. The template includes translated column headers and is readily available within the import form, making it easier to prepare compliant import files and reducing preparation errors. User interface adjustments have also been made to improve the visibility and usability of the import controls.
3.10 (US-15872) Direct invoice – removal of product field from the direct invoices screen
The Product field has been removed from the Direct Invoice form. This change streamlines the user interface, ensures consistency with other finance processes, and reduces the risk of entering information that is not used within the Direct Invoice workflow.
3.11 (US-15637) improvement on the invoice line export file naming
The invoice line export files now include the instance code and export date in the filename. For example, exported files follow a format similar to InstanceCode_Export-Invoice_YYYYMMDD, providing clearer identification, improving file organization, and reducing the risk of confusion when storing or sharing exported invoice data.
3.12 (US-15579) addion of 2 new fields in the Partner’s form: TIN – Tax Identification Number and RCCM – business registration number
To support regulatory and reporting requirements, especially in OHADA countries, two new fields have been added to the Partner form: Tax Identification Number (TIN) and Business Registration Number (RCCM). These optional free-text fields, with a maximum length of 15 characters, allow to store key supplier and customer identification data directly in UniField, improving partner record management and supporting local compliance needs.
3.13 (US-15346) Liquidity journal deletion: change of behaviour of the “delete button”
Journal deletions are now synchronized across all related instances. When an eligible manually created journal is deleted, the deletion is automatically propagated through synchronization, ensuring consistent journal structures throughout the mission hierarchy. To protect accounting integrity, deletion remains blocked when the journal is already used in a Journal Item, liquidity register, or transfer, and users receive an appropriate notification explaining why the deletion cannot be performed.
3.14 (US-15107) Mobile money – A new specific type journal for “Other financial institutions”
Users can now create journals and registers of type Other Financial Institutions, linked to dedicated liquidity accounts and the new OFIN analytic journal. The enhancement, requested by Ubuntu, includes dedicated register screens, statement reconciliation processes, support for liquidity reporting, synchronization behaviour consistent with financial registers, and integration with existing accounting workflows. This improvement provides clearer financial reporting, better segregation of liquidity accounts, and more appropriate management of mobile money and other financial institution transactions across missions.
3.15 (US-12135) removal of duplicate button on “pending cheque register line” in bank register
The Duplicate action has been removed for bank register lines originating from cheque imports. This prevents the creation of duplicate pending cheque entries while preserving the duplication feature for other eligible register lines. The change helps maintain the integrity of cheque processing workflows, reduces reconciliation problems, and encourages the use of standard correction methods for cheque-related transactions.
3.16 (US-11148) OCG: improvement of the performance of the General Ledger and Trial Balance report
The report generation has been optimized through performance enhancements, the introduction of a progress indicator during report creation, and the adoption of the.xlsx format as the default spreadsheet output. The system now also proactively checks report size limits and displays clear error messages when the requested output exceeds supported thresholds, preventing processing failures and improving the user experience. These improvements apply to both the General Ledger and Trial Balance reports, providing faster and more reliable report generation.
3.17 All Finance tickets integrated in UF42.0
| Key | Summary | Detailed |
| US-15994 | WACA VI: A Matching report for the integration of UniField Journal Items in WaCA’s HQ system | X |
| US-15977 | WACA VI: API for extraction of Journal Items for Integration in HQ accountancy | X |
| US-15985 | WACA VI: Balances by Account by Instance by Currency along with Monthly Export | X |
| US-15990 | Ubuntu: Vertical Integration file UpfileToD365- iteration 2 | X |
| US-15969 | OCBHQ Unifield job to export to HQ accountancy is in error after v41 update: dev code fix | X |
| US-15961 | To prevent OCP VI export on a period until all instances of the mission have “Mission close” state | X |
| US-15950 | OCP_MR1_COR – Taxe name changed after synch in the tax instance creator, is not changed in the other instances | X |
| US-15912 | Smaller font for the amount fields on the Cash Inventory form for better visibility | |
| US-15893 | Fix for the update of the functional amount of the JI entries at HQ level (from coordo) | |
| US-15887 | AJI: to add track changes | X |
| US-15873 | To add the template of the manual “Journal entry import” into the form | X |
| US-15872 | Direct invoice – to remove the product field from the direct invoices screen | X |
| US-15728 | When total debit/total credit in booking AND in functional currencies are all zero, we should prevent the posting of the entry | X |
| US-15637 | To improve the invoice line export file naming | X |
| US-15579 | To add 2 new fields in the Partner’s form: TIN – Tax Identification Number and RCCM – business registration number | X |
| US-15346 | Liquidity journal deletion: change of behaviour of the “delete button” | X |
| US-15107 | Mobile money – creation of an specific type journal for “Other financial institutions” | X |
| US-14097 | The deletion of the field “values” in the cash count doesn’t synch to coordo | X |
| US-13487 | OCG_CD1_CHI, KG1_KAZ and KI1_COO: not runs with model sync_trigger_something | |
| US-12135 | To remove the duplicate button on “pending cheque register line” in bank register | X |
| US-11997 | OCG_MG1_IKG: not runs with model financing contract | |
| US-11148 | OCG: improvement of the performance of the General Ledger and Trial Balance report | X |
4 Non- functional
4.1 (US-16109) Upgrade of PostgreSQL to 14.24
PSQ has been upgraded to version 14.24. All instances already on v.14 will be automatically upgraded. Those on previous versions (v.9 etc) will not be automatically upgraded as manual intervention is needed.
4.2 (US-15880, US-15972, ) SDE/Single Data Entry / SmartScan APIs additions for Packing List, Pack Types and Physical Inventory
APIs have been developed in UniField to allow data flows for Packing Lists and Physical Inventories. The APIs were developed to use JSON RPC. This completes all UniField objects which were due to have APIs developed for SDE/SmartScan.
4.3 (US-15953) RAM reduction when Mission Stock Report is run
OCG flagged this issue of a notable increase in RAM at certain times. This was due to previous updates to the Mission Stock Report. The format of the report has now been changed to reduce memory usage.
4.4 (US-15973 Conversion of previous APIs for WaCA to JSON format)
APIs which had previously been developed for WaCA have been converted from XML-RPC to JSON format. This was completed for APIs for Partners, National Staff and Journals.
4.5 (US-16133, US-16131, ) WaCA APIs for Currencies, Rates, Expats, HQ Entries
New APIs have been developed for Currencies, Rates, Expats, HQ Entries for WaCA, specifically to allow data flows with the WaCA HQ accounting system Netsuite. APIs were developed in JSON format.
4.6 (US-15335) Eye icon added to password fields to allow password characters to be temporarily displayed
An “eye” icon has been added in the system for fields where password values can be entered. By default the password remains non-visible, but the user can click the icon to see the password they are typing / have typed. This does not allow other users to see stored passwords in the system.
4.7 (US-16035) Automated export/import additional option to configure export to/import from SharePoint/OneDrive
As requested for Ubuntu, a new protocol option can be selected for automated exports and imports. As well as the options “FTP” and “SFTP” is it now also possible to select “OneDrive” as the protocol in the Tools>Tools>Automated imports / Automated Exports configuration page to allow direct exports to/imports from OneDrive.
4.8 All Non-functional tickets integrated in UF42.0
| Key | Summary | Detailed |
| US-15880 | SDE: Packing / PPL + Pack Types – basic APIs | X |
| US-16109 | PostgreSQL 14.24 | X |
| US-15986 | To update Pull API WaCA+Ubuntu with new OC’s Id | |
| US-15954 | OCG: Instance creation: Wrong Purchase Default Currency and Field Orders Default Currency | |
| US-15953 | Increased peaks in RAM utilisation (Mission Stock Report change) | X |
| US-15879 | SDE: UF unable to identify Project IN if final Synch is missing | |
| US-15973 | VI: WaCA: Adapt and convert into JSON three APIs for VI UniField > NetSuite | X |
| US-15972 | SDE: Physical Inventory APIs | X |
| US-16118 | Issue with Reconfigure: Allocation stock configuration step – Remove checks | |
| US-15941 | E-validation: List of Signatures Report not Generating | |
| US-16015 | Password reset consistencies | |
| US-16131 | WaCA_ VI: currencies, rates and expats | X |
| US-16133 | WaCA: VI HQ Entries | X |
| US-16035 | Ubuntu: Can UF export to SharePoint directly? | X |
| US-15335 | UF password field – Create “Password Eye Icon” | X |
| US-15831 | In the “Search: proprietary instances”: to create a new filter: Draft | |
