New Features in G5, version 22.3
Here's a summary of the major new features in MONITOR G5 for version 22.3, broken down by our teams that specialize in developing each area of the system. We hope you'll find this useful and interesting. For more information on all new development and changes in this version, read the Changelog at monitorerp.com/changelogs. There you also can see a video about the major new features in this version.
During this sprint we’ve been able to deliver some small but useful functionality. The larger projects are still in production, and will hopefully be delivered in the next version.
The result of the measuring item – OK or Not OK – is now saved to the database as a complement to the numerical value. This result can be seen in Measuring data log.
We've looked through all the lists in the Manufacturing and Time recording modules, and found and fixed eight procedures in which the settings tab wasn’t completely correct on the printout of the list.
We've been focusing on the recording terminal in the Mobile client, updating it to provide the same functionality as the desktop client. We are still not finished, but the following has been fixed in this version:
To support the development of the TimeCard by the Adaptation department, we have created two APIs.
The team has resolved 55 issues, of which 43 were reported by customers.
During the next sprint, we'll keep working with support for recording Location in the recording terminal. In BOM and routing, we're developing support for a density register and are also continuing to work with improvements to the Mobile Recording terminal.
During this sprint we’ve been focusing mainly on Customer order transfer (COT) with configuration, and adding some improvements to Register customer agreement.
We've added a Document structure tab in Register customer agreement. This tab can be recognized from Register quote, and works in a similar way.
We've added support for row type 2 in Register customer agreement.
We've added a new document entitled Modified customer agreement which will show any changes made to a customer agreement. This is similar to Modified order confirmation in Register customer order.
The new value on the customer agreement is shown in red text, and the previous value is visible below the current value.
We've added a new function called Planned invoice date. This setting will determine how the Planned invoice date on the agreement basis generated from the agreement will be set.
This is useful if you want to invoice your customer X days before the invoicing period. By leaving this setting as 0 days, the Planned invoice date will be the first day of the invoicing period (when using invoicing method = In advance)
A new toolbar button has been added for the package rows. This button is used to calculate volume and loading meters for a package row.
In the Packages grid we have also added a toolbar button which makes it possible to copy/split a package row.
The fields Package type and Goods type are now possible to edit.
The "Create shipment" button has been added, and can be used to create a shipment based on the pick list in the Register shipment procedure. A new field, "Shipment", has been added which shows the shipment number and the status of the shipment created from the list in the procedure.
We now transfer more fields on the order rows.
And in the header, we transfer Our reference.
It is now possible to run a Check delivery time (CDT) on customer order rows from the sales company, containing parts with configuration in the production company.
Changes that are made on a customer order in a sales company can now update the quantity and finish date of manufacturing orders in the production company. A new transfer setting is used to allow this.
The status of the customer order in a production company is now synced to the corresponding purchase order in the sales company. The status is then used on the linked customer order to inform the user whether or not changes are allowed.
The team has resolved 60 issues, of which 37 were reported by customers.
We will continue to focus on COT with configuration.
Beside this, we will focus on:
We've managed to resolve 39 issues (of which 31 were linked to support cases) in this sprint. Our developers have been working very hard, and we've managed to close a lot of development items. Our users will be able to enjoy many new, useful features in version 22.3.
In the manufacturing reporting procedures it is now possible to access the serial number linking dialog. This was previously only visible when saving, but if some serial number links need to be edited, they are now accessible for further changes. See the screenshot below:
A lot of users have sent us requests to be able to delete parts, even if the part has been used and has dependencies in transactions. The closest thing we can provide – which has now been developed – is the option to deactivate the part. This will set a status on the part, and block it, so it won’t be visible in the “search lookup” and won't included in any calculations.
We've also developed a new list type in Part List that can be used to list and view the deactivated parts – and also reactivate them if needed.
Move stock balance now has a completely new look, which we hope will take the procedure to a whole new level and allow the user to work more efficiently than before. The procedure now supports multi-selection of balances and easier search/selection, and there is a new scanning mode for users that have a handheld scanner linked to their computer.
In total we've completed 36 development items during the sprint, which are a combination of country-specific development as well as standard functionality and UI/UX improvements. Below is a summary of some of the development carried out in this version.
It is now possible to use invoicing plans on quotes. Invoicing plans can be used when an order should be partly or fully invoiced in advance or arrears. Invoicing plans can be set in the Header tab, which opens the Invoicing plan tab, just as in the Register customer order procedure. You can also see information about the invoicing plan on the quote document.
It is now possible to automatically report VAT to the Skatteetaten (Tax Agency) via Altinn, for Norwegian companies. The XML file for the reporting will be automatically created when the VAT report is printed and approved. You can upload these files manually, or allow the system to upload them automatically.
VAT can now be posted automatically when you post amounts relating to purchases and sales subject to VAT. For example, this could be receipts and invoices which have already been paid, and do not have to be registered as invoices in the accounts payable.
Support has been enabled for GoBD export. GoBD is a German standard for the export of accounting data that is used for tax audits. The feature exports a number of CSV files containing certain basic data such as parts, customers, suppliers, VAT codes, etc.
A new system setting, "Use VAT amount from imported invoice", has been added in the Purchase tab. In this setting you can select if VAT from the invoice will be used, or not, during import of a supplier invoice. The VAT code registered on the supplier will be used if you select No.
A new list type, Balance per supplier, has been added. This report displays the accounts payable balance per supplier in a layout similar to general ledger reports. For every supplier, the period's opening balance, transactions (invoices and payments) and closing balance are displayed. A corresponding list for customers was added to the system in version 22.2.
We've made some user interface improvements in, for example, the Settings for export/import, Register invoice directly and Register supplier invoice procedures.
During this sprint we've resolved 72 issues, of which 40 were linked to support cases.
During the next sprint we'll be focusing on the following development:
In this sprint, we've continued to work on adding support for Microsoft SQL Server as well as improving printing performance and better handling of hidden paths in the Paths procedure.
The new printing dialog has found its way into a variety of Register procedures, and the list will keep on growing as this development continues into future sprints.
In addition, a lot of smaller fixes and back end development have taken place, which means a lot of good things have been improved in the background that may not catch the eye of the user, but are important nonetheless.
In the next sprint, we'll be focusing a lot on resolving issues, continue working on MSSQL, and add support for the new printing dialog for the Pack for delivery procedure.
A major development focus in the next sprint will be reducing the size of the database by adding support for storing all printouts in a location other than the database, as it is today.