MT1 Release 21. April 2023
  • 21 Apr 2023
  • 2 Minutes to read
  • Dark
    Light
  • PDF

MT1 Release 21. April 2023

  • Dark
    Light
  • PDF

Article summary

Here is a list of changes and fixes that will be included in Maintenance release update 20.12.2 of MainManager FM on 21.st of april 2023. 

Please contact your project manager at MainManager for further details. 

Small changes and improvements

Be able to invoice lease contract from MainManager to Unit4 ERP (Agresso) (US3070)

As part of that integration the customer wanted 2 changes to the lease contract payment handling. One was to always work with monthly unit prices and secondly to get the billing lines more detailed, showing the quantity and the unitprice price projected to the actual price period (previously invoicing for lease has been with Quantity=1 and Unitprice= Price

For that two system settings have been added 

When <Lease contract unitprice period> is set to Month then one new locked field appears in the data model for Lease contract payment, the field Annual unitprice which is the unitprice multiplied by twelve. Also the Unitprice column gets the [per month] marking making it obvious to the user that he is working with monthly unit prices even though Payment interval can be 12 (annual), 3 (quarterly) etc.

The same Annual unitprice field appears for Lease contract payment item. Additionally a new field <Price period> is introduced. That is reflecting the service period for the payment in months. When payment plan is calculated this field is part of the calculations and for start and end contract payment period this value can differ from the actual payment interval defined in the contract payment.

The formula for the price is then Price = Quantity * Monthly unitprice * Price period

When invoicing is done and the system setting <Lease contract billing details> is set to <Detailed with price period included in unitprice> then when Invoices are created the Invoice lines for the lease contract have: 

  • Quantity= Payment item quantity 
  • Unitprice = Payment item unitprice * Payment item price period

That information is then sent to Unit4 

Small changes to integration between Visma and MM (i44849)

New boolean field added to Unit price type so it is possible to mark that it should be joint (many sites using the same)

Selection type shown for object (i44783)

If a selection type is registered on active lease contract and this object is selected in form, then the selection type is shown below the drop down field. 

Option to make building space name be highlighted in 2D instead of room number (i44861)

Following system setting <Highlight building space name instead of identification> has been added

When that setting is used then rooms are shown as following in 2D




Multiple selection of objects and connecting to Work orders and Tasks(i44100)

New action was added for connecting objects/locations/checkpoint to work orders and tasks.

 

Bug fixes

 

ProcessModuleIncident IDDescription
Building ArchiveGIS map44836Fix an error in GIS maps causing building polygons not to be shown 
Building Archive2D - polygons44787Fixed issue with selected items from drawing transferring over to multiselect actions in list. Also fixed issue with empty selection showing in Change Cleaning Info action when selecting from drawing.
Building Archive2D drawings / floors44793New global action to define how to order building floors in floor selector on drawings and other places in system
Building ArchiveHousing44794Fixed incorrect filtering on housing records in housing list view.
Document managementDocuments44525/44754Problems when adding multiple documents in drop zone, they were not getting a document type. MainRecord was alive between calls to Create Document function. Created a new Document instance for each file to save.
Operation and MaintenanceContracts44746Fix error in filtering on price index
Operation and MaintenanceWork orders44399Add column to show Closing note in list
Operation and MaintenanceStandard tasks44832Add check in action that creates tasks from standard task so that date from can not be later than date to. 






Was this article helpful?