Fusion 2.2

Build Date: 2010-12-31

New Features

  • Up until now, if someone on another computer made a change somewhere, and you were looking at a list window on your computer with the same information, the new information would automatically be refreshed within a couple of seconds. The mechanism for doing this was not very smart and caused a lot of unneeded network traffic because in almost every case, no one on another computer was in need of the refresh (ie. the specific window probably wasn't even open). This process has now been changed so that most of the time, only the computer that made the change will get the refresh messages. We have tried to choose situations where it would be worth the network traffic to still send refresh messages to all clients. If you notice a situation where a list window is not updating when you would expect it to, let us know so we can consider making a change.
  • A lot of very fundamental changes have been made to allow Fusion Server to run more efficiently. These changes include the above changes in client messaging, the new truck syncing system described below, the ability for Fusion Client to recognize when data hasn't actually changed so that it doesn't send information to the server unless it really needs to (like when clicking Save on a window after not making any changes), Fusion Client doing more of the work, and other changes that have reduced that amount of write related activity on the server. The net affect of this is that the server should not experience the hangs and slowdowns that some customers have experienced under higher loads. One welcome side affect is that the server can take at least a little more advantage of multiple cores. The downside to such fundamental changes is the possibility of introducing bugs in code that has worked well for a long time. While we have tested these changes extensively, we ask you to contact us if you notice anything we missed.
  • Added a Refresh button to the Daily Feed Detail which refreshes the information on the page. This is easier than changing the date back and forth to force it to refresh.
  • The process for syncing information between trucks and the server has been changed significantly. These changes and the reason for them is explained in greater detail in the document titled "Fusion Syncing Transition Guide". Please read this document and explain the changes to those feeding or confusion will reign.
  • During syncing, the initial connection code is more robust than it used to be so you shouldn't see that "Can't make initial connection..." error very often unless the network really is down. Also, if you do get the error, there is some extra information explaining the specific nature of the error.
  • Added "NRC Mature Weight" to the Lot Center advanced print list of available fields.
  • When age verifying without using Symmetry, if an invalid tag number was sent to the CCIA the whole age verifying queue was stopped because of the error CCIA sent back. We know look for this particular error and count the animal as not age verified and just continue with the queue without any messages.
  • It is now possible to export and import report definitions from the Detail Print area of the Lot Center window.
  • It is now possible to export and import report definitions from the Inventory Summary window.
  • You can now inline the Chuteside Batch list with the Lot Protocol list as the parent report for advanced printing.

Bug Fixes

  • When adding new death causes, the master data cache would not update so you couldn't use the new death cause in an out cohort. This is fixed.
  • When printing feed sheets, if you chose the "Print For Remainder of Day" option, the printed Target As Fed column was incorrect (it was often zero). This is fixed. Also, this report now handles pens that haven't been assigned a ration yet better.
  • An inventory offset of type Adjustment with a negative value would calculate as a positive value. This is fixed.
  • When doing a Risk Analysis Export, the projected weight usually comes from the Target Weight field for the lot. If this field is left blank, the projected weight is supposed to then come from the Mature Weight field, but this was not happening. This is now fixed.
  • In the Inventory Summary window for commodities, drugs, or inputs, the beginning and/or ending balance could be incorrect if there was no specific inventory information for the item within the date range. This is fixed.
  • Sometimes inventory items did not recalculate as soon as they should have or would recalculate out of order. This is fixed.
  • If you have an input that has an equivalency different that 1, and if that input is not associated with a commodity, Fusion forgot to take the equivalency into account when calculating inventory information as shown in the Daily Input Inventory window and the Inventory Summary window. This did not affect billing, just the inventory display in these two windows. This is now fixed. If you had any of these items and you want Fusion to recalculate the values for these inputs, please use the Inventory Queue window.

On This Page