Release Notes Wisefish 24.1.20240719.49809

An enhancement has been made to “Sales Agreement Line” and “Purchase Agreement Line”, and respective subpages. The fields “Agreed Minimum Quantity” and “Agreed Maximum Quantity” have been added. This change allows users to define minimum and maximum quantity of each line. It has also been ensured that the “Minimum Quantity” and “Maximum Quantity” fields of the Production Agreement Line are filled out from the Delivery Agreement when it is being copied over.

When a user was operating within a tenant where WiseFish is not installed the user was not able to open an Item Card. That has been changed so that a user does not need the WiseFish extension to open an item card.

An enhancement has been done to Wisefish BOM functionality such that the Wisefish BOM can be posted manually and automatically through Trade Item Output Journal. All the inventory and non Inventory BOM are automatically posted when the Posting method selected in Wiefish Setup is automatic. For Manual user has to manually post the BOM components.

There are three fields in General section of Delivery Agreements under the subsection “Warehouse Task List”. A decision has been made to hide these fields by default because there are so few customers using this. For the users that use these fields, they can personalize the page and add them back in.

We have implemented this enhancement to give the users the possibility of writing longer descriptions in Raw Material State where it is needed. The length of the “Description” field has been increased to 80. Additionally we have added a new field that is hidden by default called “Description 2”, users can add this field if the first description field is still to short.

An enhancement has been made for Blanket Sales Agreements and Blanket Purchase Agreements. Now the user is able to send the Agreement reports via email. This functionality already existed for Receipt and Delivery Agreements, now these Agreements contain this functionality as well. Images display where this functionality has been added.

When posting with API, the dates were updated to the working date. We have made a change to that so the user is able to manually input the date and it does not automatically change to the working date. This enhancement gives the user the ability to manually chose a date for any field that should contain a date without the date becoming the working date.

This is the same fix as the prior issue describes but made for Sales Agreements.

There was an issue that caused certifications to be missing whenever the user had the language set to Icelandic. This issue has been fixed so that users can have the system set to Icelandic and certification shows up on reports where and when they should.

There are two different errors that contain the same error description. This has been fixed by improving the error messages to better describe what is going wrong in the system.

When a report is created where the Certification is on the Stock Center and “Display in Invoice” is selected, the Purchase Invoice Report does not show the certification. This is also the case with Purchase Reports. This error has been fixed so that the certification is showed just like it should when this is the case.

It is not possible to credit purchase invoice/receipt if TI posted out of inventory with TI Credit Inbound Journal. Because it is not possible to reverse credit inbound with TI Credit Outbound Journal.

We have implemented a fix that will prevent this issue from happening in the first place by making sure that the user is not be able to credit purchase or fishing trip Trade Items in “TI Credit Inbound Journal”.

The way we prevent this is by changing the filtering of available OTI’s to only show “Production” and “Repacking” Trade Items available for Crediting. (So Transfer, Purchase, Fishing Trip and Sales OTIs are no longer available to be credited here.)

This means that purchases cannot be screwed up by crediting OTIs in a journal, and they need to be credited with a Credit Purchase Document.

When Fishing Gear is changed in the header of a Fishing Trip the Fishing Gear in the lines is not updated.
This has been fixed so when the user changes the Fishing Gear in the header it is updated in the lines as well.

These pages can be opened from different places and the filter is differently set depending on where you open the page from. This has been fixed so that the filter is the same no matter where you open the page from.

When a user creates a Production Agreement copied from a Delivery Agreement the field “Trade Items (base)” gets the incorrect value. This error was caused because of an incorrect values were used for the calculation, this has now been fixed so that theses values are correct after copying a DA to a PA.