Change Log

QBIS is constantly getting better. We listen to the wishes of our customers and our dedicated team ensures that QBIS evolve with the ambition to be the best system for you.

Here we list all the updates we make in QBIS.

March update 1 – 2021

During February, the QBIS Team has been working hard to deliver a lot of asked for features and improvements to the QBIS suit of producs that you as a customer are using every day. The highlights of the development have been on

• QBIS Team has been working hard with the finalization of our soon upcoming new Expense module.
• We are also proud to deliver four new improvements for our Touchscreen devices, to make life easier for both users and Administrators. The updates for the Touchscreens will go out gradually during March and beginning of April.
• Total re-design of the System settings for Time so that an administrator easily can understand and find among the settings for the Time module.

Bugs fixed

• Added support for new API version in the Procountor integration
  The integration was updated to support new version of the Procountor integration API
• The ‘Specify Reason for Change’ dialog box was not consistently displaying.
  Hours were shown in different formats inconsistently.
• Working Hours week total is missing Monday’s working time hours in the Mobile UI.
  Monday’s were excluded in the week total on the Mobile UI so that the totals would differ compared to the total in the web version.
• Salary code truncated when saving new User Account page causing issues in PAXML salary exports.
  Due to bug truncating the Salary codes when PAXML salary exports where selected the exported files caused errors when importing.
• Change how enhanced lodgings are exported in the PAXML format.
  Due to changes in some features, caused missing values in the exported file so that the exported file was not correct.
• Clock Times are prefilled on salary activity even when there are multiple intervals registered.
• Export of GL Code for PAXML exports were not working
• Capacity Utilization Report hanged during creation in some cases due to a backend error.
• Time Overview > My Time Widget: When changing employee in detailed view, the data is not updated.
  When switching user in the My Time Widget the data show was not reloaded to show the selected user.

Improvements

Touchscreen

The QBIS Team has been working hard to fulfil several improvements for the Touchscreen. The updates will go out to all running Touchscreens gradually during March.

Add support for Touchscreen handling Specify Clock Times.
We have added the possibility to use salary activities with clock time request setup to be shown and requested on the Touchscreen.

Unsatisfying interaction between the Touchscreen and HR schedules and Specify Breaks.
The interaction between HR Schedules and the touchscreens have been improved to retrieve multiple breaks if it has been added to the schedule.

The Touchscreen is not handling Prefilled breaks.
Improvements for handling prefilled breaks. See https://help.en.qbis.se/article/how-prefilled-time-really-works-on-the-touchscreen/

The Touchscreen is not handling any factors on salary activities except for factor 1.
The handling of salary activities with factors other than 1 has been approved to support any factor.

Add the Touchscreen as an Extension
The Touchscreen activation has now been moved into our new Extension Area to make it easier to administrate and have control of activated devices.

Project module

Enhancement of the Team tab inside Project module
The Team tab inside a project now includes the department and the job position the user (resource) belongs to. This will E.g give Project Managers using QBIS and even team members, the possibility to easily see where their resources come from and also what skillset (job) they have.

API

Extend the WS API to include method for User Account custom fields.
We have extended the API methods to support custom fields in the User Accounts core module so that your custom fields can be retrieved to your external applications. See https://apps.qbis.se/WS/QBIS_DS.asmx for the documentation.

Time

Include verified expenses if approved expenses are set to be included in salary exports.
When the feature for verification of expenses was activated and the “Only Export approved expenses” were set, verified expense were not exported. Now the export will export both approved and verified expense if the setting is set to yes.

Implement new standard terminology for Arrive/Leave/Break
Changed terminology for Arrive, Leave and Break. The new terminology will be Start time, End time and Break.

Extensions

Month Overview and Approval Extension Enhancement
We have now improved the Extension so that it also can be used together with the Project module.

• It is now possible to see working time deviations in the Overview.
• It now shows project hrs in the Overview.

System module

System module Time settings page redesign
We have totally re-designed the Time settings in the System module to make it easier to understand and find the right settings for the System administrator.

October update 2020

New / Improvements

• Unbilled Project Revenue Report
  A new project report, for getting control of unbilled hours and revenue at a certain date or for a selected time period.
• Fortnox Supplier Invoice improvement
  In the Fortnox Supplier Invoice Importer, the Lastmodified filter implementation unnecessarily retrieved too many items making the process slow

Bugs fixed

• Wrong icon for expanding/collapse Invoiced under Invoice Manager on the edit project page
• On new databases the vacation activity should always be set as requestable
• Link to Project module page in the Personal Profile Widget despite “Show Project Module” being deselected for the user.
• Fixed an issue where managers incorrectly always had have access to themselves where they shouldn’t
• Incorrect aligned field lengths could cause crashes when exporting invoices from QBIS to Visma Administration.
• The Specification report showed wrong total amount for activities where the factor in some cases calculated twice. The issue did not affect the total amounts
• Grouped lodgings incorrectly excluded in Visma Lön export
• No data shown was incorrectly show in the Mileage Analysis report

Change Log 2019

Change Log 2018

Change Log 2017

Change Log 2016

Change log 2015