Skip to content

Weighbridge

Weighbridge 3.3.4 [12-Jul-2021]

  • [Enhancement] Software update notification - the system will now show you a notification after login if you had a system upgrade.

Weighbridge 3.3.3 [10-Feb-021]

  • [Enhancement] Use ticket column definition to validate if product is mandatory.

Weighbridge 3.3.2 [05-Dec-2020]

  • Maintenance release.

Weighbridge 3.3.1 [30-Nov-2020]

  • Maintenance release.

Weighbridge 3.3.0 [16-Nov-2020]

  • [Enhancement] Auto Lockout - Optional settings have been added to automatically lock the system after a set timeout and/or after a ticket has been created.

    1. Automatic lockout period in seconds. The user may specify anything from 0 seconds (disabled) to 999 seconds (approximately 16 minutes). The default is 0 seconds (disabled)

    2. Perform automatic lockout after ticket creation – yes/no. The default is 'no'.

    The options in the settings window may only be updated by users with 'Weighbridge Admin' access rights as assigned in the Users administration window in Plantation Manager. These settings are local to each weighbridge, multiple weighbridges require individual setup.

    The following application logic applies:

    • The weighbridge operator launches the WB application and logs in as usual. The lockout countdown timer is started (if enabled in settings).

    • Any button press, dropdown selection or keystroke in the WB application will reset the automatic lockout timer. Inactivity will cause the automatic lockout timer to count towards the specified lockout value.

    • If the lockout period is reached, the system will, without warning, 'lock' the system and open the normal Login window.

    • The Login window will be populated with the user's username and the keyboard focus will be set to the empty password text box.

    • During this lockout state, normal background processing related to lookup cache refresh, ticket upload (if any) and linked weighbridge tickets refresh (if any) will continue as normal.

    • To unlock the system, the user must type in his/her password and press <Enter> or click OK. If the password validates successfully, the system will continue in the state it was before the lockout.

    • If a different user wishes to login, the new user's username and password may be specified. In this case, the previous user will be logged out and the new user logged in. The state prior to the lockout will be lost, i.e. open windows will be closed, etc.

    • If the 'perform automatic lockout after ticket creation' option is active, the system will be automatically locked after a ticket has been created.

Weighbridge 3.2.1 [23-Jan-2020]

  • Maintenance release.

Weighbridge 3.2.0 [29-Apr-2019]

  • [Enhancement] Weighbridge User Access Rights

    Note

    The new user access rights functionality described below is disabled by default, please contact Microforest support to enable it. But please make sure that the necessary weighbridge application rights, and Log Supplier, Customer and Supplier data access rights are properly configured beforehand.

    • Weighbridge Operator – This new application user access right allows administrators to assign weighbridge operator rights to applicable users. Only users with weighbridge operator, admin and/or override rights will have access to the weighbridge application.
    • The Log Suppliers, Customers and Suppliers data access rights are now also active on the weighbridge. Operators will not be able to select items for which they do not have access rights. However, if an existing ticket already contain any of these restricted items, it will still be available (on the specific ticket only).

Weighbridge 3.1.0 [11-Sep-2018]

  • [Bugfix] Barcode labels – Fix issue that under certain circumstances assigned default suppliers incorrectly on Weighbridge ticket when barcode label scanned.

Weighbridge 3.1.0 [11-Sep-2018]

  • [Enhancement] Weighbridge Customer Invoice

    Customer Invoice generation on ticket final leg completion may be activated on request. When activated, the weighbridge ticket information is used to generate and print a Customer Invoice. This can only happen while the weighbridge is online and has an internet connection to the Microforest server.

    Successful completion of this process involves the automatic creation of a normal Business Suite ticket, processing of the ticket to create a process batch with financial transactions (visible in File – Processing/ERP Integration – Process Manager), and invoice generation and printout on the weighbridge.

    Supply packages, account numbers, rates, prices, addresses and other relevant configurations in the Business Suite are critical for the success of this process. If any of the required information is missing, or there is no connection to the Microforest server, an invoice cannot be generated.

    • New fields have been added to the business Suite application that are required for invoice printing. Refer to the Business Suite 5.5.4 notes in the Business Suite section of this document.
    • The following Customer Invoice modes are available:
      1. Off.
      2. On, but optional – On the final leg an invoice will be printed and if successful, the normal weighbridge ticket will be printed. If invoice generation fails, the user may choose to skip it on the 'Pending Tickets' window and print the normal ticket so that the truck may leave.
      3. On and mandatory – Same as above, but invoice generation cannot be skipped. Invoice printing should be successful before a normal ticket may be printed and the truck allowed to leave.
    • A new status has been added to indicate that the ticket has a pending invoice: Completed - Pending Invoicing.

Weighbridge 3.0.1 [03-Jun-2016]

  • [Enhancement] Weighbridge Id Validation

    Ticket sources are registered on the Business Suite database and can be viewed in the Weighbridge Administration window (Logistics – Device Data Management - Weighbridge). Ticket source id 0 (Default) is reserved for tickets entered manually in the Ticket Capture window. All other devices must use a ticket source id > 0. A weighbridge's id is setup in the File – Settings menu.

    A weighbridge's id is setup locally in the File – Settings menu. A weighbridge Id = 0 may exist because of the following:

    • Not properly configured during initial weighbridge program setup/re-installation.
    • Users performing a Cleanup in the Application Launcher. All customized settings (except the waybill number) are lost in this case (including communication settings). Local ticket and lookup caches are not influenced by this.

    Normally if the weighbridge id is reset to 0, the other settings will also be reset to their default values, so this must also be checked.

    This enhancement checks the weighbridge id during login and if incorrect, forces the user to fix it before the application can be used for anything else except to update the settings. If the user that logs in is a weighbridge administrator, the Settings window is automatically opened, else the user is prompted to seek assistance from an administrator and is logged out.

Weighbridge 3.0.0 [30-May-2016]

  • [Enhancement] Handle Local Cache Corruption.

    Prior to this enhancement the only way in which local cache corruption (lookups and ticket data) could be resolved was to manually delete the cache files on the local file system.

    This enhancement enables the system to automatically delete corrupted cache files and restore the data from the server when online (also see next enhancement for ticket cache restore).

  • [Enhancement] Weighbridge PC/Server Ticket Transaction Synchronisation.

    Previously weighbridge tickets pending upload from the weighbridge(s) to the Microforest server were transmitted to the server and could be viewed in the Weighbridge Administration window (Logistics – Device Data Management – Weighbridge menu).

    This functionality has been enhanced to allow a weighbridge to synchronise its locally cached tickets with those on the server, e.g. when it's local ticket cache was corrupted, or the PC was reinstalled/replaced. It allows abandoned tickets to be deleted on the server, which will also remove it from the weighbridge's cache (currently only by Syndicate support on request).

    This functionality also enables the linked weighbridges enhancement below.

  • [Enhancement] Linked Weighbridges.

    Two weighbridges can be linked on request. Once two weighbridges are linked, leg 1 of a transaction can be started on either weighbridge and leg 2 of the transaction can be completed on the same or the other linked weighbridge. Both weighbridges list each other's tickets. Once a ticket is completed, it will disappear from both weighbridges.

    If a weighbridge has a linked weighbridge, the linked weighbridge's name is displayed and tickets from the linked weighbridge are displayed with a [Weighbridge Name] prefix.

  • [Enhancement] Additional Attributes and Overrides

    The following attributes have been added. They are protected by the 'Weighbridge Override' user access right and if used, will appear on the printed weighbridge ticket and should also be added to the weighbridge ticket definition in the Business Suite.

    • Long Haul Amount: Only applicable and available if a long hauler is specified. The operator may specify an agreed upon override amount that the long hauler will be paid. If specified, this amount will be used as the full long haul transport cost (not rate), otherwise the normal transport rates will be used.

    • Short Haul Amount: Same as above, but for short haul.

    • Weight Reduction Penalty: A penalty percentage between 0 and 30 may be specified. It reduces the net weight which influences all values calculated from weight, e.g. purchase price, sales price, all COS values (if not overridden)

    • Purchase Price Penalty: The operator may specify a penalty amount to be subtracted from the full purchase price amount. If taking into consideration that a Purchase Price Rate Override (R/ton) may also be specified in the Business Suite ticket window (not available on the weighbridge), purchase price calculation is as follows:

      • Net Weight (ton) = Weight - Weight Reduction Penalty
      • Purchase Price Rate (R/ton) = Standard Rate, or Purchase Price Rate Override.
      • Purchase Price (R) = Net Weight * Purchase Price Rate - Purchase Price Penalty

Weighbridge 2.3.5 [22-Sep-2015]

  • [Enhancement] New 'Order Number' field. This field is optional and may be ignored. If used, please contact Syndicate to add it to the weighbridge ticket type definition.
  • [Enhancement] Automatically select suppliers when barcode scanned and suppliers were specified on works orders. Refer to Business Suite 5.4.9.
  • [Change] Transporter renamed to Long Hauler
  • [Enhancement] Previously long hauler was mandatory, now either long hauler or short hauler must be selected. If long hauler is not selected, the vehicle registration number(s) will be associated with the short hauler. It may be necessary to add short hauler registration number fields to the weighbridge ticket type (otherwise registration numbers may not be displayed on the weighbridge ticket); please contact Syndicate if required.

Weighbridge 2.3.4 [07-Sep-2015]

  • [Enhancement] Add extractor supplier.

Weighbridge 2.3.3 [11-Jun-2015]

  • Maintenance release.

Weighbridge 2.3.2 [29-May-2015]

  • [Enhancement] Ticket Printout – Added Driver, Weighbridge Clerk and Security signatures to public tickets also.

  • [Enhancement] Public Tickets – Manually Specify 1st Leg Weight

    Public tickets does not support the 1st Leg/2nd Leg (in/out) measurement concept. Provision has been made to manually specify a first leg weight on any public ticket if required. If specified, 1st Leg, 2nd Leg and Net weight is included on the public ticket printout.

Weighbridge 2.3.1 [30-Apr-2015]

  • [Enhancement] Ticket Printout – Added Driver, Weighbridge Clerk and Security signatures.

Weighbridge 2.3.0 [30-Jan-2015]

  • [Enhancement] New 'Product' ticket attribute.

    This attribute is currently only available for use with the 'Barcode Label Scan' enhancement described below. It is automatically populated when a barcode is scanned and the input control is always disabled, i.e. cannot be edited by the operator.

  • [Enhancement] Barcode Label Scan

    The Barcode Label Generation enhancement mentioned in the Business Suite 5.4.0 notes above enables this functionality on the Weighbridge application. As mentioned, barcode label generation and printing can be disabled or enabled; in fact there are three modes:

    • Mode 1 - Disabled: No barcode label generation is possible in the Business Suite and barcode scanning in the Weighbridge application is disabled; only manual tickets can be created.
    • Mode 2 - Enabled, manual tickets allowed: Barcode label generation and barcode scanning are both enabled, and manual weighbridge tickets can still be created.
    • Mode 3 - Enabled, manual tickets not allowed: As above, but no manual tickets allowed, tickets can only be generated by scanning a barcoded label.

    A new label 'Barcode label scan mode' on the Settings window indicates the current mode.

    The same barcode must be used for both legs of the transaction.

    The scanned barcode is used as the delivery note number.

    As soon as labels are generated in Business Suite and the Weighbridge program's caches are updated (automatically or manually) those labels will be available for scanning on the weighbridge.

    Once a label was used to create a ticket, it can only be used to complete the ticket (2nd leg). It cannot be used to create additional new tickets.

    The new 'Scan Barcode' button is only enabled if barcodes labels are enabled (modes 2 and 3).

    • Pressing this button opens the 'Scan Barcode' window.
    • Once open, the system waits for a barcode to be scanned. If an incorrect label is inadvertently scanned, the scan may be repeated; it will automatically replace the previous scan.
    • If there is a problem with the scanner, the operator may input the barcode manually after ticking the 'Manual Input' check box.
    • The operator must press OK after a successful barcode scan or manual input.
    • If the barcode is registered in the system and it is not already used, or it corresponds to an open ticket (2nd leg pending) a new ticket is created or the open ticket is selected for completion.
    • All ticket attributes are automatically populated using the barcode information and their input controls disabled, except for the following which the operator has to provide:
      • Vehicle Registration Number
      • Harvesting Team – only if more than one for the works order harvesting supplier.
      • Transporter
      • If applicable, the following optional attributes: Short Hauler, Loader, Off Loader
    • Once the above attributes are supplied, the operator may continue to weigh the load as always and create (1st leg) or complete (2nd leg) the ticket.

    If a ticket was created via a scan, the word '(barcode)' is shown next to the delivery note number/barcode. These tickets cannot be completed without scanning the same barcode for the 2nd leg (if the mode is switched to Mode 0, they are once again handled as normal manual tickets).

  • [Enhancement] Handle missing lookups of existing tickets.

    Previously when the lookups of an existing ticket (e.g. 2nd leg pending) were no longer available, the ticket detail would no longer be visible on the main window because its values are no longer available in the combo box lookups. This can be caused by:

    • Manual changes by Business Suite administrators, e.g. remove supply from supply package, or
    • Lookups updated after year-end and all tickets (with old lookups) were not uploaded to the Microforest server prior to year-end.

    The operator is now warned of the missing lookup values and the temporary values text edits are set to the string representation of the original value, but in <> brackets to highlight the problem. The operator must, as soon as valid lookup values are available, select it from the combo box and update the ticket.

    If the selected ticket is a scanned barcode generated ticket, the applicable combo box control(s) are enabled to allow the user to correct the problem. The 'Update Ticket' button may be used to save changes, or the 'Clear All' to cancel. The ticket may also be updated when the final leg is scanned, or afterwards by opening the ticket from the 'Tickets' window.

Weighbridge 2.2.0 [05-Sep-2014]

  • [Enhancement] Login
    • Previously user was always logged in using cached user data, irrespective of online status. This presented a problem if user's password changed or user added since last cache refresh.
    • Changed to login online if internet connection available, i.e. using newest user info.
  • [Enhancement] Tickets Window - New Delete button to delete old pending tickets.
    • Only users with weighbridge admin rights.
    • Only In/Out tickets, not Public tickets
    • Only if
      1. Leg 2 pending for longer than 7 days (test ticket, abandoned, etc)
      2. Both legs are completed, but it has temporary free text values pending proper lookup selection and it is older than 3 months (never fixed, will also not be?)
  • [Enhancement] Online Check and Cache Update Frequency.
    • Shortened online check period to every 15s (was every 30s), first lookup cache refresh after 15s (was 30s) and then every 3 minutes (was 6 minutes)
  • [Enhancement] Weighbridge Log – Changed log mechanism to create a new log file every month (time stamped). Previously the log file just increased in size, slowing down log file viewing and updating.
  • [Enhancement] Product Grade – New field to be populated by Weighbridge operators if defined as part of Weighbridge Ticket field definition. Also added to Weighbridge Data Administration window.
  • [Enhancement] Combobox/Dropdown Selection Improvement – See notes for PM 5.2.3
  • [Bug Fix] Access Denied error on Cache Read
    • This error occurred when a normal windows user runs the Weighbridge application after a windows administrator has run the Weighbridge application.

Weighbridge 2.1.0 [29-Oct-2012]

  • [Enhancement] Application Launcher Offline Start Option. If used with Application Launcher 3.0.0 or higher, allows startup while internet is not available.

Weighbridge 2.0.0 [01-Mar-2011]

  • [Enhancement] Make provision for weighbridge moisture deduction, cubed tons functionality and columnar timber/pole quantity.
  • [Bug Fix] Sort properly in Customer & Commodity combo boxes.

Weighbridge 1.11.0 [20-Jan-2011]

  • [Enhancement] New setting to allow skipping first leg transaction ticket printout.
  • [Enhancement] Weighbridge Settings - upload to server for informational purposes.
  • [Enhancement] Pending transactions – upload to server for informational purposes.
  • [Enhancement] New Weighbridge management window on Business Suite – view weighbridge settings, pending transactions, and completed transactions with errors preventing ticket creation.
  • [Bug Fix] Window controls do not resize if window resized, thus also do not allow window resize or maximize.
  • [Bug Fix] - Did not properly remove completed ticket from open list if vehicle registration upper/lower case mismatch.

Weighbridge 1.10.0 [13-Jan-2011]

  • [Enhancement] Enforce the same number of weight measurements during leg one and two, except when manual weight measurement is done.

Weighbridge 1.9.0 [03-May-2010]

  • [New] Capability to use predefined vehicle empty weight

Weighbridge 1.8.1 [09-Mar-2010]

  • [Enhancement] Allow deletion of the transaction cache, only in the unlikely event of a corrupted transaction cache due to file system problems.
  • [Enhancement] Write additional ticket information to local weighbridge log file.