New Features in G5, version 22.7
Here's a summary of the major new features in version 22.7 of Monitor G5, broken down by our teams that specialize in developing each area of the system. We hope you'll find this useful. For more information on all new development and changes in this version, read the Changelog at monitorerp.com/changelogs. There you also can watch a video rundown of the major new features in this version.
During this sprint we’ve started several new projects, so a lot of the functionality delivered will be extended in future versions.
We now have support in Synchronize with BOM and routing to update the existing manufacturing order with new weight data.
There is two new system settings whereby time used either above or below a set percentage of an operation, will activate to mandatory set a cause code when the operation is set to finished.
You set up a list of cause codes for the user to select from in the Cause codes procedure. It is also possible to set comments to be mandatory for a cause code.
You find this function in the Report operation and Report manufacturing order procedures. Support for this feature will also be implemented in the Recording terminal in the next release.
In Subcontract documents/Shipped the manufacturing order, the purchase order will now be replanned to the date you enter manually as finish date when reporting shipping of the goods to the supplier. You can manually deactivate this functionality on any order row. Previously, the entered date was only used for the order document that was sent to the supplier.
In a part configurator where variables are used, the list of variables is now sorted so that rows used in the current formula are now presented at the top of the list. This makes it easier to edit simulated values and test the formula.
In Manufacturing order info and Planning window in Part register, there is now a new toolbar function to create Monitoring tasks. Previously, you had to manually set the name for the task and select who to send a notification to – this is now pre-set and the receiver of the notification is set to your user when this new method is used. For operations, you can now more easily create a task if you want to be informed when the operation has a certain status. And for parts, you can also a create tasks which monitor a certain level of balance, or get a notification when a purchase order row is delivered.
The team has solved 38 issues, of which 18 were reported by customers.
During the next sprint, we'll be working more on memory in the Product configurator and mandatory cause codes. We'll also start working on a set of updates regarding Pre- and Post-calculation improvements.
Team Sales-EDI have been focusing on delivery planning, and the ability to include both shortage and ready-for-delivery rows on a pick list. We've also been working on a new grid layout in Register customer agreement – tab Agreement basis. During this sprint we resolved 55 issues.
Our team in Gävle (Team Purchase) have mainly been working with the Return order process, to enable the possibility to return a purchase order to your supplier.
Changes in price each and discount on options in the remote configurator will be saved in the Sales company, and loaded if the configuration is reopened.
It is now possible to transfer the order row's quantity in the remote configurator. It is also possible to edit the order row's quantity in the remote configuration window. Quantity on order row is therefore locked for remotely configured parts.
The quantity is used in the calculation of staggered prices for the main part and for options, as well as in the calculation that is made when the configuration is confirmed.
In Delivery planning, list type Picking plan – Per customer, it is now possible to include both rows with a status of Shortage and Ready for delivery.
By doing so, the row with a shortage will be included on the pick list. This can be useful if the part is currently in production, and will be ready for delivery later. The Qty to deliver can later be cleared in the Pack for delivery procedure.
We've introduced a new grid layout in the Agreement basis tab in the Register customer agreement procedure. It is now possible to view invoices and credits that are linked to an agreement basis.
We have also added new functionality to the credit invoice button. It is now possible to select what you want to happen after you have credited an invoice linked to a agreement basis.
If you want to invoice your customer again – after the crediting the first invoice – select Re-invoice after credit. This will revert the status on the agreement basis after creating the credit, and the agreement basis will be possible to release again.
If you don’t want to invoice your customer again, select Invoicing complete after credit. This will retain the status (invoiced) of the agreement basis.
We have also added two new buttons to the toolbar: Suspend and Resume.
By using Suspend, it is possible to suspend an agreement basis from release. This is useful if for some reason, you don’t want to create an invoice basis. If you have set Release basis automatically to active, a suspended agreement basis will not be released.
The Resume button will change the status from Suspended to Registered and it will be possible to release the agreement basis again.
It is now possible to report delivery of customer orders via EDI import. In brief, this function corresponds to what you do in the client when using the Report delivery procedure and the Free selection list type, which means the delivery can be reported for customer orders where a pick list is not used. Along with the EDI import itself, this now also means that:
When importing a purchase order confirmation, there is now a checkbox you can use to include/exclude all text rows.
The External delivery note number field is now available as a presentation field, from the backstage procedure.
Information from the package structure (if you have used a pick list with a package structure in the Pack for delivery procedure) is available in the data sets for the following document types:
Team Sales/EDI has resolved 55 issues, of which 43 were reported by customers.
Team Purchase has resolved 16 issues, of which 14 were reported by customers.
We still have some work to do to make it possible to include shortage rows on a normal pick list – mainly formatting the shortage rows differently on the pick list document to make it easier to see which rows on the pick list are shortage rows.
We'll be making some adjustments to the credit invoice dialog in Register customer agreement. This will make it possible to select what to credit at row-level. Previously, it was only possible to credit the full invoice. We will also make some adjustments to the dialog, in order to add support for crediting comprehensive invoices.
Development of Return order is progressing well, and we plan to release Register return order in 22.8. We are currently working on adding different document types that can be useful when shipping the return to the supplier. The plan is to continue the work with return order after the release, adding functionality continuously.
We've managed to close 41 issues in total. We've started our journey to take 100% responsibility for our automated robot testing for the Stock area (this was previously handled by another department).
Some highly requested functionality is to be able to change traceability type on an existing traceable part. In this sprint, we've added the ability to switch from batch to serial number (the main prerequisite is that the balance on the batch cannot be greater than 1).
Other highly requested functionality is the possibility to split batch. By using the new icon beside the batch type field, it is possible to split the batch into smaller ones, as long as there is no cleared material on the batch.
New columns have been developed for the Import parts procedure, such as multiple units, comments, name translations and administrator.
In Part register, we have now introduced a simplified way to move stock balance. In the stock tab, the balance can be moved from one location to the next. In this release, the balance will be moved directly if the locations don’t have any “special settings”. We'll be having this functionality tested out, and see if Monitor users like the new take.
A new field for description has now been added to the procedure. This was done to make it easier to set a manual “label” to the case.
This version contains a first release of the Payment plans function, which is major development since it affect many procedures. Payment plans are used for purchase orders, and are the equivalent of invoicing plans for customer orders. You can use payment plans for the purchase orders which are to be invoiced and paid either fully or partially in advance or in arrears. The function is activated via the system setting Handle payment plans on purchase orders.
Examples of procedures/functions affected by the development:
Please note that the following functions within payment plans are not included in 22.7, but scheduled for release around the end of 2022.
It is now possible to get a more in-depth follow-up in the accounting. This can be done via automatic posting against dimensions linked to the following registers:
From previously, we also have Project as register as well. The purpose is to perform analyses, follow-up and measure profitability on a deeper level, based on postings for the registers above. In order to be able to use a register above as a posting dimension, you have to register it as a separate posting dimension in the Dimensions procedure. You can then activate which accounts that should be posted against that dimension in the Chart of accounts procedure. It is also possible to register budgets on these dimensions in the accounting.
Improvements have been made when you search for e-invoice recipients to connect via Crediflow in Customer register. The VAT number from the Customer register will be copied automatically, and Country code has been added in the search. The Country code will be loaded from the mailing address, unless you have entered a separate invoice address, in which case the country code from the address will be used.
"Our supplier number" from the Customer register is now included in the e-invoice. This information is exported as AdditionalDocumentReference in the Peppol file.
It is now possible to attach linked files even when you send e-invoices. In order to be able to attach linked files, the setting "Enclose embedded PDF in XML" must have the alternative "Linked files" selected in the Settings for export/import procedure, for Export type E-invoice. The setting "Linked files" has to be checked on the Selection tab in the Print invoice procedure during printout, in order to export the attached files. Please note that only a file of the type PDF, with a maximum size of 4 MB, can be included.
During this sprint we've resolved 55 issues, whereby 16 have been patched and 32 are linked to support cases.
During the next sprint, we'll be focusing on the following development:
We've now closed around 30 development items during this sprint. Some visible and user-oriented development is listed below. As always, however, we have made a lot of internal and general improvements, along with providing frameworks and support for other teams.
We've started development towards the support for cloud-based file management systems – starting with SharePoint.
It is now possible to set up a server printer, using the Microsoft Print to PDF – printer to select a folder to which all files will be saved when using that printer. This makes it easier to save files without being prompted with a printing dialog for each individual file each time.
We've added a link in the web client login which grants the user access to view which third-party licenses are being used.
The web client has a new look to it when you log in. It now features a more similar design to the desktop client, with a new expandable list that enables a multi-level view of companies.
When the settings menu is folded out, you can now find the User setting with the rest of the settings.
A lot of MQL fixes have been made to solve database related issues.
General improvements have been made.
To resolve issues revolving scheduled jobs.
31 issues were closed during this sprint, 17 of which were patched and 18 issues had committed support cases.
Some fixes to highlight are: