MT2 Release 20.10 21. October 2022

Here is a list of changes and fixes that will be included in Maintenance release update 20.10.2 of MainManager FM on 21st of october 2022. 

Please contact your project manager at MainManager for further details. 

Changes on access administration to multi select actions (US3114)

Users might experience after this release update that actions used for multiple lines in the list will pop up as buttons above list instead of within the action menu. Now it will be possible to configure button access to max three multi select actions within each module beside from the common actions (like export list, copy, paste etc). 

Actions above the list that are configured with button access

 

Improvements on action to create tasks from standard tasks (US3200) 

Now possible to define Action group and Action group priority on recurring tasks and standard tasks (has to be added to data model). Action groups are used lets say that you have 2 tasks on the same object belonging to the same activity group, but one task Monthly fire inspection with a monthly fire inspection checklist with priority 2 and another task Year fire inspection with a more detailed yearly fire inspection checklist with priority 4. Then the system cancels the monthly task instances when the yearly inspection occurs (with a defined days tolerance registered on the action group) (V20.10)

A new no select action has also been added <Cancel lower priority action group task instances>. It cancels all existing not started task instances that this apply to.

All task instances that have been cancelled in this way get the <Action group cancelling> set to true (column not part of default data model). The remarks are filled out with explanation

When the action <Cancel task instances> is run then the user is demanded to enter Remarks that is then registered on the cancelled task instances

The work order can now be open from the task instance window

Changes to time registration rules (i44071) 

Now it is possible to define time registration rules and assign to user roles. That fields become available by adding it to the standard data model for user roles through the Edit mode

The time registration rule is given an describing name. It is possible to set different restrictions in the rule

<Cannot register hours in advance> means that the user is not allowed to register for instance hours for later dates than today

<Lock hours approved by employee> is not standard solution but for customer having a special employee approval of own hours this disallows that such time registrations can be modified

<Cannot register hours on finished work orders> means that user is not allowed to register hours on work orders with status Finished

<Cannot register hours on closed work orders> means that user is not allowed to register hours on work orders with status Finished and booked

For cases where user should not be allowed to register hours for instance far back in time following can be set regarding allowed time frame for time registrations

By marking <Last day in next last month active> this is activated. 

If <Work days> is marked that means that the system calculates bases on the number in the <Last day in running month> the number of work days into the running month (also taking into calculations public holidays) the employee is allowed to register hours for the last period. If it is not marked than if for instance 20 is entered in <Last day in running month> then the last date that the user is allowed to register hours prior to previous month is 20th if the running month unless it lands on a weekend, than it is prolonged to next monday (that is either 21st or 22nd)

It is also possible to define how far back in the last month the user is allowed to register hours through the field <First day in previous month>. Best to explain this be example

If the customer for instance has invoicing period from 20th in the last month to 19th in the running month then the rule would be

<First day in previous month> 20 and <last day in running month> 19. That means that the user can until the 19 of the running month enter time registrations from 20th in the next last month. However after the 19th the time limits shifts to 20th of the last month 

Changes to Register hours <RegisterHoursJP> (i43984)

Now possible to register hours for many employees at once (when a group is for example working on the same task). Layout of action has also been changed and when Option <Single employee> is selected then Description suggestion field has been added showing the ID and name of work order as well as last time registration description that the employee had registered on this same work order. For multiple employee scenario the Description suggestion shows only ID and name of work orders. In that scenario he the <Employee hours registered for date> is not shown.

The Weather field is now required and does not default from last registration 

Now it is possible to register hours around midnight, for example from 22:00 to 04:00 for nightshifts to register their hours. The hours are put on the date according to the Date field 

Copy and Cut has been disabled in time registration as it does hard to validate maximum numbers of daily hours per employee etc. when using such a robust action

Condition assessment made a part of Maintenance management process (US3202)

Condition assessment step has been added to Maintenance management process for system where Operation and Maintenance are separated into 2 processes.

Detach standard task from product data and unlink document from location (i43313)

Now it is possible to detach standard tasks from product data without deleting the standard task. The <Unlink> column becomes available if user has delete rights to product standard task. This column is by default Visible  (V20.10)

It is also possible to detach documents from the referenced location without deleting the document. The <Unlink> column becomes available if user has delete rights to document. This column is by default Visible. 

Two new system settings for handling of accounts (i43877)

<Account on internal tasks> can be used for system where tasks and work orders are differentiated into Internal and External tasks. If that scenario is on then as standard account tree and account key is not visible in Standard tasks, Tasks and Work orders. If this is turned on then they appear and same demand is made to account handling on internal and external tasks

Not calculate account on tasks created from standard tasks. As standard when task is created from standard task the action tries to find out what account should be put on the created task, based on accounts connected to sites, account type on standard task etc. If this is turned on it does not do put an account on the created task unless there is a direct reference to an account on the standard task or if the project that the task is created on has an defined account, then that is put in the task. A change has been done to the creation of standard tasks that if the task is internal and the <Account on internal tasks> is not turned on then no account is put on the task

Region column in location related data lists (i44086)

A Region column has been added as possible column to all location related data lists for instance Tasks, work orders, incidents, buildings/floors/spaces, building parts etc. 

This column will only be available for configuration if in System settings the Region settings are set to <Region> or <Region group and region>

Site address columns added in the work order module (i43880)

Now the site city, zip code and street address can be added to the work order data model:

These columns can be filtered on and grouped. When added to the data model the address will appear by default in the location section in the work order form (locked). It can be removed in the form settings.