20.19 General additions

General additions 20.19

Be able to work with snapshots in an approved manner (EMM-2409)

There have been done some changes and additions to snapshots and logic surrounding them.

This is how the registration window is displayed for administrators.

Now it is possible to add access to user roles directly from the registration window instead of through sub data.  Min and max value has been added for reports and my page portals.  If this is set the report is only sent out if the calculated value is within the selected range.  The same applies to the My page portals they are only displayed if the value is within the selected range.

A new field “Publish“ has been added that marks the snapshot available for other databases.  It is only possible to mark a snapshot available if the “Exclude location” is set to true.

This is how the window is displayed for non administrators.  Some fields are hidden for regular users.

Now it is possible to register report frequency subscribers directly from the registration window instead of through sub data.  Possibility to add user roles as subscribers has been added and will the report be sent to all users within the selected user roles.

This is how the report frequency window is displayed for non administrators.  They can only select from the employee list to add subscribers.

A new icon has been added to the snapshot menu which opens up the property window for that particular snapshot.  Non administrators can only do this for their own snapshots.

A menu has been added to the my page where a user can select the order of items and turn them on and off.  This setup is saved on a user level.

A new automatic action has been added to the Report generator module that fetches published snapshots from the service database.  It will import all snapshots marked as published in the service database.

Be able to select if template should overwrite existing values (EMM-2425)

A new possibility has been added to template function so that you can select “Exclude location“.  If this option is selected the location (Site,Object) will not change when the template is selected.  Also when a template is now selected only fields that are within the saved template are emptied or changed within that registration window.

Be able to show main log history in improved manner to make it more readable and support better GDPR (EMM-2447)

This story is split into three different parts:

1. Turn on new history logging for all modules that support it

2. Improve the interface showing the history log

3. Convert old history log records into new

Before a text was created for the history logging when new record was created or a record was changed. That caused few problems, including:

• The created text was dependent of the active language of the user creating/modifying the record

• Name of captions/concepts change over time so it might be very difficult to understand what was happening for old history records

• Not suitable for GDPR (for example if names/emails/other personal info was being saved)

New history logging differs from the old one that it will store FieldName-Value pair when records are added or FieldName-OldValue-NewValue trio when records are changed. All modernized data modules will now have the new history logging turned on. That means that from the next release, most history log records will be stored by the new method.

There has also been work on the user interface displaying the history log. All changes are now grouped into days. Within each day additions/changes are shown grouped on the user responsible for the addition/change:

The left most column shows the caption of the field getting a new value (when record is created) or being modified (when record is changed). The caption will follow the active language of the user and will follow the data-model for the respective module.

Some modules will also save history logs on parent records if some changes are made on them, for example if a “Annual task budget”-record is changed then a history log record will be saved on the task that owns the record. Those changes will be shown like this on the parent record:

The user can then click “View changes” to see what was changed on the sub-record:

In connection to this work has been done to convert old history log records to new. New action was created (intended for EG admins to run) that converts old history log records for all modernized modules:

However, since some of our customers have tens, if not hundreds of millions of history records, this action can take quite a lot of time to run. The action should therefore only be run in cooperation with the MainManager’s development team.

MainManager FM WCAG compliant (EMM-2401)

An ongoing task for our development team is to test and evaluate the MainManager system according to WCAG standards and making it compliant with at least A and AA demands.

One of the things that has been fixed now is that the loading spinner for the whole system has been changed to a WCAG compliant spinner.  It has also been synchronized through out the system so the same spinner is displayed in different parts of the system.

Old spinner in content load

New spinner in content load

Old spinner in lists

New spinner in lists

Old spinner in property windows

New spinner in property windows

Be able to add text when editing images (EMM-2345)

We have added a new option to input text on images

1. New “Text“ button. When the user clicks the button a new text box is added to the image.

2. New “Pencil“ button. When the user clicks the button we go back to drawing mode.

3. The text box that is added when user clicks on “Text“ button.

Additions and changes to categories in extra fields (EMM-2653)

Following changes has been done to the extra fields concept

The categorization has been changed for Extra field category so that we have now 3 different sets of Extra fields categories (each with 5 items)

• Tag specific

• Scope specific

• Global

The tag specific which is the original set has been changed in following manner

For all tag categories except incidents categories the category set is the same for the same object. For instance Task planning and Task management has mutual sets

Mutual sets (Tag specific)

Task: Task planning, Task management, Standard task

CranePart: All levels of Craneparts

LeaseContract: All levels of lease contracts

LeaseContractPayment: Lease contract payment, Lease contract payment item, all levels

Component: All levels of building components, Product data and Product data components

Department: All sub levels of company

Scope specific means sets that are mutual for same scope of data

Scope Project: Electronic invoices, Electronic invoice breakdown, Work orders, Time and material registration, Projects, Recurring incidents, Tasks, Standard tasks, Task years, Incidents, Project years

Scope Object: Sites, Buildings, Building floors, Building spaces, Building stairwells, Capacity objects, Crane and crane parts, Housings, Open areas, Open area parts, Roads, Feeder pillars, Light poles, Tanks, Artifacts, Equipment, Sensors, Vehicles, Phones, Project folders, Product data, Product data components, all levels of building components, Transmission lines, Transmission line towers

Scope Lease contract scope: Lease contracts, Lease applications, Lease contract payments, Lease contract payment items

Scope Unitprice: Service contract items, products (articles)

Scope Organisation: Person, Employees, Companies and all sublevels of companies

Scope Document: Documents, Pictures, Drawings

Scope information: Object information, Object color, Object information, Technical information, Service partners

Bug fixes